- Rating
- 3
- Confidence
- 3
- Informativeness
- 3
- Presentation
- 3
- Soundness
- 3
Read review
Paper summary
The paper proposes a highly lightweight WAM that facilitates deployment on edge devices and rapid transfer across tasks and embodiments. It achieves relatively competitive results with very few parameters. Simulation evaluations and real-world robot experiments demonstrate the method’s efficiency and ease of deployment.
Critical strengths
- The work achieves an effective balance between efficiency and capability, serving as a fast execution system that is easy to train and deploy. This aligns well with the role and requirements of fast systems in the agentic era.
- The paper presents extensive and comprehensive experiments that provide strong support for the method’s design rationale.
- The real-world robot experiments also demonstrate the method’s deployability, offering valuable insights for robotics research.
Critical weaknesses
- Some figures have relatively low resolution and are not in vector format; their quality should be improved.
- Additional results on other simulation benchmarks, such as RoboTwin, may be needed to validate transfer across different embodiments.
- The experimental presentation may benefit from reorganization. The tables should distinguish categories of models designed for different purposes, since their evaluation settings differ. The paper should also clearly specify its own evaluation setting and explain how its strengths and weaknesses compare with those of the various baselines across different dimensions.
Questions for authors
- Lightweight WAMs are similar to diffusion policies in many respects. Given this similarity, what are the key methodological differences between the proposed approach and diffusion policies, and where might its gains primarily come from?
- Could the latency comparisons across methods be more detailed? Comparisons of training costs would also be useful, as lower training costs may be an important advantage of lightweight WAMs.
3 comments
Reply to the authors
Thanks for your reply, it addresses some of my questions. I still keep my rating and confidence.
Thank you for taking the time to review our response. We appreciate your feedback and are glad that it addressed some of your questions. Could you share which remaining concerns are most important to your assessment? This would help us focus our follow-up on the points that need further clarification. We would be happy to address them directly.
Response to Wkj9: Benchmark Coverage, Methodological Differences, and Efficiency
We thank the reviewer for the constructive suggestions on figure quality, cross-embodiment coverage, and comparison dimensions, and have revised the paper accordingly. All references below point to the revised paper and appendices.
(1) W1: Figure quality and vector graphics. Following the comment, we improved the figures as follows. We redrew the event curves and routing heatmap in Figure 10 (p. 28) as vector graphics, enlarged labels and legends, and separated the event-axis label from the wrist image. The comparison plot beside Table 1 (p. 7) now uses vector markers and offset/numbered labels to reduce overlap. Figure 2 (p. 4) clarifies the robot input/output interfaces and adaptation regimes. The duplicate comparison panel was removed from Figure 1 (p. 2).
(2) W2: Additional cross-embodiment evaluation. Following your suggestion, Table 31 (p. 42) adds a RoboTwin target-embodiment comparison on 10 held-out target tasks, with 50 initial states per task and three seeds (1,500 trials per method). LiteC-WAM achieves 90.20% mean success, with a seed-level 95% t confidence interval of [87.43%, 92.97%], versus 70.60% [69.61%, 71.59%] for Octo and 67.20% [66.21%, 68.19%] for Diffusion Policy.
This complements the physical SO-ARM101 evaluation, which reports 55/67 successful trials (82.09%; Table 15, p. 29). We distinguish these task-completion results from ARX5's offline action-agreement metric (Table 7, p. 17); the latter is not a closed-loop success rate.
(3) W3: Organization, evaluation scope, and comparison dimensions. Table 1 (p. 7) separates action-diffusion, generalist/vision-language-action, and video/world-model-based policies. Table 2 (p. 8) distinguishes spatial/keypose prediction from diffusion-based trajectory generation, noting that categories can overlap. Both tables identify published source protocols separately from our original custom evaluations.
Appendix N, Table 24 (p. 38) consolidates our task counts, initial states, model configurations, and metrics: five-task LIBERO success, 15-task RLBench development success, physical SO-ARM101 completion, and ARX5 offline agreement on the model-selection split.
For direct comparisons, Table 30 (p. 42) evaluates LiteC-WAM, Octo, and Diffusion Policy with matched tasks, demonstrations, observations, action interfaces, training budgets, and test states. On all 40 LIBERO tasks, their scores are 89.55%, 82.20%, and 78.50%, respectively. This comparison uses one seed per method; LiteC-WAM's separate three-seed full-suite result is 89.40% [85.85%, 92.95%] (Table 29, p. 41). We therefore limit superiority claims to the matched settings and avoid ranking methods across incompatible published protocols.
(4) Q1: Differences from diffusion policies and sources of gains. We agree that both approaches generate action chunks. LiteC-WAM uses flow matching with an eight-step Euler solver (Equation 2, p. 4), whereas Diffusion Policy iteratively denoises action chunks. The additional mechanism is an action-conditioned predictive branch: sparse dynamics experts predict future latent features and events, and the LIBERO feedback head converts these predictions and routing information into an action residual (Equations 3-6, p. 5; Appendix O, p. 39).
The evidence separates three effects. First, with weights, tasks, and initial states fixed, supplying joint predictive feedback raises success from 319/480 to 353/480 (+7.08 pp; Table 3, p. 9). Second, matched Top-2 routing reduces active parameters from 46.68M to 32.40M (30.6%) with 50/120 versus 49/120 successes (Table 13, p. 27). Third, adapter-based ARX5/RLBench adaptation retains 48/50 successes on the original LIBERO tasks (Table 11, p. 22).
These findings support feedback, sparse computation, and modular adaptation in their tested settings. They do not isolate a causal advantage of flow matching over diffusion, nor establish that prediction supervision alone improves control; Table 13 shows lower prediction error but no success improvement from adding predictive objectives in that comparison.
(5) Q2: Latency and training costs. Appendix P, Table 25 (p. 39) reports synchronized timing on one L40S with batch size 1, covering preprocessing through action output. For LiteC-WAM/Octo/Diffusion Policy, mean latency is 21/42/78 ms, P95 latency is 26/51/92 ms, and peak memory is 4.1/5.4/6.8 GB. These measurements cover policy calls, not the complete physical control cycle.
The same table separates shared training, adaptation, and overhead: LiteC-WAM uses 68+24+4=96 GPU-hours; Octo uses 184+24+8=216; Diffusion Policy uses 140+24+4=168. In these configurations, the reported LiteC-WAM total is 55.6% lower than Octo and 42.9% lower than Diffusion Policy. Table 9 (p. 21) separately documents stage-local training records.
We thank the reviewer again for helping improve the figure presentation, evaluation coverage, and efficiency reporting.