humanoidsdata.com

Search

Search datasets, articles, and glossary terms for humanoids and embodied AI.

← All glossary terms

Models & learning

Action space

An action space is the set and representation of commands that an agent or robot policy is allowed to choose. In robotics, actions may be discrete choices or continuous values such as joint targets, motor torques, end-effector pose changes, base velocities, or gripper commands. The action space defines what the policy outputs, not necessarily the motion the hardware ultimately executes.

Also known as: robot action space, action spaces

Updated

The policy can choose only represented actions

In a Markov decision process, the action space specifies the choices available to the agent. Sutton and Barto use actions as the signal through which an agent affects its environment. The set can be discrete, continuous, or structured from several components.

A robot action might be a desired joint position, velocity or torque; a Cartesian change in end-effector pose; a mobile-base command; a binary gripper state; or a higher-level skill such as “grasp”. These choices create different learning problems even when the visible task is identical.

A policy output is not the executed motion

The action normally passes through controllers, safety limits and hardware before the robot moves. A joint-position target may be clipped at a limit, tracked imperfectly by a feedback controller or interrupted after contact. The recorded command, controller output and measured state are therefore different quantities.

The distinction becomes important across embodiments. Open X-Embodiment aligned many datasets to a seven-dimensional end-effector representation, but retained differences such as absolute versus relative commands, coordinate frames and control conventions. The same numerical vector can produce different motion on two robots.

What action data must document

A usable dataset should identify each action field, its units, reference frame, limits, control mode and update rate. It should state whether values are absolute targets, deltas, velocities, forces or torques; whether they were normalised; and how gripper or hand commands are encoded.

The schema should also separate requested actions from measured execution where both are available. Without that information, a model can learn a mapping whose output has the right shape but the wrong physical meaning.

Sources