Repository navigation
Publish 3D arm replay and upcoming hardware profiles - #23
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.
Question
The hardware reference runs in 3D, but its public report shows a flat stick diagram. Make the recorded arm/gripper geometry inspectable and publish the next hardware targets.
Evidence
Publish the offline native-mesh replay, preserving the original numerical receipt byte-for-byte. Add orbit/zoom, joint readouts, a recorded timeline and collision-proxy inspection, with retained DVIDIA, Three.js and upstream model notices. Include the browser acceptance receipt and a captured native-render screenshot.
List YAM, OpenArm, PiPER, ARX X5 and PAROL6 as upcoming profiles, each requiring separate simulator, adapter and benchmark evidence. Link the viewer and roadmap from the paper, research homepage and README.
These artifacts display recorded unloaded simulation. They do not establish learned skills, physical fidelity, live physics or new speed measurements. Native receipt reconstruction rejects incompatible compiled-model hashes; already exported browser replays are portable.
Reproduction
The linked DVIDIA source exports the pinned UR5e/Robotiq receipt after checking native forward reconstruction across 1,809 frames. Browser acceptance covers eight groups on desktop, phone and landscape, with zero page errors or external requests. Geometry, motion, notices and original receipt are self-hosted and sealed with a separate integrity manifest.
Checks