Status labels
| Detail | Description |
|---|---|
| — | These four labels show how far a feature, robot or configuration key has been checked. They appear at the top of a page, next to headings and in table rows. An item without a label has the same status as the feature its page describes. |
Labels
| Label | Meaning |
|---|---|
| Hardware-verified | Run and checked on real hardware |
| Mock only | Implemented and checked by tests and the mock (--mock) dataflow, not on hardware |
| In development | Partly implemented, or never run on hardware |
| Design only | At the design stage; not to be used as a feature |
Current status
| Item | Status |
|---|---|
Local hooks, policy teleop hooks, lifecycle events and action.filtered |
Mock only |
| Rakuda2 teleoperated collection | Hardware-verified |
| Gravity compensation | Hardware-verified |
| Collection with DIGIT | Hardware-verified |
Policy inference and intervention on Rakuda2 with your own policy (policy, policy_teleop) |
Hardware-verified |
LeRobot checkpoints (roboloom.policy.lerobot:load), lerobot-train |
Mock only (PiPER + Pika) |
| RealSense | Hardware-verified |
Asynchronous inference, replaying a recording, a policy in another process (serve-policy) |
Mock only |
| PiPER, Pika (Gripper, Sense, wrist cameras), web camera, audio | In development |
Force feedback (feedback), estimators (estimators) |
Mock only (paused) |
| Bilateral control design, stage 6 onward | Design only (paused) |
| Detail | Description |
| --- | --- |
| — | Implemented features not listed above count as Mock only. |
Writing a label
| Detail | Description |
|---|---|
| — | <span class="status status--verified">Hardware-verified</span><span class="status status--mock">Mock only</span><span class="status status--dev">In development</span><span class="status status--design">Design only</span> |