Robot Wiki

Cross-Embodiment Transfer

Padded action vectors, motion transfer, and shared relative end-effector frames; the live disagreement.

Last reviewed
Reading time
8 min
Citations
10

An action vector is a control interface, not a hardware DoF count. ACT reports a 14-dimensional absolute-joint action vector for ALOHA, while its hardware section specifies two 6-DoF ViperX arms with grippers. The same paper also describes the observation coordinates as “7+7=14 DoF”; that wording should not be read as two 7-DoF arms Zhao 2023. Human video supplies images rather than native robot commands: EgoScale estimates hand poses, represents wrist motion relatively, and retargets hand articulation into a robot hand action space Zheng 2026. The interface and the training recipe both matter when combining these data.

The interactive compares three accounts of cross-embodiment learning with the same illustrative slot geometry. Motion Transfer is described at a high level in the Gemini report; the hatched blocks are not a recovered model architecture. Its empty human-hand row means that this diagram does not specify a hand-to-action mapping, not that the model cannot learn from human video.

Original slot-layout example

Padded shared vector: human video: no adapter modelled in this toy

7-DoF arm7 joint targets + gripper (illustrative)8 active, 24 zero-padded
dim 1: driven dimdim 2: driven dimdim 3: driven dimdim 4: driven dimdim 5: driven dimdim 6: driven dimdim 7: driven dimdim 8: driven dimdim 9: zero-padded dimdim 10: zero-padded dimdim 11: zero-padded dimdim 12: zero-padded dimdim 13: zero-padded dimdim 14: zero-padded dimdim 15: zero-padded dimdim 16: zero-padded dimdim 17: zero-padded dimdim 18: zero-padded dimdim 19: zero-padded dimdim 20: zero-padded dimdim 21: zero-padded dimdim 22: zero-padded dimdim 23: zero-padded dimdim 24: zero-padded dimdim 25: zero-padded dimdim 26: zero-padded dimdim 27: zero-padded dimdim 28: zero-padded dimdim 29: zero-padded dimdim 30: zero-padded dimdim 31: zero-padded dimdim 32: zero-padded dim
bimanual setuptwo arms, two grippers (illustrative)16 active, 16 zero-padded
dim 1: driven dimdim 2: driven dimdim 3: driven dimdim 4: driven dimdim 5: driven dimdim 6: driven dimdim 7: driven dimdim 8: driven dimdim 9: driven dimdim 10: driven dimdim 11: driven dimdim 12: driven dimdim 13: driven dimdim 14: driven dimdim 15: driven dimdim 16: driven dimdim 17: zero-padded dimdim 18: zero-padded dimdim 19: zero-padded dimdim 20: zero-padded dimdim 21: zero-padded dimdim 22: zero-padded dimdim 23: zero-padded dimdim 24: zero-padded dimdim 25: zero-padded dimdim 26: zero-padded dimdim 27: zero-padded dimdim 28: zero-padded dimdim 29: zero-padded dimdim 30: zero-padded dimdim 31: zero-padded dimdim 32: zero-padded dim
humanoid29 illustrative coordinates; not hardware DoF29 active, 3 zero-padded
dim 1: driven dimdim 2: driven dimdim 3: driven dimdim 4: driven dimdim 5: driven dimdim 6: driven dimdim 7: driven dimdim 8: driven dimdim 9: driven dimdim 10: driven dimdim 11: driven dimdim 12: driven dimdim 13: driven dimdim 14: driven dimdim 15: driven dimdim 16: driven dimdim 17: driven dimdim 18: driven dimdim 19: driven dimdim 20: driven dimdim 21: driven dimdim 22: driven dimdim 23: driven dimdim 24: driven dimdim 25: driven dimdim 26: driven dimdim 27: driven dimdim 28: driven dimdim 29: driven dimdim 30: zero-padded dimdim 31: zero-padded dimdim 32: zero-padded dim
human hand, egocentric video3D hand keypoints tracked from videono adapter modelled for human data (toy)
dim 1: unused dimdim 2: unused dimdim 3: unused dimdim 4: unused dimdim 5: unused dimdim 6: unused dimdim 7: unused dimdim 8: unused dimdim 9: unused dimdim 10: unused dimdim 11: unused dimdim 12: unused dimdim 13: unused dimdim 14: unused dimdim 15: unused dimdim 16: unused dimdim 17: unused dimdim 18: unused dimdim 19: unused dimdim 20: unused dimdim 21: unused dimdim 22: unused dimdim 23: unused dimdim 24: unused dimdim 25: unused dimdim 26: unused dimdim 27: unused dimdim 28: unused dimdim 29: unused dimdim 30: unused dimdim 31: unused dimdim 32: unused dim
blue: dims this source drivesdashed outline: zero-paddinghatched: illustrative link, not model dimensionsfaint outline: unused

Padded shared vector is an illustrative 32-slot layout across 4 rows. Robot rows zero-pad unused coordinates; the human row has no adapter modelled in this toy.

Current cross-embodiment mapping
strategy
Padded shared vector
human video
human video: no adapter modelled in this toy
embodiments
4
strip width
32 slots

This toy puts each robot row in the leading coordinates of a 32-slot vector and zero-pads the rest. It is not an implementation of pi0 or Octo and performs no normalization.

The toy does not define a human hand-to-action adapter. Its empty hand row is not a claim that padded models cannot learn from human data.

Source context: Octo Model Team 2024

Every strip width is illustrative, not a published architecture or hardware specification. The 8-, 16-, and 29-coordinate robot examples are unchanged toy choices. NVIDIA's N1.7 README describes model state/action dimensions changing from 29 to 132 relative to N1.6, and reports 20K hours of EgoScale human video. It does not turn the 29-coordinate toy into a humanoid DoF specification.

10K hours
pi0 own demonstrations
7 configurations, 68 tasks; additional public data is separate
22 embodiments
OXE v9 dataset
RT-X experiments used nine, not all 22
20K hours
N1.7 human pretraining
EgoScale human video, alongside robot demonstrations; README report
about 2×
PI generalization gain
human-robot co-fine-tuning; four human-only generalization scenarios

The four entries use different populations and units: pi0’s own robot data Black 2024, the OXE dataset rather than its nine-embodiment experimental mixture Open X-Embodiment Collaboration 2023, NVIDIA’s rounded N1.7 pretraining report NVIDIA 2026.

Kareer 2025 The fourth entry is PI’s four-scenario relative performance comparison. Human-video hours are not robot-demonstration hours.

Robot interfaces and an illustrative padded vector

The pi0 report describes 10,000 hours of its own dexterous-manipulation data across 7 robot configurations and 68 tasks, in addition to previously collected OXE, DROID, and Bridge data. Its mixture discussion counts timesteps: 9.1% comes from open-source datasets, while its own datasets supply 903 million timesteps Black 2024. Those populations do not support describing most of the 10,000 hours as OXE data.

Octo describes a different interface strategy. It curates 25 OXE datasets using delta end-effector control, zero-pads missing camera channels, and aligns gripper commands so +1 means open and 0 means closed. For downstream changes to action spaces or observations, it can add lightweight encoders or output heads while retaining the pretrained transformer Octo Model Team 2024. This is not evidence that Octo uses the article’s former widest-robot action-vector and per-embodiment normalization recipe.

The padded mode above is an original slot-layout example: it puts each toy robot’s coordinates first and fills the remainder with zeros. It does not implement either paper, and its empty human row means that this toy has no hand-to-action adapter; it does not establish that a padded model cannot learn from human data.

Moritz Reuss’s October 2025 critique says that “OXE is mostly low-quality data” and that methods for quantifying imitation-learning data quality remain inadequate. This is his stated assessment, not evidence that normalization produces a spurious transfer effect. It is also not a claim that padding cannot represent human-hand data. Reuss 2025

Strategy two: Motion Transfer across robot embodiments

Gemini Robotics 1.5 is trained on robot data from ALOHA (citing ALOHA 2), bi-arm Franka, and Apptronik Apollo, alongside Internet text, images, and video. The v3 report describes Motion Transfer as a new architecture and training recipe for learning across embodiments, and attributes its gains to aligning embodiments and extracting shared knowledge. In the generalization ablation, the authors compare GR 1.5 against two GR 1.5 variants trained without Motion Transfer: one on a single embodiment and one on multi-embodiment data. Comparisons are interleaved on the same robot work cell; they generally report mean progress score and its standard error, not just binary success. Gemini Robotics Team 2025

The separate cross-embodiment benchmark tests tasks whose action demonstrations were collected only on another robot. The report finds that Motion Transfer helps, but its incremental effect is less pronounced for Apollo than for the other platforms. This is not evidence that every benefit of adding multi-robot data comes from Motion Transfer. The report's generalization and transfer sections use a shared checkpoint; its long-horizon agent experiment separately adds post-training for bi-arm Franka. Gemini Robotics Team 2025 Gemini Robotics On-Device 2 is described as natively multi-embodiment and inheriting Motion Transfer from 1.5. DeepMind reports adaptation to new bi-arm embodiments in a few hours of adaptation time, typically with fewer than 200 examples, and names Dexmate, SO101, and Trossen demonstrations. The announcement does not give a separate count, held-out task split, evaluation denominator, or compute-only timing protocol for each platform. This is an attributed robot-embodiment adaptation result, not evidence for arbitrary human-to-robot action mappings. Parada 2026

The disclosure is partial, not absent. The v3 model card specifies continuous numerical robot actions, and the report describes the orchestrator/VLA split and Motion Transfer at a high level. It does not specify the internal alignment representation or a slot layout. Its discussion says the architecture can learn from human and synthetic videos without action annotations, while presenting broader use of those sources as future work. The interactive therefore leaves the specific hand-to-action mapping unmodelled; it must not turn that limitation into a claim that human video is unusable. Gemini Robotics Team 2025

Strategy three: one relative end-effector space for robots and humans

NVIDIA’s N1.7 README describes a relative end-effector action space shared across human and robot embodiments, with actions expressed as deltas from the current pose. It calls this representation a key factor in cross-embodiment performance and reports 20K hours of EgoScale human video in pretraining alongside diverse robot demonstrations NVIDIA 2026. That README statement does not establish the former claim that EmbodimentTag is a geometric frame transform.

The separate EgoScale v1 paper makes the motion representation more specific. It uses relative wrist motion and retargets 21 human hand keypoints into a 22-DoF Sharpa hand action space. Robot arms use relative end-effector control, but the hands use target joint angles. Its embodiment-conditioned MLP adapters encode proprioception and decode hand actions; wrist prediction, the backbone, and the action expert are shared Zheng 2026. EgoScale also uses aligned human-robot mid-training, so its method should not be described as transfer with “no domain-adaptation step.” The N1.7 README’s pretraining statement and the EgoScale paper’s full training pipeline are distinct claims.

Two reported human-to-robot transfer recipes

Physical Intelligence’s Simar Kareer and colleagues reported on December 16, 2025 that they co-fine-tuned pretrained pi0.5 on human data and the most relevant robot data. Human demonstrations were treated as another embodiment, with 3D hand positions as actions, without a special transfer-learning mechanism. The note reports about 2× performance across four generalization scenarios present only in the human demonstrations: bussing, spice, dresser, and eggs Kareer 2025. This is a relative performance ratio, not a two-percentage-point increase or a result over arbitrary robot tasks. The note does not give a numeric evaluation-trial denominator for this aggregate.

Their feature analysis projects mean-pooled final-layer VLM tokens with t-SNE. Greater human-robot feature overlap correlates with the generalization results as robot pretraining becomes more diverse; human fine-tuning data is held fixed between these models Kareer 2025. This is the reported analysis, not a proved universal scale threshold for alignment.

Ruijie Zheng and the EgoScale coauthors take a more explicitly aligned route for dexterous manipulation. They write that effective transfer in their setting requires scale, explicit motion supervision, and a small amount of precise human-robot alignment. They also report that large-scale human pretraining without precise embodiment alignment already outperforms their mid-training-only baseline across most tasks; adding aligned mid-training gives their best overall performance Zheng 2026.

Keep both results scoped to their experiments. PI studies robot pretraining followed by human-robot co-fine-tuning on four generalization scenarios Kareer 2025; EgoScale studies large-scale human pretraining, aligned mid-training, and task-specific robot post-training Zheng 2026. These two sources do not establish a winner at matched data, hardware, compute, and tasks. No claim about the existence or absence of other head-to-head experiments is made here.

How to read this module

The slot layouts are original illustrations, not published architectures or hardware specifications. Their widths and readouts are unchanged toy assumptions. Motion Transfer has a high-level description and controlled ablations in the Gemini 1.5 report, but this illustration is not its internal architecture. The N1.7 README describes state/action dimensions changing from 29 to 132 relative to N1.6; these are model-interface dimensions, not a humanoid’s hardware DoF or pi0 dimensions NVIDIA 2026. The source-reported 10K robot-data hours, 20K human-video hours, and about-2× four-scenario ratio retain their separate settings and citations above. PI’s number here is a lab-note report, not independent replication.

See also

  • Vision-Language-Action Models

    RT-1, RT-2, RT-X, Octo, and OpenVLA: web-scale pretraining meets robot control, and the cost of discrete action tokens.

  • Other Generalist Policies

    Gemini Robotics, GR00T, Helix, Skild, and GO-2: how to read closed-model vendor claims.

  • Major Datasets

    Open X-Embodiment, DROID, BridgeData V2, AgiBot World, RoboMIND: five datasets compared.

Linked from

  • Other Generalist Policies

    Gemini Robotics, GR00T, Helix, Skild, and GO-2: how to read closed-model vendor claims.

  • Action Spaces for Robot Learning

    Joint, Cartesian, torque, impedance, chunked and tokenized actions: what each representation gives the learner and pushes onto the controller.

  • Foundation Models for Robotics

    What foundation means in robotics, how VLA, world-model and multimodal pretraining differ, and what adaptation still costs.

  • Major Datasets

    Open X-Embodiment, DROID, BridgeData V2, AgiBot World, RoboMIND: five datasets compared.

  • Generalization

    What the pi0.5 and pi0.7 results demonstrate, and what they do not: the open-world gap.

References

  1. Tony Z. Zhao, Vikash Kumar, Sergey Levine, Chelsea Finn, RSS 2023.

    https://arxiv.org/abs/2304.13705

  2. Kevin Black, Noah Brown, Danny Driess, Adnan Esmail, Michael Equi, Chelsea Finn, Niccolo Fusai, Lachy Groom, and 16 more, RSS 2025, 2024.

    https://arxiv.org/abs/2410.24164

  3. Octo Model Team, Dibya Ghosh, Homer Walke, Karl Pertsch, Kevin Black, Oier Mees, Sudeep Dasari, Joey Hejna, and 12 more, 2024.

    https://arxiv.org/html/2405.12213v2

  4. Open X-Embodiment Collaboration, Abby O'Neill, Abdul Rehman, Abhinav Gupta, Abhiram Maddukuri, Abhishek Gupta, Abhishek Padalkar, Abraham Lee, and 286 more, 2023.

    https://arxiv.org/abs/2310.08864

  5. Moritz Reuss, 2025.

    https://mbreuss.github.io/blog_post_iclr_26_vla.html

  6. Gemini Robotics Team, Abbas Abdolmaleki, Saminda Abeyruwan, Joshua Ainslie, Jean-Baptiste Alayrac, Montserrat Gonzalez Arenas, Ashwin Balakrishna, Robert Baruch, and 165 more, 2025.

    https://arxiv.org/abs/2510.03342

  7. Carolina Parada, 2026.

    https://deepmind.google/blog/gemini-robotics-2-brings-whole-body-intelligence-to-robots/

  8. NVIDIA, 2026.

    https://github.com/NVIDIA/Isaac-GR00T

  9. Ruijie Zheng, Dantong Niu, Yuqi Xie, Jing Wang, Mengda Xu, Yunfan Jiang, Fernando Castañeda, Fengyuan Hu, and 7 more, 2026.

    https://arxiv.org/abs/2602.16710

  10. Simar Kareer, Karl Pertsch, James Darpinian, Judy Hoffman, Danfei Xu, Sergey Levine, Chelsea Finn, Suraj Nair, 2025.

    https://www.pi.website/research/human_to_robot

Spot a factual error or missing qualification? Report a content correction.