-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Small fix to mass in convert_parmed #737
Conversation
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## main #737 +/- ##
=======================================
Coverage 91.99% 91.99%
=======================================
Files 67 67
Lines 6459 6460 +1
=======================================
+ Hits 5942 5943 +1
Misses 517 517
☔ View full report in Codecov by Sentry. |
Just as a note to this, we have added the ability to load GMSO forcefields via gmso.Forcefield.load, so you shouldn't have to use ff_utils anymore. However, we should also consider adding a gmso.Forcefield.foyer_load() method as well, so you don't have to do this conversion step every time. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, minus the single question about the GSD pinning. Good catch @chrisjonesBSU
environment-dev.yml
Outdated
@@ -15,7 +15,7 @@ dependencies: | |||
- openbabel>=3.0.0 | |||
- foyer>=0.11.3 | |||
- forcefield-utilities>=0.2.1 | |||
- gsd>=2.0 | |||
- gsd>2.0,<3.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are we pinning gsd<3? I feel like we should want the latest version to have compatibility with hoomd 4.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I meant to make an issue about this. I changed it in this PR because tests were failing. gsd 3.0 changed the API terminology from using Snapshot
to Frame
which causes some breaking changes in convert_hoomd
gsd.hoomd.Snapshot
would need be to be changed to gsd.hoomd.Frame
I'll still make an issue so that we can discuss how to handle supporting GSD.
Looks like this solves #655 as well; just noticed that. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! I will merge this once all the test pass (except for the bleeding test)
I ran into an error when using
to_parmed
andfrom_parmed
on a typed gmso topology. I think there was just a small over-sight on preparing thesite.mass
value by converting it to amu units and typefloat
which is what was already being done for sigma, charge, etc..Here is the snippet that gives an error. It results from calling
round
on a unyt quantity with value and unitsError: