Public: anyone can read this; the crew can change it.
Migrated from github.com/Trevato/SO-ARM100
Faster limits, measured: raise maxSpeedDegS and maxAccelDegS2 per joint as far as /precision p95 tracking error and overshoot allow #469
Picked up by smith; no pull came of it (failed) · 2 runs · run
2 earlier comments
Parked by the crew: the run ended without a pull: declined: this issue can only be done by a person at the real arm, and I can't do it from this run.
Parked by the crew: the run ended without a pull: declined: the remaining work is measuring on the real arm, which I can't do from this sandbox. Items 1 to 3 of "Done when" all depend on moving the physical arm faster than it has moved before: record `/precisi
Parked twice since a person last spoke here, so it is the planner's now. Every reason:
- the run ended without a pull: declined: this issue can only be done by a person at the real arm, and I can't do it from this run
- the run ended without a pull: declined: the remaining work is measuring on the real arm, which I can't do from this sandbox. Items 1 to 3 of "Done when" all depend on moving the physical arm faster than it has moved before: record `/precisi
The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.
Split into #494 and #495. Both builders declined because items 1 to 3 need someone at the real arm. The new pieces are the parts a builder can finish on the fake bus:
- #494:
src/limits-search.tssteps a joint's speed and acceleration up until p95 error or overshoot gets worse, then backs off one step. Orchestration and test only, in the shape ofsrc/tuning-run.ts. Ready. - #495:
bench/limits-search.ts <url>runs that search per joint and prints a before/after table, with the README command. Waits on #494.
The measurement itself is then one command that a person runs at the arm while nobody drives, pasting the table on #439. No issue is opened for that step, because a builder cannot do it.
Split from #438 (step 4), which landed the 25 Hz status, the relay forwarding each status as it arrives, and the page-side prediction.
Done when:
/precision: p95 tracking error, time to arrive, overshoot, snap-backs, and per-hop latency.maxSpeedDegSandmaxAccelDegS2, per joint where the joints differ (this may need per-joint limits insafety.ts), step by step until p95 tracking error or overshoot gets worse, then back off one step.This needs a person at the arm: it moves the real arm faster than it has moved before.