Skip to content

Show native arm replay in 3D and list upcoming hardware - #10

Open
Tarzelf wants to merge 2 commits into
feat/hardware-reference-v0.1from
feat/reference-3d-replay
Open

Tarzelf wants to merge 2 commits into
feat/hardware-reference-v0.1from
feat/reference-3d-replay

Conversation

@Tarzelf

@Tarzelf Tarzelf commented Oct 11, 2026

Copy link
Copy Markdown
Contributor

The hardware benchmark already runs native 3D physics, but its report displays only a flat projection of link centers. Add an offline mesh replay that exposes the actual arm, coupled gripper, collision proxies and six recorded joint angles with orbit controls and a timeline.

The exporter verifies pinned assets and the original receipt, reconstructs recorded poses with native forward kinematics, and checks tool, pad and link positions before exporting. It preserves original benchmark files and upstream notices. The browser bundle is self-hosted and reproducibly built; no live physics or physical robot control is added.

Add YAM, OpenArm, PiPER, ARX X5 and PAROL6 to the upcoming hardware roadmap with distinct model, adapter and benchmark requirements. All remain upcoming support candidates.

Validation: 500 local Python tests; native replay checks across 1,809 frames; offline wheel installation/resource checks; desktop, phone and landscape browser acceptance, including camera controls, missing case combinations, malformed-data errors and uncompressed fallback. Linux CI also rebuilds the browser bundle and exports its own numerical receipt.

This is stacked on the hardware-reference source alpha in #9. It does not merge or qualify the earlier feature stack, shoe-task competence, physical transfer or a learned action 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