Execute the action rows at 15 Hz using a controller that accepts target joint angles. Test how many
rows to execute before requesting a new prediction, and capture fresh observations for each request.
Decide whether the simulator pauses while waiting for inference or keeps advancing, and record that
choice with your results.
A reply to test inputs only checks the API connection. Evaluate task success in the simulator, how
old observations are when actions execute, how closely the controller follows the targets, and
whether actions stay within your limits before moving to
hardware integration.
Build a simulator adapter
Build a simulator bridge for the DROID policy contract.
The upstream FLUX Action repository and
DROID model card provide model and
evaluation references. Upstream local inference code does not directly connect a simulator to the
Reactor endpoint.
You will need to build the connection between your simulator and Reactor; this guide describes the
required mapping and does not include a runnable adapter. First use
Get your first actions to check the API connection, then
build the adapter using the API reference.