Skip to content

Fix: Migrate suction margin/gap for MuJoCo 3.9 contact semantics - #811

Draft
danwahl wants to merge 1 commit into
mainfrom
bump-mujoco-3.10
Draft

Fix: Migrate suction margin/gap for MuJoCo 3.9 contact semantics#811
danwahl wants to merge 1 commit into
mainfrom
bump-mujoco-3.10

Conversation

@danwahl

@danwahl danwahl commented Jul 26, 2026

Copy link
Copy Markdown

Motivation

MuJoCo 3.9 redesigned the contact margin and gap geom attributes, and every suction site here uses the pre-3.9 idiom.

Brief description

Detection moved from dist < margin to dist < margin + gap, and force from dist < margin - gap to dist < margin. All five sites use margin == gap — the idiom for sensing a part without pushing it away — which now generates force from a full margin out: at margin = gap = 0.02, a 15 mm separation is force-generating on 3.10 where 3.6 produced none.

Applies the upstream migration margin_new = margin_old - gap_old, zero at every site — the markup upstream moved its own adhesion demo to. factory_sim's override="enable" forces every margin to o_margin, so its edits are inert there; kept for consistency.

Merge order

  • PickNikRobotics/moveit_pro#20813 merged first

Only correct on MuJoCo 3.10+. Under the 3.6 shipping today this reads as detection at 0, so cups stop sensing parts until they interpenetrate.

How it was tested

  • Reproduces 3.6 behavior exactly under 3.10 across a separation sweep: detection to margin + gap, zero force-generating contacts, force only on penetration.
  • All four loadable scenes still compile under 3.10; factory_sim Objectives run end to end against the paired branch.

Release notes

None — the user-facing migration guidance ships with PickNikRobotics/moveit_pro#20813.

MuJoCo 3.9 redesigned contact margin/gap. Detection moved from `dist < margin`
to `dist < margin + gap`, and force generation from `dist < margin - gap` to
`dist < margin`.

All five suction sites here use margin == gap, the idiom for "detect early but
only apply force on true contact". Under the new semantics that same markup
generates force from a full margin away, so the cups push parts off before
touching them. Measured with margin = gap = 0.02: on 3.6 a 15 mm separation is
detected with no force, on 3.10 it is force-generating.

Applies the upstream migration, margin_new = margin_old - gap_old, which is 0 at
every site since margin equals gap. This is the same markup upstream migrated its
own adhesion demo to.

Ordering: this markup only behaves correctly on MuJoCo 3.10 or newer. Under 3.6
it reads as detection at 0 and force at -gap, so the cups stop sensing parts
until they interpenetrate. Merge this only once moveit_pro ships the 3.10 bump,
which also carries the widen_body_margin_for_gap change that restores detection
on multi-geom bodies.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012DpJinnRQknbm62X7GCveK
@coderabbitai

coderabbitai Bot commented Jul 26, 2026

Copy link
Copy Markdown

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: d9eea250-fc18-44a9-9d2a-c88e9f50b565

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Comment @coderabbitai help to get the list of available commands.

@github-actions

Copy link
Copy Markdown

MoveIt Pro Example WS - Objectives Integration Test Report

@danwahl danwahl added this to the 10.0.0 milestone Jul 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant