Learn¶
One page per workflow question, each ending with something that runs; pick the row that matches what you are doing.
Guides by subsystem, each ending in something that runs. New here? The Start ladder orders these for a first week, and Concepts explains the three objects every page uses.
| you want to | read |
|---|---|
| hand a robot to an agent and see the gate work | Agents |
| build a scene, add objects and cameras, randomize | Simulation |
| run a Hub checkpoint, pick a provider | Policies |
| record a dataset and train from it | Record, Training |
| plug in a real arm | Drivers, Feetech arms |
| several robots, one e-stop | Mesh, Safety and e-stop |
Policies¶
- Policies: which provider for what you have, the provider matrix and one page per provider; lerobot_local runs a Hub checkpoint in process.
Agents, simulation, training¶
- Agents: a
Robotas a Strands tool, the tools around it, the operator gate, what a refusal looks like. - Simulation: MuJoCo, Isaac, Newton, worlds and objects, predicates and rollouts, randomization.
- Training: what trains where; LeRobot, RL, Isaac Lab.
Data¶
- Record, Verify, Foxglove, Label and judge, Stream and sync: a dataset from the first frame to a filtered training set, and a live view while it records.
Hardware¶
- Drivers: the contract and the generated table of shipped drivers.
- Teleoperation, Cameras, Calibration.
- Setup pages: Feetech arms, Unitree, Franka, UR, Reachy Mini, Microduck, Booster T1.
Mesh¶
- Mesh: what it is and the three switches.
- Fleet, Safety and e-stop, Topics, Bridges.
Operate¶
- Dashboard: what
strands-robots dashboardserves, who may click, the e-stop button. - ROS 2: three transports, when each, one gate.
- Security: every control between a model and a motor, on one page.
Every runnable fence on these pages was executed against this commit. A fence marked sketch needs hardware, a GPU or an account, and says which.