Skip to content

Commit 7d77f4f

Browse files
tryakshclaude
andcommitted
Confirm the absent grasp at solver level, and name the inverted finger command
The published grasp finding inferred "the pads never touch the handle" from finger link origins, which is weak: a link origin can sit far from the pad surface it carries. Replaced with a measurement that cannot be argued with. A contact sensor filtered to the two inner-finger bodies reports exactly 0.0 N against the blade at every commanded closure across the full finger_joint range of 0 to 0.8203 rad, and the joint reaches every commanded value exactly with zero drive torque, so nothing obstructs the pads anywhere in their travel. The same sweep upgrades the secondary observation to a second defect. The joint limits are 0 to 0.8203 and pad separation is 0 mm at 0 rad, so zero is the closed end and separation grows with the command. The task calls 0.45 pregrasp and 0.60 closed, so the command it treats as closing opens the fingers by a further 16 mm. That is now a result rather than a lead, and it will surface the moment the frame error is corrected. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
1 parent f87233a commit 7d77f4f

1 file changed

Lines changed: 14 additions & 10 deletions

File tree

‎docs/status.md‎

Lines changed: 14 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -344,10 +344,14 @@ force grid from 0 to 120 N, so 128 environments sweep the surface in one run.
344344

345345
Report: `evidence/grasp_axial_pull_gate.json`.
346346

347-
**There is no grasp to characterise.** The finger pads settle 165 mm away from
348-
the handle and never touch it, the drive joints reach their commanded closure
349-
without developing torque, and the blade is a free-floating body in zero
350-
gravity. Its motion under load confirms this arithmetically rather than by
347+
**There is no grasp to characterise.** The solver says so directly: with a
348+
contact sensor filtered to the two inner-finger bodies, PhysX reports exactly
349+
0.0 N between pad and blade at every commanded closure across the full
350+
`finger_joint` range of 0 to 0.8203 rad, and the joint reaches every commanded
351+
value exactly with zero drive torque, so nothing obstructs the pads anywhere in
352+
their travel. That measurement does not depend on where the pad surfaces are
353+
assumed to be. The pads settle 165 mm away from the handle and never touch it,
354+
and the blade is a free-floating body in zero gravity. Its motion under load confirms this arithmetically rather than by
351355
inspection: 120 N on a 10 kg blade for 1.5 s predicts 13.5 m of free travel, and
352356
the measurement is 12.5 m. The earlier "failed pull gate" was not a weak grip.
353357

@@ -375,12 +379,12 @@ blade. Three consequences:
375379
three certifications. The grasp task needs its own corrected offset, leaving
376380
the insertion tasks on the value they were trained against.
377381

378-
A secondary observation needs confirming before it is acted on: finger-pad body
379-
separation grows monotonically with the commanded value, from 0 mm at 0.00 rad
380-
through 42.7 mm at 0.45 to 58.9 mm at 0.60. The task calls 0.45 "pregrasp" and
381-
0.60 "closed", so the command it treats as closed separates the pad bodies
382-
further than the one it treats as open. That was measured between pad *body
383-
origins*, not certified pad faces, so it is a lead rather than a result.
382+
A second defect sits behind the first and will bite the moment it is fixed: the
383+
finger command runs backwards. Pad separation grows monotonically with the
384+
commanded value, from 0 mm at 0.00 rad through 42.7 mm at 0.45 to 58.9 mm at
385+
0.60, and the joint's own limits are 0 to 0.8203 rad. Zero is therefore the
386+
closed end. The task calls 0.45 "pregrasp" and 0.60 "closed", so what it treats
387+
as closing the gripper opens it by 16 mm.
384388

385389
**What this does and does not invalidate.** It does not touch the promoted
386390
Level-0/1/2 insertion results. Those depend on blade-versus-slot geometry, rail

0 commit comments

Comments
 (0)