Rakuda2: teleoperated collection
Hardware-verified
- Goal: drive the follower with the leader and save episodes with the RealSense (and DIGIT) to a LeRobotDataset.
- Prerequisites: Rakuda2: configuration and read check is done; for gravity compensation, Rakuda2: gravity compensation too.
- Time: 30 minutes or more.
- Result: episodes are saved in
.roboloom/rakuda2/datasets/rakuda2(rakuda2-digitwithdigit).
1. Prepare
Before collecting, optionally configure leader joint locking and torso-yaw compensation. Edit control in the active leader*.yaml and couplings in controller.yaml. Align the leader joints to be locked with the follower before launch. These settings work with both standard and gravity-compensated configurations, but the combination has not been tested on hardware.
With only gravity enabled, the configuration records RealSense only. To also record DIGIT, enable the option digit as well (--with gravity,digit); the save location is separated automatically as rakuda2-digit. For the supported combinations and limitations, see Rakuda2.
Before moving the follower, verify the robot's safe range, low-speed following, stop, and torque off, then change nodes/follower.yaml to torque: true. Support both arms, and start after completing the EEPROM check with the dataflow stopped.
2. Start and collect
uv run roboloom validate --with gravity
uv run roboloom run --with gravity
With --with, the launcher is not opened. To start from the launcher, run uv run roboloom, choose rakuda2 in the robot list, and tick gravity.
- Check the robot status, sensor acquisition rates, and recorder. If an initial pose (home) is configured,
homemoves both arms there before you start. - Align the leader to the follower and confirm the controller is
following. While analigningwarning is shown, match the pose and retry starting. - Start following and recording with
start pick up the cup, and operate with the leader. - Stop with
stop.stopholds the follower and does not turn off torque. - Save with
save, or discard withdiscard. Check the saved result's warnings for missing-data rate, valid-command rate, and control period. - Collect another episode with the next
start <task>. - To finish, do
stop→ save or discard → support the leader and follower arms andquit, then explicitly select supported Release or follower Hold in the confirmation. Cancel is selected initially; Enter alone cancels.
estop on a fault is latched and does not recover automatically. Operate with physical support and stop means available.
3. Collect episodes of a fixed length
Fixed-duration collection can also be done with the following. After the controller is ready, follow the on-screen instructions and press Enter to start.
uv run roboloom record --task "pick up the cup" --seconds 30 --episodes 3 --with gravity
The same dataflow can be used from Python.
from roboloom import Session
with Session.launch("rakuda2", options=["gravity"]) as session:
session.wait_ready()
result = session.record("pick up the cup", seconds=30)
print(result.index, result.frames, result.warnings)
The arms must be supported when the script ends as well. To build in manual stop and release, see Python API.
4. Where it is saved
With only gravity enabled, the save location is .roboloom/rakuda2/datasets/rakuda2 (output is relative to the configuration YAML); with digit it becomes datasets/rakuda2-digit. Logs are kept in .roboloom/rakuda2/logs/<dataset name>-<time>/. Keep the configuration, calibration, and tuning YAMLs under management, and you can resume collection into a dataset with the same configuration, FPS, and features.
Interactive CLI commands use the Textual operator screen: Ctrl-L for command input, Ctrl-N for panes, Ctrl-G for emergency stop, Ctrl-C/Ctrl-Q for exit confirmation. record --plain and non-TTY runs start without an Enter prompt. Python API displays remain input-free Rich views.
Next
- Check the recording, train a policy and run it: Rakuda2: from collection to inference
- Dataset columns and missing data: Dataset format