Skip to main content
Every setting for axol run-policy. Add any flag below to the command, or set it once in the control panel — see Command configuration for config files and syntax details.
Stiffness, gripper torque, observe_torques, observe_cartesian, fps, and the camera set must be the same as in Data Collection. A policy only works with the dynamics it was trained on.

Policy

Action chunking

How the action chunks returned by the policy are stitched into smooth motion.

Recording

Optional — the rollout is recorded to a dataset when --repo_id is set.

Contact safety

A contact stop trips when a joint’s torque is higher than the gravity model expects — the arm hit something. The arms then go limp instead of pushing through.

Robot

CAN buses, cameras, and what goes into observations.

Cameras

One ZED camera per slot: overhead, left_arm, right_arm. Flags are shown for overhead; swap in the other slot names. Stereo ZED X cameras are detected from their serial. The control panel’s Cameras tab edits all of this visually.

Arm gains

Arm stiffness, gripper limits, and per-joint gains. Per-arm and per-joint flags are shown for left / elbow. Swap in right, or any joint: shoulder_1, shoulder_2, shoulder_3, elbow, wrist_1, wrist_2, wrist_3.
A robot calibrated with tune.pid --save, tune.friction --save, or tune.gravity --save uses its own measured values (from ~/.almond/calibration.json) instead of the defaults below. Flags you pass still override both.
Both arms share these. kp/kd are the stiffness-1 values (the default); the soft columns are what stiffness 0 blends toward. shoulder_1 also sets kd_host_q to 3.0; every other joint leaves it null.
Fallback values of fc, k, fv, fo for each motor, measured on the reference robot with tune.friction.