You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do you have plans to broaden your effort to include protein and biopolymer force fields?
As mentioned above, we have successfully applied for federal funding to allow us to broaden the scope of the Initiative beyond the Consortium-funded focus on small molecules and cover complex biomolecular systems. We would like to partner with the biopolymer force field community to build a family of fully consistent general biopolymer and small molecule force fields, with the goal of fully consistent handling of biopolymers and small molecules, including natural (proteins, RNA, DNA) and unnatural (e.g. peptoids) biopolymers, as well as posttranslational modifications and nonnatural amino acids. Handling of unusual nonnatural amino acids or bases can be a major headache with current force fields, but our approach will allow a single simple force field to consistently treat biopolymers and small molecules. This expanded effort is not within the current scope of Consortium funding, and would benefit from bringing in partners with significant expertise in biopolymer force field development.
We aim for our effort to be synergistic with, not competitive with, existing force field efforts, and we are seeking advice from the experts in the field who are a part of our OpenFF Initiative Advisory Board and others. We are always excited to support other efforts to seek funding for exciting new force field science—see Requesting Letters of Collaboration below if you would like us to demonstrate our support in your application for funding.
Biomolecular force fields:
amber14sb will be ported to amber14SB.offxml. After the first refit, biomolecular force field parameters will become a part of openff-x.y.z with documentation describing the details.
This seems (~4 years?) out of date
https://openforcefield.org/community/faq/
The text was updated successfully, but these errors were encountered: