How do I…?#
Short answers, grouped by stage of the pipeline. Each links to the full guide.
Get going#
Try it without a GPU |
|
Train my first policy |
|
Do everything in a browser — also on a remote GPU server |
Motion data#
Train on LAFAN / GMR / my own clips |
|
Spot bad clips before training |
Prepare motion data (Check the clips) — Studio Data → Clip |
Double the library with mirrored clips |
Prepare motion data ( |
Look up the NPZ arrays or CSV columns |
Train#
Pick a task |
|
Tune rewards, observations, sampling or PPO without code |
WBC Studio (Preset) |
Reuse a set of changes, e.g. state estimation |
WBC Studio (modules) |
Resume, extend or pin a checkpoint |
|
Train on several GPUs |
Train a policy (Multi-GPU) |
Train on rough terrain |
Evaluate and deploy#
Watch a policy on many clips at once |
WBC Studio (Play) |
Debug the reference and adaptive sampling in viser |
|
Export ONNX + |
|
Look up observation sizes |
Observations · the run’s |
Extend#
Add a robot from its MJCF / URDF |
|
Ship a robot as a package |
|
Add a paper’s setup as a task |
|
Script the Studio |
Something broke#
Troubleshooting covers the common errors — missing tasks, empty motion library, DOF mismatch, GPU / GL errors, resume, Studio access and robot checks.