Add pair-scoped attached-payload collision checks - #2
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
strict 5 mm payload-only planning buffer
the intended payload/attachment-region contact by construction
pre-result protocol/result commit boundary
Fixed-query evidence
The original straight carry is rejected by both predicates: across 23 samples,
it has nine robot-collision samples and 11 payload-margin violations, with a
minimum cube/pillar distance of
-0.065709578 m.The fixed-seed planner returns six waypoints and 47 densified samples with:
0.011848632 mminimum cube/pillar distance0.006848632 mreserve above the 5 mm payload gate2.251250420 radjoint-space path costThe improvement is not presented as free: the carry grows from four to six
waypoints and representative worst tracking error rises from 0.0037 to
0.0067 rad.
Claim boundary
This is a sampled planning-path result for one deterministic rigid box/query at
0.05 rad joint-space edge spacing. It is not a continuous swept-volume or
hardware safety certificate. The experiment does not model grasp stability,
slip, uncertainty, fingers, compliance, calibration error, or payload-versus-
robot self-collision outside the explicitly allowed attachment contact. The
visual/mocap weld remains a scripted grasp stand-in, and executed measured
states are not audited for payload clearance in this experiment.
Reproducibility
cargo fmt --all -- --check cargo clippy --workspace --all-targets --all-features -- -D warnings cargo test --release --workspace --all-targets cargo run --release -p arm-lab-demo --bin multi_query_bench -- --checkThe exact branch passes 40
arm-labtests, seven benchmark tests, strictlint/formatting, the full existing multi-scene artifact check, compiled-pose
transform validation below
1e-10, and independent source/evidence review.Audit history
The first commit fixes geometry, pair scope, query, seed, 5 mm threshold, and
acceptance gates before implementation/results. The second commit contains the
implementation and measured evidence. Please preserve both commits rather than
squashing away that boundary.