CU-86ad1nbm0 Fix instability in multi-worker Wepy setups by replacing omm.State with custom State class - #2
Open
edeustua wants to merge 5 commits into
Open
CU-86ad1nbm0 Fix instability in multi-worker Wepy setups by replacing omm.State with custom State class#2edeustua wants to merge 5 commits into
edeustua wants to merge 5 commits into
Conversation
edeustua
force-pushed
the
emiliano/multi-gpu
branch
from
November 5, 2025 03:17
ac47480 to
a79321e
Compare
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.
Previously, both TaskMapper and WorkerMapper relied on omm.State objects from OpenMM to manage simulation state. This caused issues when spawning multiple processes, each initializing its own omm.Context, leading to conflicts and unstable behavior in multi-worker Wepy runs.
To address this, a custom State class has been implemented. This new class reproduces the functionality of omm.State—tracking positions, velocities, energies, and other simulation data—without depending on the underlying C++ object that is tightly coupled to a single OpenMM context.