-
Notifications
You must be signed in to change notification settings - Fork 86
Add Lipid21 #390
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
Add Lipid21 #390
Conversation
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #390 +/- ##
=======================================
Coverage 84.14% 84.14%
=======================================
Files 5 5
Lines 776 776
=======================================
Hits 653 653
Misses 123 123 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
The user who requested this tested it out and it works for them. I have also checked that it is able to parameterize all of the standard OpenMM Modeller-supported lipids. Let me know if this looks good, and if you approve, I will merge, and can then open a PR to add Lipid21 to OpenMM. |
|
I'm not familiar with any of this code. I don't think I'm qualified to review it! |
|
Working on #393 has been awful in general (current state can be found at https://github.com/epretti/openmmforcefields/tree/validate-amber: this is still a work in progress!), but the lipid force fields have thankfully not contributed to the many problems that have come up. So that we can get this merged here and then get Lipid21 into the OpenMM 8.4 beta, I've run some additional validation of this new force field. In addition to the basic validation done by the existing conversion script, I've put together a lipid test suite in the The associated changes to ParmEd mentioned previously had caused the GLYCAM XML file to change as well. None of the results should have changed, but I'm reverting that update in this PR for now until we can actually validate it properly by resolving #393. |
|
That sounds great. I'm sorry Amber validation has been so painful! |
Fixes #291 and #384. Relevant changes in my patched branch of ParmEd are
5592a24and98d5d5f. This also affects GLYCAM (just the FFXML, not any force field behavior) because the script that ParmEd now uses to postprocess the exceptions is more general.