Allow a dynamics object to propagate several independent trajectories - #458
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds functionality to allow a dynamics context to be re-used for a dynamics block at a different lambda value to the one at which it was created, e.g. within a Hamiltonian replica exchange simulation. Methods are provided to query and set the internal "clock" parameters of the object, as well as swapping the energy trajectory. Building on top of this allows us to extend SOMD2 to enable replica exchange on more modest hardware, where it's not possible to create contexts for all replicas due to memory constraints, or to perform simulations where a very large number of replicas are needed, e.g. ABFE.
develinto this branch before issuing this pull request (e.g. by runninggit pull origin devel): [y]