Closed mattwthompson closed 1 year ago
I think we could use something like this to include all standard electrostatic forces, tagging @SimonBoothroyd to double check.
if parameter_key.tag in {"ChargeIncrementModel", "LibraryCharges", "VirtualSiteHandler"}:
# Make sure to retain all of the electrostatic handlers when dealing with
# charges as the applied charges will depend on which charges have been applied
# by previous handlers.
handlers_to_register.update(
{"Electrostatics", "ChargeIncrementModel", "LibraryCharges", "VirtualSiteHandler", "ToolkitAM1BCC"}
)
@jthorton that looks right - good catch on "ToolkitAM1BCC"
as I think that should be there also!
For testing, would it be sufficient to make system subsets in a number of different cases or should we set up some actual gradient-based calculations?
For testing, would it be sufficient to make system subsets
I think this would be enough and maybe make sure we can calculate the energy of the sub system using openmm and matches what we expect particularly for systems with v-sites, maybe add in a system mixed with v-site water and some other molecule without a v-site.
@jthorton this does everything I think we set out for it to originally do - I'm not sure all gradient-based fitting is enabled but I'd like to get this change in before worry about that scale. Could you give this a brief once over in case I've accidentally slipped in something silly?
Thanks!
Description
This PR is a minimal change to get this snippet running without (obvious) error.
Todos
Notable points that this PR has either accomplished or will accomplish.
VirtualSiteHandler
in system subsetVirtualSiteHandler
's dependencies in system subsetscale_amount=-0.5
)distance
parameter in OPCQuestions
Status