humanoidsdata.com

Search

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

← All glossary terms

Data & collection

Motion capture

Motion capture is the measurement and reconstruction of a person’s or object’s movement over time, commonly as joint positions, orientations or a fitted body model. Optical markers, cameras and inertial sensors can supply the measurements. Humanoid robotics uses the resulting motion sequences for analysis, imitation and retargeting to a robot body.

Also known as: mocap

Updated

How motion is captured

Optical systems track visible markers or estimate pose from images. Inertial systems use body-worn accelerometers and gyroscopes to infer segment orientation and movement. Hybrid systems combine signals to reduce weaknesses such as visual occlusion or inertial drift. The Physical Inertial Poser paper demonstrates full-body tracking from six inertial measurement units with physics-based correction.

The output may be raw marker positions, skeletal joint rotations, root motion or a fitted body mesh. AMASS converts multiple optical marker-based datasets into a common SMPL-family body representation. That processing makes sources easier to combine, but it also embeds choices about the body model, coordinate frames and pose fitting.

From human motion to humanoid data

Captured human movement is not a robot control command. A humanoid has different limb lengths, joint limits, mass distribution, actuators and feet. Motion retargeting must map the recording to that body while preserving contacts and balance as far as the task requires. Fast or acrobatic human poses may remain physically infeasible.

Motion capture is useful as a reference for locomotion, whole-body skills and natural movement priors. DeepMimic used captured clips as imitation targets while reinforcement learning produced physics-based control. For reusable training data, a motion-capture release should state its skeleton or body model, units, frame rate, coordinate convention, calibration and any contact labels. Object state, force and intent may need separate sensing or annotation.

Sources