-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Frames and energies are always saved after dynamics.run() #256
Comments
Given the way that things are currently implemented, this is really tricky to fix. For example, the total number of steps is stored as a class attribute, but this is only updated if the state is saved when the dynamics block exits, which only happens when coordinates are saved, or when |
This diff seems to fix things, although I'll need to make sure that there are no unintended consequences.
|
I am using Sire dynamics for replica exchange. In doing so, I need to run short cycles at the
energy_frequency
then swap replicas. However, if I set aframe_frequency
to larger than my simulation run time I find that a frame is still saved afterdynamics.run()
completes. In fact, it seems that energies and frames are always saved when it exits. This is massively impacting performance, since I am effectively saving frames at the (very short)energy_frequency
.As a solution, the code should be updated so that calls to
.run()
are not independent of each other, i.e. it remembers how many steps were performed before and calculates the time till saving the energy or a frame accordingly.The text was updated successfully, but these errors were encountered: