No more operational messages #473
Open
+99
−384
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
facebook-github-bot
added
the
CLA Signed
|
This pull request was exported from Phabricator. Differential Revision: D77941643 |
thomasywang
added a commit
to thomasywang/monarch-1
that referenced
this pull request
Jul 9, 2025
Summary: Operational messages were used in order to signal to the simulator that it should perform certain actions like growing or shrinking the mesh. This was needed since the python and rust were running in separate processes, and messages were needed to communicate between the two, but now everything is on the same process so we can do this in memory. Differential Revision: D77941643
thomasywang
force-pushed
the
export-D77941643
branch
from
fc60c01 to
2770cc6
Compare
|
This pull request was exported from Phabricator. Differential Revision: D77941643 |
thomasywang
added a commit
to thomasywang/monarch-1
that referenced
this pull request
Jul 9, 2025
Summary: Operational messages were used in order to signal to the simulator that it should perform certain actions like growing or shrinking the mesh. This was needed since the python and rust were running in separate processes, and messages were needed to communicate between the two, but now everything is on the same process so we can do this in memory. Differential Revision: D77941643
thomasywang
force-pushed
the
export-D77941643
branch
from
2770cc6 to
1933700
Compare
thomasywang
added a commit
to thomasywang/monarch-1
that referenced
this pull request
Jul 9, 2025
Summary: Operational messages were used in order to signal to the simulator that it should perform certain actions like growing or shrinking the mesh. This was needed since the python and rust were running in separate processes, and messages were needed to communicate between the two, but now everything is on the same process so we can do this in memory. Differential Revision: D77941643
|
This pull request was exported from Phabricator. Differential Revision: D77941643 |
thomasywang
force-pushed
the
export-D77941643
branch
from
1933700 to
ec043a3
Compare
thomasywang
added a commit
to thomasywang/monarch-1
that referenced
this pull request
Jul 9, 2025
Summary: Pull Request resolved: pytorch-labs#473 Operational messages were used in order to signal to the simulator that it should perform certain actions like growing or shrinking the mesh. This was needed since the python and rust were running in separate processes, and messages were needed to communicate between the two, but now everything is on the same process so we can do this in memory. Differential Revision: D77941643
thomasywang
added a commit
to thomasywang/monarch-1
that referenced
this pull request
Jul 10, 2025
Summary: Operational messages were used in order to signal to the simulator that it should perform certain actions like growing or shrinking the mesh. This was needed since the python and rust were running in separate processes, and messages were needed to communicate between the two, but now everything is on the same process so we can do this in memory. Differential Revision: D77941643
thomasywang
force-pushed
the
export-D77941643
branch
from
ec043a3 to
cf2fc1f
Compare
thomasywang
added a commit
to thomasywang/monarch-1
that referenced
this pull request
Jul 10, 2025
Summary: Operational messages were used in order to signal to the simulator that it should perform certain actions like growing or shrinking the mesh. This was needed since the python and rust were running in separate processes, and messages were needed to communicate between the two, but now everything is on the same process so we can do this in memory. Differential Revision: D77941643
Summary: Pull Request resolved: pytorch-labs#473 Operational messages were used in order to signal to the simulator that it should perform certain actions like growing or shrinking the mesh. This was needed since the python and rust were running in separate processes, and messages were needed to communicate between the two, but now everything is on the same process so we can do this in memory. Differential Revision: D77941643
thomasywang
force-pushed
the
export-D77941643
branch
from
cf2fc1f to
219ae17
Compare
|
This pull request was exported from Phabricator. Differential Revision: D77941643 |
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.
Summary: Operational messages were used in order to signal to the simulator that it should perform certain actions like growing or shrinking the mesh. This was needed since the python and rust were running in separate processes, and messages were needed to communicate between the two, but now everything is on the same process so we can do this in memory.
Differential Revision: D77941643