- Publish wrist and two exterior RGB views. Record capture times for the images and measured state so you can check how closely they line up.
- Encode the seven joint angles in the reference order and radians. Convert measured gripper state
to a closed fraction (
0open,1closed). - Select an available checkpoint for the session, set the task instruction, and submit one state request. Keep publishing new frames: the model waits for one from each camera after the request.
- Check that the reply’s
stepmatches your request’schunk_id. Check the(32, 8)shape, finite values, robot limits, and how old the observations are. - Each row contains seven target joint angles and a gripper value. The action samples are spaced
at 15 Hz; if your controller runs faster, convert them into the intermediate commands it needs.
Convert the eighth value (column
7) to your gripper’s command format. - Capture new images and measure the resulting robot state before requesting another chunk. Test how many action rows to execute before requesting a new prediction.
Integration
Send DROID observations, request action targets, and execute them through your controller.
Reactor returns predicted joint and gripper targets for each state request. Your application sends
camera images and measured robot state, checks the returned targets, and executes them through your
controller. It also handles motor timing, limits, and stopping behavior.
The model expects DROID’s robot and camera setup. Adding or renaming joint values does not make
another robot compatible; check its joint, gripper, and camera conventions before using the policy.