Section 46.8: Advanced humanoid dynamics and contact mechanics

"Operational space is the wish. Whole-body control is the bill."

A Field-Tested Control Loop

Why The Specialist Layer Matters

Earlier sections introduced platforms, teleoperation, whole-body control, and foundation models. This section adds the mechanical depth required for a serious humanoid researcher: reduced-order models for planning, full multibody dynamics for execution, contact mode reasoning, and controllers that remain stable when hands, feet, hips, and torso all matter.

The key abstraction is a hierarchy of models. A planner may reason over center of mass, centroidal momentum, footstep locations, and hand contact targets. A whole-body controller then maps those targets into joint torques or position commands while satisfying contact, friction, joint, actuator, and balance constraints.

Centroidal Dynamics And Balance

For a humanoid of mass $m$, center of mass position $c$, total linear momentum $l$, and angular momentum $k$, the centroidal dynamics summarize the whole robot as:

$$\dot c = \frac{1}{m}l, \qquad \dot l = mg + \sum_i f_i, \qquad \dot k = \sum_i (p_i - c) \times f_i + \tau_i.$$

The contact point $p_i$, contact force $f_i$, and contact torque $\tau_i$ are the bridge from geometry to behavior. If the required force exits the friction cone, the plan is not merely suboptimal. It asks the robot to push on the world in a direction the world will not support.

Contact-Rich Loco-Manipulation

Loco-manipulation begins when walking and manipulation stop being separable. Carrying a heavy object changes the support polygon, the feasible torso motion, the footstep plan, and the hand force budget. Opening a door may require one hand to pull, one foot to reposition, the torso to rotate, and the controller to maintain balance while the door hinge imposes a moving constraint.

A serious system therefore treats limbs as resources. A hand may be an end-effector, a brace, a sensor, or a temporary support. A foot may be a locomotion contact, a push contact, or a stabilizing anchor. Interlimb coordination is the policy that assigns these roles over time.

Practical Recipe

1. Start with a constrained task, such as pick, carry, place, or door traversal.
2. Write the contact schedule and identify which contacts are required, optional, or forbidden.
3. Plan footsteps, hand contacts, and object motion with centroidal feasibility checks.
4. Use Drake, MuJoCo, MJX, Isaac Lab, or Pinocchio to verify dynamics and constraints.
5. Train or adapt a policy only after the model-based baseline exposes the physical limits.
6. Evaluate with pushes, payload changes, object pose shifts, friction changes, and perception latency.

# Minimal evidence schema for whole-body humanoid research.
from dataclasses import dataclass, asdict

@dataclass
class HumanoidTrial:
    task: str
    contact_schedule: list[str]
    controller: str
    perturbation: str
    metrics: dict[str, float]

    def as_row(self) -> dict[str, object]:
        return asdict(self)

trial = HumanoidTrial(
    task="carry object while stepping over a low obstacle",
    contact_schedule=["left_foot", "right_foot", "left_hand_object", "right_hand_object"],
    controller="centroidal planner plus whole-body QP",
    perturbation="payload shifted by 8 cm during mid-step",
    metrics={"com_error_cm": 3.4, "max_foot_slip_cm": 0.7, "recovery_time_s": 0.42},
)
print(trial.as_row())

Expected output interpretation. The printed record is valuable because it binds the contact schedule, controller class, perturbation, and recovery metrics into one artifact. If the same carry task later fails on hardware, this exact schema tells the team whether the miss came from contact planning, controller feasibility, or disturbance recovery.