Skip to main content

Checkpoint

Your computer
Sample output

Inputs and output

Deploy and predict

Deploy the checkpoint URI directly. Orchestral resolves, imports and prepares it before bringing up the serving deployment.
your computer
Sample output
robot computer
The selected GR00T processor defines the camera keys. Inspection prints the state and action key orders with their widths. Supply the flat state vector in that order; returned action columns follow the action key order. Widths come from the saved processor’s statistics.json. Zero-width entries are inactive and are omitted from the advertised inputs and outputs; relative normalization bounds do not add action columns. For example, the base checkpoint’s XDOF embodiment has 14 active state values and 14 active action values per step. The LIBERO checkpoint contains multiple embodiment tags, so select libero_sim when inspecting, importing or deploying it. For other multi-embodiment checkpoints, pass the exact metadata tag with --options embodiment_tag=.... Select a policy within a checkpoint with --options checkpoint_subdir=.... Inspection reports each camera’s required frame offsets. Pass a single HWC image for a camera with offset [0]; pass a THWC array for a camera with multiple offsets, ordered as listed by inspection. Camera names and counts come from the selected checkpoint, so they can differ between embodiments. The runtime setting execution_capture=none selects reference PyTorch execution with the same checkpoint, BF16 precision, and saved sampling steps.