feat(imitation): add controlled OpenYAM policy rollout - #3855
Draft
TomCC7 wants to merge 4 commits into
Draft
Conversation
This was referenced Sep 1, 2026
❌ 5 Tests Failed:
View the top 3 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
TomCC7
force-pushed
the
feat/openyam-lerobot-rollout
branch
from
September 1, 2026 04:46
a19c88a to
8a4b255
Compare
TomCC7
force-pushed
the
feat/openyam-lerobot-rollout
branch
2 times, most recently
from
September 1, 2026 17:00
00b98d8 to
611eabe
Compare
TomCC7
force-pushed
the
feat/openyam-lerobot-rollout
branch
from
September 1, 2026 17:16
611eabe to
ecc4e45
Compare
TomCC7
force-pushed
the
feat/openyam-lerobot-rollout
branch
from
September 1, 2026 17:17
ecc4e45 to
80d489a
Compare
TomCC7
force-pushed
the
feat/openyam-lerobot-rollout
branch
from
September 1, 2026 17:56
80d489a to
cb38d4d
Compare
TomCC7
force-pushed
the
feat/openyam-lerobot-rollout
branch
from
September 1, 2026 18:54
cb38d4d to
4c265e6
Compare
TomCC7
force-pushed
the
feat/openyam-lerobot-rollout
branch
from
September 1, 2026 23:51
4c265e6 to
65e9b0e
Compare
TomCC7
commented
Sep 2, 2026
| joint_names: Ordinary joints this task owns, in command order. | ||
| priority: Priority for arbitration. | ||
| hold_duration: Seconds to keep emitting a target; 0.0 holds forever. | ||
| requires_activation: Reject commands until explicitly activated, and |
Member
Author
There was a problem hiding this comment.
bad design why is this required
TomCC7
commented
Sep 2, 2026
TomCC7
commented
Sep 2, 2026
| primary_by_hand = { | ||
| OperatorHand.LEFT: msg.left_primary, | ||
| OperatorHand.RIGHT: msg.right_primary, | ||
| grip_by_hand = { |
Member
Author
There was a problem hiding this comment.
@ruthwikdasyam wanted to change teleop deadman lock to grip instead of AX to free more buttons for policy rollout. (notice for AI that this comment is for human and no need to address)
TomCC7
commented
Sep 2, 2026
|
|
||
| TASK_EXPOSES: dict[str, list[str]] = { | ||
| "trajectory": ["execute", "cancel", "get_state", "get_status"], | ||
| "trajectory": ["activate", "deactivate", "execute", "cancel", "get_state", "get_status"], |
Member
Author
There was a problem hiding this comment.
we shouldn't need activate/deactive this invalidates the whole point of arbitration
TomCC7
commented
Sep 2, 2026
|
|
||
|
|
||
| class PolicyRolloutSupervisor(Module): | ||
| """Own policy/task activation without blocking input or RPC handlers.""" |
Member
Author
There was a problem hiding this comment.
what why we need this class instead of policy only?
TomCC7
commented
Sep 2, 2026
Member
Author
There was a problem hiding this comment.
and what's the use of this?
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 4 of the OpenYAM learning slice in the original stack. It adds fail-closed policy task activation, semantic Quest action bindings, queued rollout supervision, and the OpenYAM rollout blueprint.
Learning slice
Validation: 217 focused rollout and control tests plus 3 generated-registry tests passed.