Repository navigation
Unify fluid trajectory recording and Gym replay - #1160
Merged
yuecideng merged 1 commit intoNov 11, 2026
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.
Description
Unify fluid trajectories with the existing Gym replay modes.
kinematicandcontrolrestore recorded robot, rigid-body and full particle positions/velocities without advancing physics;dynamicrestores the initial particle state and then replays recorded controller actions through DexUni. The separateFluidReplayEnvand its synthetic-only tests are removed.Accepted Task Program pours can opt into
--record-trajectory --record-fluid-state. Particle frames are stored in arena-local coordinates in bounded, content-verified sidecars (32 MiB per environment row), aligned to the initial, control and terminal trajectory boundaries. Fluid replay validates qualification, program hash, scene particle counts and sidecar contents before constructing the World. Existing non-fluid replay modes retain their behavior.Depends on #790 (
feat/dexuni-fluid-prototype).Type of change
Validation
kinematicanddynamicCLI replays both completed 751 steps. A real frame-200 kinematic state check had maximum particle position/velocity error 0; a 10-step dynamic check wrote fluid state only at reset and subsequently changed particle state through the solver.Checklist
black ..