humanoidsdata.com

Search

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

← All glossary terms

Data & collection

Teleoperation

Teleoperation is real-time human control of a robot from a remote or mediated interface. For humanoid training-data collection, the operator’s inputs are mapped to robot motions while cameras, proprioception, commands and outcomes are recorded, producing embodied demonstrations in the robot’s own observation and action spaces.

Also known as: tele-operation, remote operation

Updated

From operator motion to robot action

ISO 8373:2021 defines teleoperation as real-time human control of robot motion from a remote site. The interface can be a joystick, a pair of leader arms, a VR system or a pose-tracking camera. “Real-time” means that the operator acts through a live feedback loop; it does not imply zero delay or a direct one-to-one mapping.

The mapping depends on the embodiment. In ALOHA, backdriven leader arms command bimanual follower arms. A humanoid system may instead convert a person’s hand or body pose into feasible targets, while a lower-level controller maintains balance and respects joint limits. OmniH2O uses kinematic pose as an interface for whole-body humanoid control through VR or RGB-camera input.

Why teleoperation produces useful training data

Teleoperation records the task from the robot’s own sensors while preserving the actions that caused each change. That makes the result more directly useful for policy learning than ordinary human video, which usually lacks robot commands and proprioception. A collection can include multiple camera streams, joint state, operator input, executed action, force signals, language and success labels.

The method does not guarantee clean demonstrations. Network delay, poor ergonomics, action scaling and operator corrections all appear in the data. The DROID collection used a shared teleoperation and robot stack to improve consistency across sites. For humanoids, collectors should also record controller mode, safety interventions and whether commanded motion was clipped, because the operator’s request and the robot’s executed action may differ.

Sources