[Draft] Self-consistently parameterize protein-ligand with espaloma-0.3.0 #1215
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR is a draft to self-consistently parameterize protein-ligand systems with
espaloma-0.3.0
which was built on top ofperses-0.10.1
. Note that this PR is not ready to be merged to the latest release but intended to keep track of how one could self-consistently parameterize a protein-ligand systems withespaloma-0.3.0
.Motivation and context
Current implementation of perses cannot parameterize the protein-ligand system self-consistently with
espaloma
.One work around is to parameterize the system with the current implementation (protein: Amber, ligand: espaloma), and use the solvated system to regenerate the protein with
EspalomaTemplateGenerator
implemented inopenmmforcefields.generators
.A more simple way is to handle the protein as a single residue
openff.topology.Molecule
object and append it with the other small molecules, Then load the list ofMolecules
intoopenmmforcefields.generators.SystemGenerator
. However, this raised some issues described here.How has this been tested?
This version was used to run the custom PL-benchmark described here.