robot-atlas

Manipulation & Learned Policies

Comparison Matrix

Every major policy across eight architectural axes: action representation, horizon, frequency, backbone, conditioning, cross-embodiment, hierarchy, openness.

Last reviewed 2026-08-08

The preceding modules in this domain each followed one lineage at a time. This one lays them side by side. The table below covers 18 policies, from RT-1 in 2022 to the current frontier, across the eight axes that determine how a learned policy behaves in a control loop. Every value comes from a primary source: a paper, a model card, or the vendor's own documentation, and the row carries that source. Two honesty rules apply throughout. Cells the vendor has not published read "not disclosed" instead of a guessed value, and figures that circulate without verification, such as the RT-2 and OpenVLA control rates, are omitted rather than repeated Brohan 2023 Kim 2024.

The eight axes

Action representation is how the policy emits motor commands: continuous regression, discrete tokens decoded like text, or a generative head (diffusion or flow matching) that samples continuous chunks. This choice drives everything downstream, including inference cost and control rate.

Horizon shows the planned chunk length HH against the steps actually executed H^\hat{H} before the policy re-plans. The gap between the two numbers sets the policy's reactivity: Diffusion Policy predicts 16 steps but commits 8, and π0.7 predicts 50 but commits only 15 to 25 Chi 2023 Physical Intelligence 2026.

Control frequency is the policy-side rate, not the low-level controller's. ACT queries its transformer at 50 Hz and smooths with temporal ensembling Zhao 2023; RT-1 managed 3 Hz Brohan 2022. Dual-rate stacks report both rates in the cell note.

Backbone, conditioning, and cross-embodiment describe what the model is built on, what signals it consumes, and whether one checkpoint serves multiple robot bodies. Cross-embodiment "yes" hides three different mechanisms, padded joint vectors in the π line, a shared relative end-effector frame in GR00T N1.7, and DeepMind's unnamed Motion Transfer recipe Black 2024 NVIDIA 2026 Gemini Robotics Team 2025.

Hierarchy marks whether a slow reasoning layer sits above the fast policy, and whether that layer lives inside one model (internal, as in π0.5's subtask prediction) or in a separate system (external, as when GR00T pairs with a whole-body controller) Black 2025. Weights records whether you can download the model today.

Weights
Action representation

18 of 18 methods

18 policies across the eight architectural axes. Horizon shows planned / executed steps (n.d. = not disclosed). Cells the vendor has not published are marked not disclosed and always sort last, in both directions. Rates the sources do not verify, such as the RT-2 and OpenVLA control rates, are omitted rather than guessed.
BackboneConditioning
RT-12022discrete tokens1 / 13 HzFiLM-EfficientNet + TokenLearner + 19M transformerlanguage, 6-frame image historylimitednoneopen
ACT2023continuous100 / 1temporal ensembling over overlapping chunks50 HzResNet-18 x4 + transformer encoder-decoder, ~80M4 RGB cameras, joint positionsnononeopen
Diffusion Policy2023diffusion16 / 810 Hzinterpolated to 125 Hz at executionResNet-18 + 1D CNN-UNet or DiT2 observation framesnononeopen
RT-22023discrete tokens1 / 1not disclosedPaLI-X / PaLM-E, up to 55Blanguage, imagenononeclosed
Octo2024diffusionnot disclosednot disclosedvaries by deploymenttransformer, 27M or 93M, trained from scratchlanguage or goal imageyesnoneopen
OpenVLA2024discrete tokens1 / 1not disclosedPrismatic-7B (LLaMA-2 + DINOv2 + SigLIP)language, single imageyesnoneopen
π02024flow matching50 / 5050 HzPaliGemma 3B + 300M action expert2-3 RGB cameras, language, proprioceptionyesnoneopen
OpenVLA-OFT2025continuousnot disclosednot disclosed25-50 Hz classPrismatic-7B + parallel L1 action headlanguage, image, proprioceptionyesnoneopen
π0-FAST2025discrete tokens50 / 5050 Hznominal; slower in practicePaliGemma 3B + FAST DCT tokenizer2-3 RGB cameras, language, proprioceptionyesnoneopen
π0.52025flow matching50 / 5050 HzPaliGemma-class 3B + 300M expertlanguage, images, web VQA, subtask predictionyesinternalopen
π0.62025flow matching50 / 5050 HzSigLIP 400M + Gemma3 4B + 860M expert, ~5Blanguage, up to 4 images, metadatayesinternalclosed
Gemini Robotics 1.52025not disclosednot disclosednot disclosedGeminilanguage, interleaved thinking tracesyesinternalclosed
π0.72026flow matching50 / 25executes 15-25 of 5050 Hz20 Hz on some deploymentsGemma3 4B + 860M expert, ~5Blanguage, subtask, metadata, subgoal images, memoryyesinternalclosed
Gemini Robotics 22026not disclosednot disclosednot disclosedGeminilanguage, ER 2 tool callsyesinternalclosed
GR00T N1.72026flow matching40 / n.d.not disclosedembodiment-dependentCosmos-Reason2-2B (Qwen3-VL), 3B totallanguage, images, state (dim 132)yesexternalopen
Helix 022026continuousnot disclosed200 HzS1 200 Hz, S0 1 kHzS2 VLM + S1 visuomotor transformer + S0 10Mhead and palm cameras, fingertip tactile, full-body proprioceptionlimitedinternalclosed
AgiBot GO-22026not disclosednot disclosednot disclosedasynchronous dual-ratenot disclosedlanguageyesinternalclosed
Skild2026not disclosednot disclosednot disclosednot disclosednot disclosednot disclosednot disclosedclosed

What the matrix shows

Generative action heads displaced regression. ACT's deterministic CVAE decoder is the last entry in the continuous-regression column; from late 2023 onward every row samples actions through diffusion, discrete tokens, or flow matching Chi 2023 Black 2024. The discrete-token detour of RT-1, RT-2, and OpenVLA bought web-scale pretraining at the cost of autoregressive decode latency, and the field's answer was the flow-matching action expert: continuous chunks in a handful of denoising steps, trained behind a stop-gradient so the VLM backbone keeps its web knowledge Driess 2025. π0-FAST is the exception that tests the rule: it keeps the autoregressive recipe and makes it fast enough with DCT tokenization, at roughly twice the end-to-end latency of the flow head Pertsch 2025.

Chunks got long, then execution got selective. Horizon went from 1 step in RT-1 to 50 in the π line, but the newest rows shrink the committed horizon rather than the planned one. π0.7 executes 15 to 25 of its 50 predicted steps, and the real-time chunking work exists precisely to keep long-chunk policies responsive under inference latency Physical Intelligence 2026 Black 2025.

Fifty hertz became the standard claim, and the note column shows what it costs. Temporal ensembling, parallel decoding, KV-cached prefixes, and five-step denoising all exist to make a multi-billion-parameter model answer inside a 20 ms budget Kim 2025 Physical Intelligence 2025. Helix 02's split is the extreme version: no single rate closes the loop, so a 200 Hz visuomotor policy hands off to a 1 kHz whole-body controller Figure AI 2026.

Hierarchy moved inside the model. From π0.5 onward the frontier rows all carry an internal high-level layer: subtask prediction in the π line, the ER orchestrator in Gemini Robotics, the S0/S1/S2 stack in Helix Black 2025 Parada 2026. The external-hierarchy era of separate planners is covered in the next module.

Finally, the weights column tells the access story in one glance. Everything downloadable, ACT through OpenVLA-OFT, π0 through π0.5, GR00T N1.7, sits at least one generation behind the closed frontier, and the closed rows are exactly the ones with the most "not disclosed" cells Black 2025 Bjorck 2025.

Read the closed rows with care

Gemini Robotics 1.5 and 2, Helix 02, AgiBot GO-2, and Skild disclose little or nothing about action representation, chunking, or control rate. Their cells are marked "not disclosed" because that is the honest state of the public record, and vendor demonstrations are not architecture documentation. Where a claim is unverifiable, this atlas says so instead of filling the gap with a plausible number Skild AI 2026.

One comparison the table cannot make is frequency against frequency. ACT's 50 Hz, Helix's 200 Hz S1, and π0.7's 50 Hz with training-time latency compensation are three different measurement setups, not three points on one scale. Treat the Control Hz column as "the rate the source reports for the policy" and read the cell notes before ranking two rows against each other.