- Rating
- 2
- Confidence
- 4
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper studies whole-body cooperative control for two humanoid robots performing unconstrained shared-object transport. The core claim is: reconstruct human dyadic cooperative motions from multi-view video, retarget them to paired G1 robot references while preserving relative geometry and temporal alignment; train a centralized Teacher with readiness-gated cooperative rewards and a three-stage curriculum; distill into decentralized Student policies that use a shared base policy plus role-specific residuals, augmented with lightweight learner-state refinement to mitigate closed-loop distribution shift. The paper also releases a paired demonstration dataset and achieves an 80.18% success rate in simulation, with a mention of hardware human-robot collaboration.
Critical strengths
- Problem is interesting and the data pipeline is solid. The paired demonstration construction, coordination-preserving retargeting, and multi-metric evaluation are careful and useful contributions.
- Ablations are thorough within the proposed framework. The removal of learner-state refinement, role residuals, and staged training all produce significant drops, suggesting these components matter within CoWBC.
Critical weaknesses
-
The paper fails to justify why the proposed method is necessary. The central question is: can a single-robot object-transport tracking policy (trained on single-humanoid box-carrying demonstrations, e.g., SceneBot and OmniContact, and OmniContact seems to be open sourced) be deployed zero-shot on two humanoids, each treating the other as part of the environment? Intuitively, if each robot simply tracks the object's motion while maintaining its own balance, the pair might successfully transport the object without any explicit cooperation mechanism. Without this comparison, readers cannot judge whether CoWBC's complexity is justified.
-
Hardware validation claim does not match the experimental body. The abstract and conclusion mention "hardware human-robot collaboration," yet all main tables (Tables 2, 3) report only simulation results. The conclusion itself states "dual-robot hardware validation remains future work." This mismatch inflates the perceived impact. Real dual-robot results (even with small sample size) or a downgraded claim are needed. Besides, the authors does not provides video results.
-
Cooperation metrics are geometric proxies, not physical measures. Grasp Synchronization Error, Dual Support Ratio, and VWCR are all based on wrist-to-anchor distances. The paper acknowledges they do not measure contact force. Yet Safe Success and Cooperation Pass Rate implicitly assume geometric symmetry equals good load sharing. In practice, two robots may appear coordinated while exerting opposing forces that destabilize both. Without wrist torque or contact force estimates, the claimed "cooperation" remains unvalidated.
Questions for authors
-
Have you evaluated a single-robot tracking policy (e.g., SceneBot, OmniContact) deployed zero-shot on two G1 robots? If yes, what were the Safe Success, Fall Rate, and Drop Rate? If not, why was this obvious baseline omitted?
-
If you did try it and it failed, what were the dominant failure modes? Does CoWBC's learner-state refinement, role residual, or readiness gating specifically address those failures?
4 comments
Rebuttal by Authors (Part 2)
Weakness 1 and Questions 1–2 (continued)
2. Failure mechanism and analysis of a representative episode
The key difficulty is that the shared object couples the robots’ feedback loops, however, each robot still corrects errors independently using its single-robot policy. Each action affects the shared object and the other robot’s contact forces; a common trajectory alone cannot ensure coordinated load sharing or balance. Stability learned in a single-robot setting therefore does not automatically transfer to the coupled dual-robot system.
To examine this process, we selected a representative dual-deployment episode and measured contact forces and motion states, which is shown in rebuttal's part4 https://iclr-visualization.pages.dev/#rebuttal. We also tested a single-robot control with the same checkpoint. It lifted the box in its original task by 1.27 m and finished upright. Dual deployment also initially lifted the box. However, it failed to maintain stable shared support.
During 1.0–1.3 s, the robots applied opposing vertical forces (+17.71 N and −8.96 N), causing one robot’s contact force to counteract the other’s lifting effort. During 1.655–2.375 s, the second robot lost contact with the box, leaving the first robot to support it alone; its mean upward force during 1.8–2.1 s was insufficient (3.63 N versus the 9.81 N weight), and the box accelerated downward. During 2.12–2.28 s, the box hit the floor and the first robot subsequently lost balance, illustrating the coordination and load-sharing challenges that can arise when extending single-robot policies to physically coupled dual-robot transport.
This episode illustrates a possible limitation of independent local tracking under shared-object coupling. It does not imply that all failed episodes follow the same sequence.
CoWBC addresses these challenges through three designs. Readiness gating and staged teacher training establish the conditions for sustained transport. Role-specific residuals learn local corrections for different contact conditions and postures. Learner-state refinement improves recovery from execution deviations.
3. Targeted learning designs and ablation evidence
CoWBC first learns cooperation in a physically coupled dual-robot environment and then distills the Teacher’s skills into Student policies for decentralized execution. Paired references provide consistent relative geometry and timing, while a centralized teacher learns coordinated actions under shared-object contact and robot-balance constraints. The ablations in Table 3 use different Teacher or Student baselines, so their gains should not be added together. The detailed analysis is as follows.
(a) Readiness gating and staged training: organizing objectives around skill prerequisites
Readiness gating and staged training align reward weighting and learning order with the prerequisites for cooperative transport. Gating adjusts reward weights according to body-tracking quality and bilateral readiness, while staged training progresses from stable positioning to transport and posture/robustness refinement, helping both robots establish joint support before learning more demanding skills. As shown in Table 3 in the main paper, adding gating to end-to-end Teacher training increases Safe Success from 60.53% to 71.05%, while reducing Fall/Drop Rates from 38.60%/8.77% to 28.51%/3.51%. Staged training under the same gated objective further improves these metrics to 80.30% Safe Success and 18.00%/1.80% Fall/Drop Rates, supporting the value of cooperative readiness and ordered skill acquisition.
(b) Shared base and role-specific residuals: representing shared skills and role differences
The shared base captures common control skills, while role-specific residuals provide local action corrections, allowing both robots to accommodate different postures and contact conditions. As shown in Table 3 in the main paper, adding role-specific residuals increases Safe Success from 70.86% to 80.18% (+9.32 percentage points) and Cooperation Pass from 63.60% to 82.60%, while reducing Fall/Drop Rates to 18.54%/1.66% and Wrist-to-Anchor Distance Asymmetry from 0.0589 m to 0.0487 m. These results support role-specific adaptation for cooperative transport.
(c) Learner-state refinement: extending supervision to Student-visited states
Learner-state refinement queries the Teacher at Student-visited states to reduce the mismatch between demonstrations and closed-loop execution. Because either robot’s errors alter the shared object’s motion and its partner’s interaction conditions, this corrective supervision helps both robots recover from off-reference states. As shown in Table 3 in the main paper, adding refinement increases Safe Success from 36.40% to 80.18% (+43.78 percentage points) and reduces Fall/Drop Rates from 62.28%/25.88% to 18.54%/1.66%, supporting its effectiveness in improving closed-loop cooperative execution.
Rebuttal by Authors (Part 3)
Response to weakness2:What video evidence supports the hardware claims?
- Thank you to the reviewers for their questions. We have added real-world deployment experiments demonstrating two robots jointly transporting a table while maintaining stable motion under the same fully unconstrained conditions. In response to your inquiry regarding the collaborative task between the two robots, please find attached a video demonstrating the two robots physically moving a table. You can also view the rest of the videos on our project website rebuttal's part5 https://iclr-visualization.pages.dev/ . Our framework supports different forms of cooperation, including human–robot collaboration, collaboration between robots of the same model, and collaboration between robots of different models.
Rebuttal by Authors (Part 4)
Response to Weakness 3: What can geometric cooperation metrics establish about load sharing or opposing forces without direct force or torque measurements?
We thank the reviewer for highlighting the distinction between geometric coordination and physical load sharing. We agree that wrist-to-anchor distances do not directly measure contact forces or load sharing.
We also clarify that Cooperation Pass is a geometric coordination diagnostic, not a prerequisite for Safe Success (Appendix B.4). Safe Success evaluates task-stage completion and safety outcomes.
We define adverse interactions in relation to the task and motion phase. These are interaction loads that hinder the robots’ balance, effective object support, or intended motion. Opposing gripping forces and ordinary load-bearing forces are not inherently adverse. We therefore interpret measured loads together with the robots’ execution states.
3.1 Do both robots physically support the load, rather than merely appear geometrically coordinated?
We evaluated the Student policy in 200 simulated episodes across 19 motion conditions, with box masses of 0.95–1.05 kg and friction coefficients of 0.45–0.55. The box followed simulated dynamics throughout execution, and we recorded all robot–box contact forces and Fall/Drop events.
Overall, 162/200 episodes achieved Safe Success. Airborne intervals supported exclusively by robot contacts occurred in 188 episodes, including 162 successful and 26 failed episodes. The remaining 12 episodes contributed only to overall task results.
We computed airborne support statistics per eligible episode and averaged them equally, including failures. Mean signed vertical support was for Robot 1 and for Robot 2. Both robots simultaneously provided positive vertical support during an average of 99.50% of airborne time. These measurements confirm that both robots physically supported the load, although similar average contributions do not imply equal instantaneous load sharing.
| Physical diagnostic | Result |
|---|---|
| Episodes evaluated | 200 |
| Episodes with airborne intervals supported only by robot contacts | 188 |
| Mean signed vertical support force: Robot 1 / Robot 2 | / |
| Fraction of airborne time when both robots simultaneously provide positive vertical support | 99.50% |
| Fraction of airborne time when both robots simultaneously provide upward support greater than each | 98.00% |
3.2 Can geometric coordination conceal destabilizing interactions?
We next examine interaction loads that may impair the robots’ balance or object support. We assess each robot’s loading alongside its posture, support state, and failure events.
Experimental design
We added a per-robot loading analysis based on simulated contact-force records. We computed the external moment of box contact forces about each robot’s whole-body center of mass (CoM). We examined these moments alongside base-orientation tracking errors, vertical support forces, and Fall/Drop events. The whole-body CoM was calculated from the link CoMs, weighted by their actual masses.
This analysis preserves each robot’s individual loading information. Even when the robots’ moments acting on the box cancel, their individual loads remain observable. These quantities are external contact moments, not wrist-joint torques.
Results and analysis
| Physical diagnostic | Successful episodes (n = 162) | Failed episodes (n = 26) |
|---|---|---|
| External contact moment about Robot 1’s whole-body CoM (N·m) | 18.86 ± 6.01 | 27.94 ± 12.59 |
| External contact moment about Robot 2’s whole-body CoM (N·m) | 19.42 ± 6.34 | 31.90 ± 13.26 |
| Larger base-orientation tracking error across the two robots (°) | 3.86 ± 1.29 | 23.25 ± 9.91 |
Failed episodes had higher mean episode-level P95 external moments for both robots (27.94/31.90 N·m, versus 18.86/19.42 N·m in successful episodes), alongside a higher mean episode-level P95 of the larger orientation error (23.25° versus 3.86°).
Within the 0.5 s before the first Fall/Drop event, combined vertical support decreased from to between the first and second halves of the window, while the larger base-orientation tracking error increased from 7.76° to 27.66°. These statistics are within-episode temporal means averaged equally across failed episodes, rather than P95 values, and show concurrent support loss and growing posture deviations before failure.
Together with the bilateral support measurements above, these results provide physical evidence beyond geometric coordination. They confirm that both robots physically contribute to supporting the object. They also reveal loading patterns associated with weaker support and larger posture deviations. We therefore assess cooperation using contact forces, individual loading, and execution outcomes.
Rebuttal by Authors (Part 1)
We thank Reviewer YEPk for the thoughtful review and for highlighting the strengths of our paired demonstration pipeline, coordination-preserving retargeting, and ablation studies. We appreciate your suggestion to replenish a single-robot policy on two robots and we will address this baseline, the scope of our hardware validation, and the interpretation of our cooperation metrics below.
Thank you for identifying this missing comparison. We have evaluated a frozen single-robot policy deployed independently on two G1 robots. We will include this baseline and the corresponding failure analysis in the paper.
The single-robot policy was trained with only one robot manipulating the object. During dual deployment, the other robot also actively pushes and lifts the same box. This changes both the effects of each robot’s actions and the loads it experiences. Both policy instances still correct errors according to their single-robot training. Without cooperative training, one robot’s corrections conflict with the other robot’s transport and balance requirements.
CoWBC learns cooperation in the physically coupled dual-robot environment. Readiness gating and staged Teacher training establish the prerequisites for joint transport. Role-specific residuals learn local corrections for different postures and contact conditions. Learner-state refinement provides corrective supervision at off-reference states visited by the Student. This improves recovery from execution errors.
The corresponding ablations in Table 3 of our paper also support these designs. Readiness gating, role-specific residuals, and learner-state refinement improve Safe Success by 10.52, 9.32, and 43.78 percentage points, respectively. These results support their task-level effectiveness.
1. Single-robot policy and independent dual deployment
In a representative failure, the two robots exerted opposing vertical forces on the box. One robot then lost contact, leaving the other unable to support the load. The box fell, and the remaining robot lost its balance. A video of this failure is available on our project website rebuttal's part4 https://iclr-visualization.pages.dev/#rebuttal. This case illustrates how independently deployed single-robot policies can fail to maintain stable joint support when coupled through a shared object.
Specifically, to compare a single-robot policy with its extension to two-robot cooperation, we use a PPO-trained single-G1 whole-body box-transport policy. For dual deployment, we apply the same frozen policy separately to each G1. Each robot constructs its input from its local state, assigned motion reference, and the shared object’s state and plan. Each robot then computes its joint targets independently. The two reference clocks are synchronized.
We evaluate a policy trained using the OMOMO dataset in a cooperative transport setting. Each of the three evaluation seeds covers all 19 scenarios. As shown in following table, it reports mean rates across the three seeds. All rates are expressed as percentages and rounded to two decimal places. There is no dual-robot fine-tuning. Neither policy receives teammate states or actions. The robots do not exchange actions. They interact physically through a shared object.