- Rating
- 4(+1)
- Confidence
- 3
- Informativeness
- 3
- Presentation
- 3
- Soundness
- 3(+1)
Read review
Paper summary
This paper introduces ProWAM (Progressive World Action Modeling), a world-action model for robotic manipulation that augments action generation with an ordered set of visual sub-goals. Instead of relying on dense future-video rollouts or a single endpoint prediction, ProWAM parameterizes sub-goals by normalized relative task progress. At inference time, ProWAM does not perform full iterative video generation. Instead, it performs a single forward pass through the video expert. The paper reports strong results on LIBERO-Plus, randomized RoboTwin, RoboCasa365, and a small set of real-robot tasks.
Critical strengths
- Strong empirical performance across benchmarks. ProWAM achieves competitive results on LIBERO, RoboTwin, RoboCasa365, and real-world Franka tasks.
- Practical inference-efficiency improvement. The KV-cached inference strategy significantly reduces video-backbone computation, achieving a favorable trade-off between computational efficiency and performance.
Critical weaknesses
- Predefined temporal-progress sub-goals may not always align with meaningful task stages. ProWAM indexes sub-goals by normalized temporal progress along the remaining demonstration, rather than by explicit semantic task boundaries. While this provides a simple and consistent parameterization across trajectories of different lengths, manipulation stages such as approaching, grasping, transporting, and releasing can have substantially different durations across demonstrations. It would be helpful to explain how sensitive the method is to this potential mismatch between temporal progress and task-level structure.
- The use of predefined intermediate sub-goals may face challenges in stochastic or dynamic environments. ProWAM predicts sub-goals at fixed relative-progress positions, which may be effective when the task evolves along a reasonably predictable trajectory. However, when unexpected disturbances occur or the robot deviates from the nominal execution path, the originally predicted intermediate targets may become less informative. It would be useful to clarify how the method handles cases where the predicted visual progression becomes inconsistent with the actual execution.
Questions for authors
- How are the inference-time progress schedules selected for different benchmarks? Were and tuned on a validation set, and if so, what data were used for model selection?
- Could the authors report the wall-clock training time for both Stage 1 (video-only pretraining) and Stage 2 (joint video-action fine-tuning), including the number and type of GPUs used for each stage? In addition, please provide the minimum GPU memory requirement for inference. These details are important for assessing the practical training and deployment cost of ProWAM.
- Please clarify the meaning of in Line 201, as this is its first occurrence in the manuscript. It appears that denotes the progressive visual sub-goal latent(s), i.e., the set of sub-goal representations .
- Could the authors explain why ProWAM underperforms Xiaomi-Robotics-1 on RoboCasa365? In particular, could the predefined relative-progress positions used for sub-goal prediction be misaligned with meaningful task stages, thereby limiting performance on long-horizon composite tasks?
3 comments
The authors have addressed my concerns. I recommend acceptance.
Thanks for your feedback and we are glad that we address your concerns. We really appreciate your constructive comments and the discussion
Dear Reviewer VX5X
As the discussion deadline is approaching, we would appreciate it if you could let us know of any remaining concerns. We would be happy to address them before the deadline.
Thank you