refactor(imitation): isolate LeRobot policy runtime - #3856
Closed
TomCC7 wants to merge 4 commits into
Closed
Conversation
Member
Author
|
Superseded by #3315 after the split baseline, policy, collection, and rollout layers were inserted into the original stack. |
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 is layer 2 of the OpenYAM learning stack. It introduces the isolated LeRobot policy runtime and its typed DimOS module boundary without collection or rollout orchestration.
Stack
Existing review history remains on #3315 because GitHub prevents changing the base branch of a PR already contained in a larger Stack. This PR points at the same tested policy commit with the correct narrow base.
Validation: 21 host-side and 14 isolated-runtime tests passed.