-
Notifications
You must be signed in to change notification settings - Fork 18
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
Remove soon-to-be-duplicate functionality from protocols.forcefield._topology_molecule_to_mol2 #152
Comments
A PR from you or @jthorton when this is moved upstream would be welcomed! |
Wait, why do we need |
@SimonBoothroyd : Note that you can feed SDF files to antechamber -fi mdl -i input.sdf -fo mol2 -o output.gaff.mol2
|
If you want a |
I remember hearing rumblings of this but wasn't sure what was decided in the end - it would be fantastic if in future decisions like this could be captured in maybe a short blog post! If this is the case I'd be happy to make the switch at some point, although looking through the issue tracker it seems like SDF support may still be a pending feature? (cc @j-wags) |
The functionality for charged SDF reading/writing wasn't ready, and getting Parsley out on time was the first priority, so I made this function to get it done. |
We're conflating different things here. @j-wags is referring to reading/writing charged SDF files for the Open Force Field Toolkit, and I was wondering if the mol2 files were used as input to In either case (OFF toolkit or antechamber/LEaP) you should not need mol2 files. I can help you get rid of them if I know why you were using them! |
@jthorton is working on integrating the functionality from https://github.com/openforcefield/propertyestimator/blob/master/propertyestimator/protocols/forcefield.py#L811-L931 back into the OpenFF Toolkit.
So, this is a bookmark to remember to remove this soon-to-be-duplicate code when possible, just so it doesn't start to diverge.
The text was updated successfully, but these errors were encountered: