Rakuda2 sensors
The sensors in the Rakuda2 template and the options that enable them. Each sensor's settings are in Sensors.
| Sensor | Node name | Configuration | How to enable | Status |
|---|---|---|---|---|
| RealSense | camera |
nodes/camera.yaml |
on by default | Hardware-verified |
| DIGIT | digit_left, digit_right |
nodes/digit_left.yaml, nodes/digit_right.yaml |
option digit |
Hardware-verified |
| Audio | audio |
nodes/audio.yaml |
choose with --sensors (off by default) |
In development |
- Set the serial numbers to those of your sensors. A sensor's name becomes its feature name in the dataset (
observation.images.cameraand so on). - Each sensor needs an entry of the same name under
max_age_msinnodes/recorder.yaml(Recorder entry).
Combinations
| Enabled options | Recorded sensors | Dataset name |
|---|---|---|
| none | RealSense | local/rakuda2 |
digit |
RealSense + left/right DIGIT | local/rakuda2-digit |
gravity, digit |
RealSense + left/right DIGIT | local/rakuda2-digit |
digit, policy |
RealSense + left/right DIGIT | local/rakuda2-digit-eval |
- The image features change, so
digiton and off are separate datasets. DIGIT episodes are not appended to a RealSense-only dataset. - Enabling
digitdoes not change the policy's input. To give the DIGIT images to a policy, setobserveinnodes/policy.yamlto[camera, digit_left, digit_right](Choosing observations). - All options are in Launch options and combinations.
Choosing sensors
Mock only
The sensors to start and record (sensors) and the sensors the policy observes (observe) are chosen separately for each launch. None is the configuration's default, [] is none. The follower state is always passed.
uv run roboloom run --sensors camera,audio
uv run roboloom infer --seconds 20 --sensors camera,audio --observe camera
with Session.launch(
"rakuda2",
options=["policy"],
sensors=["camera", "audio"],
observe=["camera"],
policy="my_lab.policies:load",
) as session:
session.wait_ready()
session.record("pick", seconds=20)
- An empty choice is
--sensors "" --observe "". The launcher has separate check boxes for the sensors to start and for the policy's observations, and remembers the last choice. - The YAML of a sensor not chosen is not read. Observing a sensor that is not started is an error.
- Sensors added by options, the left and right DIGIT included, can be chosen one by one. The choice is resolved after the options are applied.
- An optional sensor is declared in
config.yamlas{file: nodes/audio.yaml, default: false}. A plain path is on by default. - A sensor left out of
observeis still recorded when it is started. - When you pass a
RobotConfig, settle the choice withload_config(..., sensors=[...], observe=[...]). - The rules are in Sensor selection.