humanoidsdata.com

Search

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

← All glossary terms

Hardware & control

Task space

Task space is a coordinate space used to express quantities directly relevant to a robot task, such as an end-effector pose, centre-of-mass position, gaze direction, contact force, or several objectives together. It describes what should be achieved, while joint space describes the robot configuration used to achieve it.

Also known as: operational space, Cartesian task space

Updated

A task selects controlled quantities

Khatib's operational-space formulation develops control directly in coordinates associated with a manipulation task. A hand position is a common example, but humanoid tasks can also include foot contacts, torso orientation, gaze and centre-of-mass motion.

Task space is therefore not always ordinary three-dimensional workspace. It can combine position, orientation, force or other outputs chosen for the objective. Every component needs a reference frame, units and convention.

Kinematics connects task and joint spaces

Forward kinematics maps a joint configuration to task quantities. The robot Jacobian relates their local velocities. Inverse kinematics searches for joint values that realise a desired task-space target.

The mapping is often many-to-one: a redundant humanoid can keep its hand fixed while changing elbow posture. Whole-body controllers use this freedom to balance priorities such as reaching, avoiding joint limits and maintaining foot contact. Near a singularity, some task-space motions require very large joint velocities or cannot be produced locally.

Commands must state their representation

An end-effector action may encode an absolute pose, a relative pose, a velocity or a wrench. Rotations may use matrices, quaternions, Euler angles or axis-angle vectors. Numerically similar arrays can therefore mean different actions.

Robot datasets should document the controlled link, parent and reference frames, rotation representation, units, update rate and mapping to low-level control. If several tasks are stacked, preserve priorities and weights. Task-space data without those conventions cannot be replayed reliably.

Sources