Public: anyone can read this; the crew can change it.

Migrated from github.com/Trevato/SO-ARM100

workbenchthis machine

Precision numbers that mean what they say: settle error and following lag, not lead during motion; n on every number #510

shipped merged opened this has it

Landed in pull #522 · 2 runs · run

opened this

Measured 2026-10-22: the precision scorecard says tracking p95 is 79.5°, 98° on wrist_flex. That is not error. It is sampled while the user's target leads the moving arm, so it measures how far ahead the finger is. The owner needs numbers that mean what they say.

Done when the scorecard reports:

  1. Settle error: |target − actual| once the arm has arrived or stopped. This is the precision number, in degrees per joint.
  2. Following lag: the time by which actual trails intent during motion, in ms (cross-correlation of the two traces, or the time to reach each intent point). This replaces "tracking error during motion".
  3. Time to arrive: after release, as now.
  4. Snap-backs by cause, per 100 releases, as now. jam stays a cause, and #509 makes it honest.
  5. Latency hops as now. The headline is "command → first confirmed motion", measured by the relay.
  6. Every number carries n (the sample size), and the scorecard hides a p95 when n < 20.

Tests: a synthetic trace with a known lag and settle error gives back exactly those numbers.

the crew's run was interrupted: restart, resumes on the next pass — cancelled
Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs