humanoidsdata.com

Search

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

← All glossary terms

Models & learning

Inverse dynamics

Inverse dynamics is the problem of determining the forces, torques, or actions associated with a specified motion or state transition. In model-based robotics it commonly computes joint forces or torques from position, velocity, and acceleration under a dynamics model; learned inverse-dynamics models instead infer actions from observed states or outcomes and may not expose physical parameters.

Also known as: inverse dynamics model, IDM

Updated

Two uses share one direction of inference

Classical robot dynamics relates a robot's state and acceleration to the generalized forces or torques that produce that motion. Inverse dynamics works from the desired motion toward the required effort. Modern Robotics Chapter 8 derives this relationship for open-chain robots, while MuJoCo's computation documentation explains how its inverse-dynamics pipeline evaluates forces for a known state and acceleration.

Robot learning often uses the same name for a learned mapping. An inverse-dynamics model can observe two states, a current state plus a future, or a representation of an outcome, then infer an action that connects them. It may predict Cartesian pose commands, joint targets, motor commands, or an action distribution rather than physical joint torque.

The common idea is direction: outcome or motion first, action or effort second. The inputs, outputs, and physical meaning must still be stated.

Inverse dynamics is not forward dynamics

Forward dynamics begins with the robot state and applied forces or torques, then predicts acceleration or a later state. It answers “what happens if this action is applied?” Inverse dynamics asks “what action or effort is associated with this requested change?”

A learned world model and a learned inverse-dynamics model can therefore be paired. The world model predicts a future outcome; the inverse model maps that outcome back to an executable action. ForceWAM uses this structure for contact-rich manipulation: its inverse model learns actions from recorded visual-wrench futures in both task demonstrations and exploratory play.

A learned inverse model does not guarantee feasibility

The inferred action is conditional on the data and representation used to train the model. A visually similar future can require different forces, and an action valid for one robot may violate another robot's joint, torque, contact, or timing constraints.

Dataset documentation should identify the action space, coordinate frame, control mode, prediction horizon, sampling rate, current-state inputs, future or goal representation, and whether the target action was commanded, measured, optimized, or inferred. Evaluation should separate reconstruction of logged actions from closed-loop task execution on the target system.

Sources