Skip to content

Add hardware reference mechanics and measurable fidelity tools - #9

Open
Tarzelf wants to merge 2 commits into
feat/laptop-skill-pilot-v0.1from
feat/hardware-reference-v0.1
Open

Tarzelf wants to merge 2 commits into
feat/laptop-skill-pilot-v0.1from
feat/hardware-reference-v0.1

Conversation

@Tarzelf

@Tarzelf Tarzelf commented Oct 11, 2026

Copy link
Copy Markdown
Contributor

The existing authored arm has simplified links and disabled moving-arm collision masks, so it cannot establish hardware fidelity. This adds a separate pinned UR5e/Robotiq reference with verified in-memory assets, coupled gripper mechanics, collision inventory, three-timestep CPU diagnostics and offline replay. A strict paired trace scorer measures simulator/physical joint, tool and jaw disagreement without declaring hardware readiness.

Explicit provisioning preserves per-asset licenses; installed verification and scoring work without the optional native runtime. The measured bundle retains all 18 unloaded numerical attempts, source hashes and narrow timing boundaries. Physical calibration, shoe task learning and the bimanual assembly remain unmeasured. LeRobot can be a future collection layer while DVIDIA builds its own policy.

Validation: 488 local tests passed, including actual pinned native assets; 36 new reference/CLI tests and 25 paired-scoring tests pass. Installed-wheel help, asset verification, receipt inspection and scoring pass without NumPy/MuJoCo. Offline report controls, downloads and layouts passed at 1440, 390 and 320 pixels with no browser errors or remote requests. A new Linux CI job explicitly provisions and tests the reference assets.

This PR builds on the compact actuator pilot in #8. The new reference does not reuse that artifact as a task policy.

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