- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
StreamingWAM adapts streaming diffusion to world action models using a persistent future-action buffer with chunk-dependent noise levels. Each steady-state replan performs one Euler update, executes the least-noisy block, shifts the buffer, and appends fresh noise. A clean executed-action prefix and dense visual history provide context; a separate multi-step warm start initializes the buffer. The contribution is the adaptation and integration of rolling, variable-noise diffusion into WAM control. Evaluation covers LIBERO, LIBERO-Plus, RoboTwin 2.0, and six real-robot tasks. The reported results are promising, but configuration inconsistencies and incomplete attribution limit my assessment.
Critical strengths
The integration is practical and coherent for computationally expensive WAMs. A persistent buffer, chunk-wise noise staircase, executed-action prefix, and visual history provide a reasonable way to amortize denoising while retaining context across replans. The paper appropriately cites Streaming Diffusion Policy and Diffusion Forcing; the value lies in adapting these mechanisms to joint video–action modeling. Reporting both initialization and steady-state latency makes the deployment costs more interpretable: simulation/real-robot warm starts take 406.2/436.8 ms, versus 72.9/57.3 ms in steady state (Sections 3.1–3.3; Table 7).
The evaluation is broad and includes substantial reported gains. LIBERO-Plus uses the full 10,030-episode protocol, RoboTwin covers all 50 tasks, and the real-robot study includes 50 trials for each of five manipulation tasks plus 50 timed whack-a-mole sessions. StreamingWAM reports 79.4% on LIBERO-Plus and 98.7% on LIBERO. Across the five real-robot manipulation tasks, it achieves 168/250 successes versus 120/250 for the strongest listed baseline, including 32/50 and 20/50 on the two moving-object tasks. These results make the approach worth serious consideration, subject to the comparison issues below (Tables 1 and 10–12; Appendix A.3).
Critical weaknesses
- The configuration of a central baseline is inconsistent across the paper. Table 3 reports Fast-WAM-Joint at 61.03% for and 68.78% for . Table 9 is labeled but reports Joint at 68.8%; Table 6 lists for LIBERO Joint Async. Here denotes actions executed per replan. The separate “shadow configuration” qualification applies to the real-robot RTC-v2 row and does not resolve the simulation settings. I cannot determine which label or result is incorrect. Consequently, the headline 79.4% versus 68.8% comparison currently lacks a reconciled execution protocol and cannot establish a clearly -matched gain. The equal-update LIBERO ablations remain positive evidence, but the main comparison needs clarification (PDF pp. 9 and 13–16).
- The evidence does not fully separate architectural benefits from training budget, execution configuration, or component interactions. At , prefix plus dense history adds 4.80 percentage points, the staircase alone adds 0.36, and their combination adds 18.33; this shows a strong interaction rather than the “additive” effect stated in Figure 7. The prefix/history bundle also prevents attribution to either component separately. LIBERO matches 83,400 updates, but RoboTwin adds 135,776 streaming updates after a 135,776-step Joint checkpoint, and the real-robot model adds 30,000 after 20,000 Joint updates. These gains therefore cannot be attributed entirely to streaming. The latency explanation also needs qualification: the real-robot 6.4× comparison uses 10-step Joint at 368.6 ms, whereas dynamic-task Joint Async uses one step at 46.8 ms, faster than StreamingWAM’s 57.3 ms. The dynamic success gains remain meaningful, but speed alone does not explain them. Likewise, smoother commands and computation-based time to first action do not establish which mechanism causes the success improvements (Tables 3 and 5–8; Figure 7; Appendix E.3). I currently lean toward rejection. Resolving the baseline configurations and confirming a substantial LIBERO gain under a reconciled, matched protocol could move my recommendation toward acceptance. Matched-total-update results for RoboTwin/real-robot experiments, or appropriately narrower attribution, would further strengthen that case.
Questions for authors
Essential clarification: What , denoising-step count, checkpoint, and execution mode produce the 68.8% Joint result in Tables 1 and 9? How should this result be reconciled with Tables 3 and 6? Component attribution: Do existing results isolate the clean action prefix from dense visual history? Otherwise, can attribution be restricted to their combination and the “additive” description revised to reflect the observed interaction? Training and deployment comparison: Are matched-total-update Joint controls available for RoboTwin and the real robot? If not, can the architecture-attribution claims be narrowed, and latency comparisons explicitly tied to the actual configurations used for static and dynamic success evaluations?
9 comments
Response to W2/Q2: Component Attribution and Complementary Effects
Thank you for identifying the attribution issue. We agree that "additive" is inaccurate and will replace it with "complementary." The new ablations separate visual history from the action prefix and show contributions from both under the same staircase setting; below we report the controls and clarify the limits of this attribution.
We agree that the original manuscript did not sufficiently separate visual history from the clean action prefix. The additional ablations and their interpretation are given below.
1. Correcting the "additive" interpretation
Your concern about "additive" is valid. In the original fixed-K=4 comparison, the historical-context combination improves success by 4.80 percentage points, staircase alone by 0.36 points, and the full combination by 18.33 points. This is not a simple sum of two independent improvements. We will replace "additive" with "complementary" to reflect the observed interaction more accurately.
2. Separate ablations and explicit inference settings
All configurations below use the same Fast-WAM backbone, initialization, training budget, and task-evaluation protocol. Configurations without historical frames still receive the current image. Configurations with staircase use one update per steady-state replan; those without staircase use ten denoising steps per replan. Success rates (%):
| Visual history | Action prefix | Staircase | K=4 | K=8 |
|---|---|---|---|---|
| Yes | No | No | 64.90 | 72.82 |
| No | Yes | No | 63.10 | 73.15 |
| Yes | Yes | No | 65.83 | 73.71 |
| Yes | No | Yes | 77.87 | 76.43 |
| No | Yes | Yes | 77.38 | 76.82 |
| Yes | Yes | Yes | 79.36 | 78.73 |
3. Individual contributions of the two context sources
Within the staircase setting, both context sources contribute to the full model. Removing visual history lowers success from 79.36% to 77.38% at K=4 and from 78.73% to 76.82% at K=8, corresponding to drops of 1.98 and 1.91 percentage points. Removing the action prefix lowers success to 77.87% and 76.43%, respectively, corresponding to drops of 1.49 and 2.30 points.
4. Cross-K behavior and scope of attribution
The one-step rolling staircase configurations also show smaller performance differences between the two evaluated execution horizons. With both visual history and the action prefix retained, the ten-step non-staircase configuration differs by 7.88 points between K=4 and K=8, whereas the one-step rolling configuration differs by 0.63 points. This is consistent with the broader K sweep in Figure 3. We explicitly report the different inference-step settings rather than treating this as a comparison that varies only one component.
In summary, historical context supports task performance, the one-step rolling staircase scheme is more stable across the evaluated execution horizons, and the full method combines these benefits. The larger gain at fixed K=4 should not be interpreted as the gain between each model's best configuration. We will add the separate ablations and revise the component attribution and "additive" wording accordingly. Given the rebuttal time constraints, the new separated ablations currently cover K=4 and K=8; if you consider it necessary, we will extend the sweep to additional K values. Thank you for helping us clarify these contributions.
Response to W3/Q3: Matched Training Budgets - RoboTwin
Thank you for requesting a matched-total-update Joint control. On RoboTwin Clean, StreamingWAM achieves 84.2%, versus 80.3% for continued-training Joint at the same total training budget. This response reports the RoboTwin control, its training curve, and the scope of the conclusion.
1. Shared initialization and matched training budgets
We agree that comparing StreamingWAM after additional training with a Joint checkpoint that has not received those updates does not isolate the effect of the method. To address this, we add continued-training Joint controls starting from the same Joint initialization, using the same data and batch size, and receiving the same number of additional updates. The comparison is therefore between continuing Joint training and switching to StreamingWAM training, not between unequal total update counts.
For RoboTwin, both branches start from the Joint checkpoint trained for 135,776 updates and receive a further 135,776 updates, totaling 271,552 updates, with a global batch size of 64. Evaluation covers all 50 tasks with 100 episodes per task, or 5,000 episodes. Both branches use K=8. Joint uses ten denoising steps, while StreamingWAM uses one steady-state update.
| Model / stage | Initial Joint updates | Additional updates | Total updates | Clean success rate |
|---|---|---|---|---|
| Initial Joint checkpoint | 135,776 | 0 | 135,776 | 80.4% |
| Continued-training Joint | 135,776 | 135,776 | 271,552 | 80.3% |
| StreamingWAM | 135,776 | 135,776 | 271,552 | 84.2% |
At the matched total update count, StreamingWAM improves over continued-training Joint by 3.9 percentage points.
2. Training curve and interpretation
The RoboTwin Clean training curve will be provided in the updated supplementary material at Rebuttal_Figures/RoboTwin_training_curve.png. It traces the initial Joint training and the two subsequent branches. The horizontal axis is cumulative training updates, and the dashed line marks the end of the shared initial Joint training. The 56.4% point corresponds to switching to streaming deployment before any additional streaming training; it should not be confused with the 80.4% obtained using Joint execution at the same training-update count.
Joint reaches approximately 80% success late in the initial training stage and remains around that level during continued training. StreamingWAM also fluctuates during adaptation, but finishes at 84.2%, compared with 80.3% for Joint at the same total training budget. Thus, in this setting, the improvement cannot be explained solely by the number of additional training updates.
3. Scope of the additional RoboTwin evidence
We prioritize Clean to examine performance as training continues. Success rates in the original Random setting were generally lower, making this trend harder to distinguish within the available evaluation budget. We have not completed the matched-budget Random evaluation within the rebuttal period; the RoboTwin conclusion above is limited to Clean.
In summary, the added continued-training control retains a performance advantage for the complete StreamingWAM configuration on RoboTwin Clean at equal total update counts. The inference settings are stated explicitly, and the separate component ablations address attribution within the full design. We will incorporate the results and training curve into the revision and make the initialization, subsequent training budgets, and evaluation configurations explicit. Thank you for highlighting this important control.
Response to W1/Q1: LIBERO-Plus Baseline Configurations and Matched Comparisons
Thank you for identifying the configuration inconsistencies. The 68.8% result uses K=10, ten denoising steps, and synchronous chunk execution; Table 9's blanket K=4 label and Table 6's simulation "Async" label need correction. Below we reconcile the original results and provide the matched-budget, matched-H/K comparisons requested.
We agree that the original manuscript did not adequately trace each result to its execution configuration. We have rechecked these settings and added baseline evaluations across H, K, and denoising-step counts.
1. Mapping Tables 1, 3, and 9 to checkpoints and configurations
The 68.8% in Tables 1 and 9 uses the official Fast-WAM deployment configuration: H=32, K=10, and ten denoising steps. The 61.03% and 68.78% in Table 3 use the same Joint checkpoint with ten steps at K=4 and K=16, respectively. Table 9's caption did not correctly distinguish the K values of its rows. We will annotate each row with its actual configuration and retain the mapping between original and additional evaluations.
The main Fast-WAM result also uses the official configuration with 83,400 training updates, H=32, K=10, and ten denoising steps; the added H/K sweep focuses on Fast-WAM-Joint.
2. Execution mode in Table 6: simulation versus real robot
LIBERO-Plus uses standard synchronous chunk execution: predict from the current observation, execute the first K actions, obtain a new observation, and replan. The simulation label "Joint Async" in Table 6 is inaccurate. We will rename that row Fast-WAM-Joint and explicitly state synchronous chunk execution and its configuration. The "shadow configuration" concerns the real robot and does not explain these simulation results; the two will be described separately.
3. Complete additional evaluation at matched training budgets
All models below use 83,400 training updates, the same training data and batch size, and the same evaluation protocol. The original H=32 ten-step results at K=4/8 were 61.03%/72.76%; the new evaluations yield 61.33%/70.68%. Evaluation randomness may contribute to these differences. We report old and new results separately and use the new baseline evaluations for the matched comparisons below. We will update the corresponding tables, curves, and analysis while retaining their provenance.
The first five rows share one H=32 Joint checkpoint, the next five share one H=16 Joint checkpoint, and the last two share one StreamingWAM checkpoint. Only evaluation settings vary within each group. StreamingWAM's one step refers to steady-state updates after warm start.
4. Fixed-configuration versus best-evaluated comparisons
Joint performs better at K=8 than at the official K=10 setting in these evaluations; its best result among the listed settings is 70.68% (H=32, K=8, ten steps). Focusing on K=8 with matched H=16, StreamingWAM achieves 78.73%, versus 68.12% and 65.74% for ten-step and one-step Joint: gains of 10.61 and 12.99 percentage points. The matched K=4 comparisons show the same direction of improvement. We will distinguish fixed-configuration comparisons from comparisons of each method's best evaluated setting.
In summary, the performance advantage remains after aligning training budgets and the stated evaluation settings. Thank you for this essential check. We will incorporate the additional results, reconcile the checkpoint/configuration descriptions, and use the separate ablations to discuss the contributions of the full design.