Physical AI glossary
What is Action chunking?
In the guide: 3.6 How the models make smooth, precise motion
Most of these models also use action chunking: instead of predicting one action at a time, they predict a short sequence of future actions in one pass, execute part or all of it, and then predict again from the new observation. Chunking has three benefits. It produces smoother motion, because consecutive actions are generated together and are therefore consistent. It reduces the number of separate decisions at which an error can creep in. And it copes better with demonstrations in which the person paused or hesitated, which would otherwise confuse a model predicting one step at a time. Some systems overlap successive chunks and blend them to avoid a visible jolt at each boundary.
In the guide: 5.6 Onboard vs. offboard compute
Any approach must respect a layered timing structure. The lowest layer, the motor control loop that holds each joint at its commanded position or torque, runs on dedicated electronics at hundreds of hertz to a kilohertz and is always local. The question is where the higher layers, the learned policy and any reasoning model, should run. The main positions are these: - Cloud with action chunking. The model predicts a short sequence of future actions at once, a technique called action chunking. It begins computing the next sequence while the robot is still executing the current one, called real-time chunking, and the new chunk is blended in smoothly when it arrives. Network delay is thereby hidden inside the buffer of actions the robot already holds, as long as the delay is shorter than the chunk. This avoids an expensive, power-hungry computer on the robot, and the robot's hardware does not become obsolete as models grow larger. Teams using this approach run it in production for laundry, coffee making and navigation. - On the robot. Other teams, along with safety-critical driving systems, keep the model on the robot. A falling robot has no time to consult a server, and a robot holding a knife cannot freeze for three seconds without alarming the people around it. Networks cannot guarantee timing, because packet loss, congestion and outages are unpredictable, so these teams train a large model and then distill it: they train a smaller model to imitate the large model's outputs, producing a policy compact enough to run on the robot's own processors, usually with some loss of capability. - Split by speed. Some teams run fast reflexes, operating on a timescale of milliseconds, on the robot, and run slower reasoning about what the robot sees in the cloud, about once a second. The slow layer chooses goals and sub-tasks; the fast layer turns them into motion and reacts to contact. This mirrors the general hierarchical design of robot control, in which each layer runs at a rate matched to how quickly its decisions go stale. - Connectivity sets a ceiling. Many warehouses barely have internet access, with dead zones among metal racking, which limits how much any robot there can rely on the cloud.