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
minimisation_steps, an argument to feptasks.minimize() , currently matches the openmm LocalEnergyMinimizer.minimize() argument maxIterations in that when its equal to 0, it will run as many steps of minimization as needed, not zero steps.
minimisation_steps should work like this instead:
None should be interpreted to run until tolerance is reached
Even if this is a minor change, this is an API breaking one. I think we should leave it to the next milestone release, where many API breaking changes will happen. We also need a docstring for the HybridCompatibilityMixin.setup method, I'll open a new issue for that one.
minimisation_steps
, an argument tofeptasks.minimize()
, currently matches the openmmLocalEnergyMinimizer.minimize()
argumentmaxIterations
in that when its equal to 0, it will run as many steps of minimization as needed, not zero steps.minimisation_steps
should work like this instead:See thread: #1065 (comment)
related: #1083
The text was updated successfully, but these errors were encountered: