Add multi-scene planning and penetration-aware tracking evidence - #1
Merged
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.
Summary
three shipped MuJoCo scenes and nine fixed scene/query fixtures
repository
sampled penetration for a tracking pass
field and outcome while ignoring only wall-clock planner timing
part of the planner's collision geometry
Frozen result
the numeric-plus-zero-sampled-penetration gate in 13/18
all are the
tabletop_pillar/reverse_cross_workspacefixture, with 25–72affected path samples and 0.050–0.079 mm maximum penetration
The result is intentionally evidence-bounded: the tasks are hand-designed,
planner collision checks are discrete, executed collision checks detect
sampled penetration rather than continuous swept-volume safety, and there is
no hardware or sim-to-real claim. The carried cube is not modeled as planner
collision geometry in this branch.
Reproducibility
Local release verification on the exact head passes 34
arm-labtests, sevenbenchmark tests, strict lint/formatting, the full deterministic artifact check,
and the demo build.
Audit history
The commit sequence deliberately retains the evidence corrections instead of
squashing them away: the benchmark matrix was locked before outcomes, executed
contact auditing was then added, and the collision claim was narrowed from a
positive threshold to MuJoCo-emitted sampled penetration (
dist < 0). Thishistory makes the limitations and retained failure cases reviewable.