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
I would like to clarify if PlumedForce uses periodic boundary conditions by default.
I noticed that when I created a breakpoint and inspected the PlumedForce instance the only available method is usesPeriodicBoundaryConditions. The returned value from this method is False. Additionally, since the setUsesPeriodicBoundaryConditions method is not available, one cannot change this aspect of the force.
Does this mean that the Plumed script dictates the use of periodic boundary conditions? For example, if one uses the RESTRAINT keyword in Plumed, the default option is that PBCs are used; so does PlumedForce use PBCs even though the usesPeriodicBoundaryConditions returns False?
The text was updated successfully, but these errors were encountered:
But when it comes to actually computing the force, it checks system.usesPeriodicBoundaryConditions(), that is, whether any other force in the system applies periodic boundary conditions. If so, it passes the box vectors to Plumed:
I see, thank you. I have other forces in my OpenMM script that use periodic boundary conditions, so the PlumedForce should get the box vectors from those forces.
I would like to clarify if
PlumedForce
uses periodic boundary conditions by default.I noticed that when I created a breakpoint and inspected the
PlumedForce
instance the only available method isusesPeriodicBoundaryConditions
. The returned value from this method is False. Additionally, since thesetUsesPeriodicBoundaryConditions
method is not available, one cannot change this aspect of the force.Does this mean that the Plumed script dictates the use of periodic boundary conditions? For example, if one uses the RESTRAINT keyword in Plumed, the default option is that PBCs are used; so does PlumedForce use PBCs even though the
usesPeriodicBoundaryConditions
returns False?The text was updated successfully, but these errors were encountered: