-
Notifications
You must be signed in to change notification settings - Fork 114
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
Mutating to non-standard amino acids not present in available force field libraries #286
Comments
Here's the script that was used to generate it. It just started from a standard Amber force field and modified certain parameters. It should be easy to do the same thing for any residue you have parameters for. |
Thanks @peastman
|
I haven't used espaloma, so I'm not sure how it works. Perhaps someone else can help with this? |
Thanks @peastman Best, |
It should be possible to use OpenFF, but it may require some manual work. The script above starts from an OpenMM force field. OpenFF uses its own force field format based on different concepts: chemical signatures instead of atom types. Somehow you need to create an OpenMM force field for the residue you're interested in. I don't know if there's any automated way to do that. I would ask the OpenFF developers. |
Hello.
This is related to #44
I am exploring if there is a possibility to add hundreds of non-canonical amino acids to templates and soft.xml to allow for mutating standard residues to any of these residues.
These residues don't exist in the standard force fields but can be parameterized using ambertools, openff, espaloma etc.
Are there any instructions/hints about how to use user-derived force field parameters to generate soft.xml?
It seems to me that a way to use OpenFF, Espaloma would be really nice as it would allow for quick addition of these non-canonical residues. I don't need a perfect structure as I would subject these to minimization and MD simulations later.
I would be really grateful for any suggestions.
Best,
Amin.
The text was updated successfully, but these errors were encountered: