Files
UniversalTrain-ai/docs/ROBOT_ONBOARDING_LESSONS.md
chenlin ceca51b0d8
Checks / Layout, translation and Colab checks (push) Has been cancelled
Checks / Ruff (push) Has been cancelled
Checks / Framework tests (native backend, CPU) (push) Has been cancelled
Checks / Portable Rust controller (push) Has been cancelled
Improve generic robot onboarding, walking controls and end-effector interaction
Default humanoid intake to command-following gait and support bounded Cartesian target dragging for arms. Carry model and actuator semantics through calibration, native verification and packaging. Document reusable intake decisions and cover them with regression tests.
2026-11-06 10:54:58 +08:00

3.9 KiB

Robot onboarding: diagnosis and skill maintenance

Start with the requested capability and operating conditions. Use the route table to select the applicable stage skills. A route recommendation is provisional until its required inputs are confirmed.

Establish the claim before choosing tools

Derive observable pass criteria from the request and available evidence before choosing a candidate. Use the rows relevant to the request:

Claim Evidence
The model loads Resolve dependencies; inspect the compiled topology, units and frames.
The physical model supports the task Check the intended initial state, constraints, joint margins and loads. Measure ground contact and stance only where relevant.
Commands work Compare requested and measured physical responses across the claimed range, including rest or transitions where meaningful.
Motion has the requested quality Pick measures suited to the mechanism and task; inspect individual components as well as the aggregate. Retain representative replay.
An export is faithful Compare source and target behavior at matched inputs and states, then compare trajectories on the declared runtime.
The package works Run the final archive with its actual dependencies and controls on its supported host.
Motion meets a subjective requirement Present representative evidence and record the user's verdict separately.

Record each relevant claim as passed, failed or untested; mark a potentially confusing but inapplicable check not applicable and say why. Keep partial passes when the overall request fails. A missing required probe is a coverage gap; it is not a measured failure of that probe.

Diagnose one layer at a time

  1. Reproduce the first failing claim. Identify the exact inputs, runtime, conditions and measurement; distinguish source facts, chosen values and unknowns. Preserve the baseline and source provenance.
  2. Trace the relevant path from input to outcome. For example, if a control moves the wrong way, compare device input, commanded target and measured movement before tuning gains. If only an export fails, compare it against the working source at the first step where they differ. Skip stages the route does not use.
  3. State a possible cause, a check that distinguishes it from an alternative, the predicted result and what decision each outcome would support. Prefer a shared instrument when it measures the right quantity; otherwise inspect source data or design a bounded probe. No robot-specific helper is required.
  4. Change the smallest justified factor. Repeat the failed check under the same conditions and check previously working behavior affected by the edit. Tie results to the applicable artifacts and settings (hashes where available). Report the margin for borderline passes. Leave the cause open if the evidence does not distinguish it; do not relax a criterion after seeing the result.

Required closeout for every new robot

Put one review in the robot's case report at completion or when blocked:

Record What to enter
Scope and evidence Requested capability, source and missing inputs, applicable gate outcomes, artifacts, conditions and limits.
Diagnosis Symptom → measurement → cause or uncertainty → change → retest result, or the next distinguishing test.
Skill decision Name the owning skill. Add or correct the reusable decision there; if covered, identify the existing rule the case confirmed. Keep robot names, values, paths and experiments in the case report.
Validation Record what was checked. For a changed decision, try a different mechanism or missing-input case without relying on the original helper. Verify links and skill metadata.

Review even if no candidate passed. This review does not authorize additional training, deployment or hardware operation.