-
Notifications
You must be signed in to change notification settings - Fork 56
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
Several bugs in Lammps IO #378
Comments
Hi, Orion- I have run out of time to support InterMol right now because of lack of funding/students and because of the future development of interchange. See ParmEd/ParmEd#1204 for more discussion . . . I'd like to promise review, but because we never set up great testing on InterMol when we started in the olden days, I can't guarantee it won't break things, and I currently don't have time to do that sort of testing when I have grad students to mentor on their projects. |
Dear Sirs, If any chance to solve Intermol problems that related to dihedral angles for conversion from LAMMPS to GROMACS? |
Hello @yel21, Unfortunately this issue was never resolved. As alluded to above above, this is a planned feature for the not-yet-completed force field interchange library. Until that package is more mature, it is unlikely we'll have a solution to cross-application force field conversion. In the meantime, the OpenFF Toolkit has some great tools for parameterizing forcefields. |
Hello @orioncohen, |
I've encountered several bugs in the LAMMPS IO when using 'opls' dihedral type and 'cvff' improper style. I believe that I can fix them, but I am wondering if those fixs would be merged.
One of the errors is already addressed by PR #349, but that has been open for two years.
The other error occurs in the
canonical_dihedral
function inlammps_parser.py
.If
dihedral == TrigDihedral
at the beginning, thenconvertfunc
will never be defined and an error will occur. An easy fix.If I create a PR and fix these issues, is any developer available to review and merge them? I'd like to contribute but it appears the code has not been updated in some time.
The text was updated successfully, but these errors were encountered: