Public: anyone can read this; the crew can change it.
Migrated from github.com/Trevato/SO-ARM100
Data view: a session's joint traces (intent against actual) #521
Pull #527 was closed · 2 runs
2 earlier comments
Parked by the crew: the preview's deploy failed and the decider saw no point in another try (pull #524 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.
Parked by the crew: the preview's deploy failed and the decider saw no point in another try (pull #527 closed).
Parked twice since a person last spoke here, so it is the planner's now. Every reason:
- the preview's deploy failed and the decider saw no point in another try (pull #524 closed)
- the preview's deploy failed and the decider saw no point in another try (pull #527 closed)
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 #533 and #534. Both parks (pulls #524 and #527) were main's red tests, fixed in 2d8bec1, and the pull bundled the arm, the store and the page. #533, the arm's 5 Hz trace at GET /precision/trace, is ready now and can start from branch smith/521-…. #534 stores and draws it, and waits on #533 and #530.
Split from #508. The session detail in /admin/data shows a turn's numbers and its events, but not its traces: the arm keeps only each drive session's summary card. Have the arm keep a decimated trace per joint (intent and read-back, e.g. 5 Hz, capped) for recent sessions, serve it with /precision, store it with the turn in facts.sqlite, and draw intent against actual in the session dialog with the event marks on the same axis.