- Rating
- 1
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
This paper addresses the phenomenon that, in hierarchically controlled humanoid robots, there exists a discrepancy between the high-level reference command a_t and the proprioceptive state s_{t+1} after actual execution by the low-level controller, and proposes HWAM (Humanoid World Action Model). The method concatenates the executed proprioceptive state onto the action stream of the World Action Model, and performs joint denoising generation of state and action; the training follows the three-way FDM / IDM / Policy objectives in the UWM / Cosmos3 style, the architecture interface references Fast-WAM, and the video backbone is based on Wan2.2. The authors first quantify the discrepancy between the reference and the execution on the LimX OLI platform (direct MAE 4.42°, steady-state 2.885°) as the motivation; subsequently, on the three real-robot tasks of OLI (Candy Picking, Object Collection, Plush-Toy Picking) and the ALOHA clothes-folding task, they compare with baselines including π0.5, Fast-WAM, Cosmos3-Edge, and DiT4DiT, report the highest success rates, and provide ablations of the state objective and the training paths, as well as video prediction PSNR diagnostics.
Critical strengths
The research question is genuine and meaningful. In hierarchical humanoid control, the high level outputs reference commands, while the low-level WBC/impedance control rewrites them; "command ≠ actual execution" is a real problem. The authors quantified this phenomenon and attempted to incorporate it into WAM modeling, and this direction is worth studying. The method is simple, easy to reproduce, and has real-robot evaluation. The method only concatenates state onto the action channel, making it easy to plug into existing WAMs. The experiments are conducted on two real platforms and four tasks, with a relatively large number of baselines, and Wilson confidence intervals are provided.
Critical weaknesses
The necessity of predicting state is never argued, and the core causal chain is missing. a_t and s_{t+1} are both ground truth and highly correlated (they differ by only about 4°), s_t is already part of the input, and the predicted s is discarded at deployment—so the state objective is likely just redundant auxiliary supervision. In the teleoperation data, a_t already implicitly absorbs the execution deviation, and the low-level controller stays the same at deployment; the authors never explain why s still needs to be modeled explicitly. Their own results do not support it either: adding the state objective under VGM/Policy drops the success rate from 60.0% to 45.5%, open-loop MAE improves by only about 5%, and the PSNR gain under GT is almost trivial. Beyond that, the deviation sources (control/contact/dynamics) are never decomposed, the per-joint statistics claimed in the main text are missing from the appendix, and there is no latency compensation.
Questions for authors
-
Decomposition of the deviation sources: can the MAE be reported separately by joint groups (legs/waist, arms, dexterous hands) and by contact phase (pre-contact/contact)? Can the MAE after latency compensation (searching for the optimal time shift) be reported? And please supplement the per-joint statistics claimed in the main text but missing in the appendix.
-
What is the specific dimensional composition of state? Apart from the 31 shared joints, does it include quantities that are not in action, such as base velocity, IMU, hand currents? (The wording "first 31 shared joints" implies that state is higher-dimensional.) If it does, state provides genuinely additional information, which would significantly change my judgment of the method's motivation.
-
Please report the number of trials for each task and each configuration (including all ablations), and give the confidence interval or significance test for the 32.8-point interaction effect. Are there any multi-seed results?
-
The data is collected by teleoperation, and the operator has already corrected the commands in a closed loop based on actual execution, and the low-level controller is also unchanged at deployment. In this case, compared with directly learning a by BC, what extra does explicitly modeling s provide?