Cache some charge increment calculations #1126
Open
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
For some systems, most of the time writing GROMACS files was spent adding up a bunch of charges. This is a shortcut to speed that up. Some rough checks using some of the slower toolkit examples:
$ python -m pytest --nbval-lax --dist loadscope -n logical --durations=20 ../openff-toolkit/examples/using_smirnoff_in_amber_or_gromacs ../openff-toolkit/examples/using_smirnoff_with_amber_protein_forcefield -p no:randomly > head.log
With e6f9f88:
Compared to 0.4.0:
Checklist
.to_gromacs
on several systems