Skip to main content
Training a policy is rarely one-and-done. This page covers how to evaluate your skill, identify common failure modes, and iterate toward reliable performance.

First test

After deploying your trained skill, run it from Manual Control with the same setup you used for recording.
1

Reproduce the training scene

Place the robot, objects, and lighting as close as possible to the conditions you recorded in. The first test should be easy for the policy — if it fails on its own training distribution, something is wrong.
2

Run the skill

Select the skill in Manual Control and tap play. Watch the full execution without intervening.
3

Note the result

Did the robot complete the task? Where did it hesitate, overshoot, or fail? Mental notes are fine — you’ll iterate fast.

Common failure modes

SymptomLikely causeFix
Robot doesn’t move or barely movesToo few episodes, or episodes have inconsistent startsRecord more episodes with consistent start poses
Arm overshoots the targetJerky demonstrations or high variance in approach anglesRe-record smoother demonstrations; try a larger chunk size
Robot starts well but driftsNot enough variation in demonstrationsAdd more episodes with slight object position changes
Works on first run, fails on repeatObject or robot position shiftedRecord with more position variation; aim for 2–5 cm spread
Gripper doesn’t close at the right timeInconsistent grasp timing across episodesFocus on consistent timing when closing the gripper
Robot ignores the object entirelyLighting or background changed significantlyRecord in the current conditions, or control lighting more carefully

How to improve a policy

Add more data

The most reliable way to improve a policy. Add 20–30 episodes that specifically cover the failure case, sync, and retrain. You don’t need to start from scratch — the new episodes are added to the existing dataset.

Tune hyperparameters

If the behavior is qualitatively close but not quite right, adjust the run configuration — chunk size for the smoothness/reactivity tradeoff, max steps for dataset size, learning rate for training stability. When to change the defaults maps each symptom to the right knob.

Improve demonstration quality

Review your recorded episodes. Look for:
  • Episodes where you hesitated or corrected course excessively
  • Episodes that are much longer or shorter than average
  • Episodes where the start pose is significantly different
Replace low-quality episodes with clean ones, re-sync, and retrain.

Scaling up

Once your policy works in the original setup, gradually introduce variation:
  1. Move the object a few centimeters between runs
  2. Change the object slightly (same cup in a different color)
  3. Adjust lighting modestly
If the policy breaks, record 10–20 more episodes under the new conditions and retrain. Each round of data makes the policy more robust.
Invest in data variety and you’ll spend less time debugging — see how many episodes you need for concrete numbers.

Structured evaluation

Rollout evaluation (in development)

A measured version of this workflow is taking shape on the web app’s Profiling page: scored rollouts with failure tags, dedicated evaluation datasets, and auto-stop for learned skills. Still under development — not in a released OS build yet.