Repository navigation
Publish PiPER contact pilot with retained friction failure - #26
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
How does the runnable PiPER CPU profile perform on grasp, carry and release? This extends the hardware matched simulation paper and physical-grounding topic.
Evidence
Publish the frozen nine-attempt authored pilot: nominal placement 2/2, low-friction placement 0/1, open-jaw 0/3 and hold 0/3, with all nine numerically valid. Keep the slippery failure and one missed 20 ms computation window in the record.
The paper, homepage and README link the exact source and immutable Hugging Face revision
b07b6e0e95a19158384734d140abb36a9adb670b. The local summary mirror preserves original report/protocol/integrity bytes and explicitly points to the full remote bundle. Authored control, development tuning, synthetic scenes and measured CPU clocks are explained; learned shoe skills and physical robot qualification remain open.Reproduction
Source commit
c9a72584b4f35c38ad2616894f56da719bba0182; seed 642103; installed wheel run under network denial; 20 simulated seconds per attempt with 1 ms physics and 20 ms commands. The linked installation guide and frozen protocol include exact runtime, geometry, units and scoring. Measured outer wall time was 1.386–2.285 seconds per attempt on one CPU host, excluding rendering, serialization and real sensors/actuators.Checks
npm run checkbuilt 15 publications and 471 artifacts with valid metadata/links; all 42 tests passed.