Action Spaces for Robot Learning
Joint, Cartesian, torque, impedance, chunked and tokenized actions: what each representation gives the learner and pushes onto the controller.
- Last reviewed
- Reading time
- 6 min
- Citations
- 11
An action space is the interface between a policy and the rest of the robot. It decides what the network predicts, which errors the low-level controller must absorb, how frequently inference must run, and whether data from two embodiments can share labels. Calling both outputs “actions” hides differences large enough to reverse a model comparison.
The useful question is not which action space is best. It is which responsibilities should live in the learner and which should remain in a controller with explicit geometry, dynamics and safety limits.
Try the check below and choose the Cartesian interface only if the controller underneath can uphold its side of the contract.
Self-check
Read the reasoning
- Absolute joint positions for each robotThe same joint vector places different robots in different physical poses. This is easy to replay on one embodiment and a poor shared task-space label across different kinematic chains.
- Relative Cartesian end-effector deltas plus gripper stateThis expresses motion where the task happens and delegates embodiment-specific inverse kinematics and tracking to each robot controller. The frame and rotation convention still have to be identical.
- Raw motor torques at the policy inference rateTorque can express contact behavior, but it is tightly coupled to dynamics, actuator limits and a high-rate safety loop. It is the least portable starting point for these two arms.
Cross-embodiment transfer improves when the label describes task-space motion and each robot owns the kinematic conversion underneath.
The contract has four parts
An action is not only a vector. A complete action contract specifies:
- Coordinates: joint, Cartesian, object-relative or another frame.
- Semantics: absolute target, delta, velocity, force, torque or controller parameter.
- Timing: control rate, prediction horizon and how stale predictions are handled.
- Execution: interpolation, clipping, inverse kinematics, feedback control and safety limits.
Two papers can both report a seven-dimensional action while meaning different things. One may emit an end-effector translation and axis-angle rotation delta at 10 Hz, integrated by an operational-space controller. Another may emit absolute joint targets at 50 Hz. The output widths match; the learning problems do not.
Joint-space actions
Joint position targets are the common imitation-learning baseline. They align naturally with leader-follower teleoperation: the demonstrated joint angles can become the labels with little transformation. ACT used continuous targets for two six-joint ViperX arms plus their grippers, predicted as chunks rather than one step at a time Zhao 2023.
The advantage is repeatability on one mechanism. The controller can interpolate targets, enforce joint limits and close a high-rate loop below the policy. The cost is embodiment specificity. A shoulder angle on one arm does not describe the same end-effector motion on another.
Joint velocity targets remove the dependence on an absolute zero and can make short-horizon corrections smoother. They drift when integrated, and the same velocity still maps to different Cartesian motion under different link geometries.
Both representations require an accurate kinematic model. The kinematics module derives the forward map and Jacobian that connect joint motion to the hand Lynch 2017.
Cartesian actions
Cartesian actions describe what the tool should do: translate, rotate, open or close. Relative deltas are popular because they keep values locally bounded and reduce dependence on an absolute world origin. They also provide a plausible shared label for arms whose joint counts and link lengths differ.
The simplicity is above the waterline. Underneath, each robot needs inverse kinematics or an operational-space controller, singularity handling, joint-limit avoidance and a named reference frame. Khatib's operational-space formulation is the classical statement of controlling motion and force in task coordinates rather than joint coordinates Khatib 1987.
Rotation needs special care. Euler-angle deltas have discontinuities and depend on axis order. Axis-angle and exponential coordinates are compact but must define whether the increment is expressed in the tool or world frame. A six-number action is not portable until that convention is written down.
NVIDIA's GR00T N1.7 moved to a shared relative end-effector action space to align egocentric human motion with robot motion NVIDIA 2026. That is a representation choice, not merely a preprocessing detail: it determines which non-robot data can become a useful target.
Torque and impedance actions
Torque actions give a policy direct authority over dynamics and contact. They can express compliant insertion, balancing and fast reactions that position targets hide. They also demand a high control rate, accurate timing, actuator-specific scaling and a safety layer that remains effective when the learned output is wrong. Franka's control interface exposes a 1 kHz torque-level loop, which illustrates the rate at which this contract normally lives Franka Robotics 2026.
Impedance actions are a useful middle layer. The policy selects a pose target plus stiffness and damping, while a controller converts the error into forces. Variable end-effector impedance has been studied explicitly as an RL action space for contact-rich tasks Martin-Martin 2019. It gives learning control over compliance without asking it to synthesize every torque sample.
This split is often the engineering sweet spot: the learner decides how the robot should yield, and a verified controller owns the fast feedback.
Chunks change the time axis
An action chunk predicts several future steps per inference. In ACT's ablations, chunking improved ACT and the two baselines the authors retrofitted with it, and the CVAE objective proved essential on human demonstrations: removing it cut success on the two simulated human-data tasks from 35.3% to 2% Zhao 2023. Diffusion Policy also predicts a horizon and executes only the first portion before replanning Chi 2023.
Chunks reduce inference pressure and model temporally coordinated motion. They also create a stale-plan problem. If contact makes the world diverge after the first few steps, the remaining chunk reflects an observation that is no longer current. Receding-horizon execution, temporal ensembling and real-time chunk replacement Black 2025 are different answers to that problem.
Report the chunk horizon and the executed horizon separately. “Predicts 16 actions” does not tell a reader whether all 16 are sent open loop or whether the policy replans after four.
Tokens change the output geometry
RT-2 Brohan 2023 and OpenVLA mapped continuous action dimensions into discrete vocabulary tokens so robot control could use language-model training machinery. OpenVLA discretizes seven action dimensions into 256 bins and emits the tokens autoregressively Kim 2024. This makes cross-entropy training easy and adds quantization error plus sequential decoding latency.
FAST takes the opposite route: transform an action chunk into frequency coefficients, quantize the sparse coefficients, then apply byte-pair encoding. Its universal FAST+ tokenizer was trained across one million robot trajectories Pertsch 2025. The tokenizer compresses smooth trajectories better than independent uniform bins, but the decoded result is still meaningful only under the action convention used before tokenization.
Tokenization is therefore not an action space by itself. It is an encoding layered on joint, Cartesian or another continuous action space.
A selection rule
Choose the lowest-level action that the task requires and the platform can support safely.
| Requirement | Practical starting point | Main burden below the policy |
|---|---|---|
| Single-arm imitation on fixed hardware | Joint positions or velocities | Tracking and joint limits |
| Transfer across different arms | Relative Cartesian deltas | IK, frames and singularities |
| Contact compliance | Cartesian impedance targets | Fast force or torque controller |
| Dynamic locomotion or dexterity | Torque or residual torque | Dynamics, rate and safety |
| Slow semantic manipulation | Chunked Cartesian actions | Replanning and stale chunks |
| Language-model output head | Tokenized chunks | Quantization and decode latency |
Hold the controller, rate, horizon and observation history fixed when comparing policy architectures. Otherwise the experiment measures a package of interface changes. The action space is the package's most consequential part because it decides which errors learning must solve and which errors classical control is still allowed to reject.
See also
- Kinematics
Forward and inverse kinematics, DH parameters, and the Jacobian; the theory behind the 3D playground.
- Control
PID, LQR, MPC, and whole-body QP: the classical stack under every learned policy.
- Action Chunking (ACT and ALOHA)
Predicting action sequences instead of single steps: the CVAE structure, the chunk-size tradeoff, and temporal ensembling.
- Cross-Embodiment Transfer
Padded action vectors, motion transfer, and shared relative end-effector frames; the live disagreement.
Linked from
- Vision-Language-Action Models
RT-1, RT-2, RT-X, Octo, and OpenVLA: web-scale pretraining meets robot control, and the cost of discrete action tokens.
- Comparison Matrix
Every major policy across eight architectural axes: action representation, horizon, frequency, backbone, conditioning, cross-embodiment, hierarchy, openness.
- Robot Learning Curriculum for ML Engineers
A dependency-aware route from supervised learning to real robot policies, with the minimum robotics stack each stage assumes.
- The Robot Learning Stack
Data capture, schemas, training, simulation, evaluation, serving and robot integration as one reproducible system rather than a model checkpoint.
- Kinematics
Forward and inverse kinematics, DH parameters, and the Jacobian; the theory behind the 3D playground.
- Control
PID, LQR, MPC, and whole-body QP: the classical stack under every learned policy.
References
Kevin M. Lynch, Frank C. Park, Cambridge University Press, 2017.
https://modernrobotics.northwestern.edu/
Tony Z. Zhao, Vikash Kumar, Sergey Levine, Chelsea Finn, RSS 2023.
https://arxiv.org/abs/2304.13705
Cheng Chi, Zhenjia Xu, Siyuan Feng, Eric Cousineau, Yilun Du, Benjamin Burchfiel, Russ Tedrake, Shuran Song, 2023.
https://arxiv.org/abs/2303.04137
Kevin Black, Manuel Y. Galliker, Sergey Levine, 2025.
https://arxiv.org/abs/2506.07339
Anthony Brohan, Noah Brown, Justice Carbajal, Yevgen Chebotar, Xi Chen, Krzysztof Choromanski, Tianli Ding, Danny Driess, and 46 more, 2023.
https://arxiv.org/abs/2307.15818
Moo Jin Kim, Karl Pertsch, Siddharth Karamcheti, Ted Xiao, Ashwin Balakrishna, Suraj Nair, Rafael Rafailov, Ethan Foster, and 10 more, 2024.
https://arxiv.org/abs/2406.09246
Roberto Martin-Martin, Michelle A. Lee, Rachel Gardner, Silvio Savarese, Jeannette Bohg, Animesh Garg, IEEE/RSJ Int. Conf. Intelligent Robots and Systems, 2019.
https://doi.org/10.1109/IROS40897.2019.8968201
Oussama Khatib, IEEE J. Robotics and Automation, 1987.
https://doi.org/10.1109/JRA.1987.1087068
Karl Pertsch, Kyle Stachowicz, Brian Ichter, Danny Driess, Suraj Nair, Quan Vuong, Oier Mees, Chelsea Finn, and 1 more, 2025.
https://arxiv.org/abs/2501.09747
Franka Robotics, Franka Robotics, as of 2026-08-20.
https://frankarobotics.github.io/docs/
Spot a factual error or missing qualification? Report a content correction.