- Rating
- 1
- Confidence
- 4
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
This paper proposes FReD-VLA, a hybrid vision-language-action policy that first generates an action proposal with flow matching and then applies diffusion-based refinement through an Action Distribution Calibrator. The main motivation is to combine the low latency of flow-based generation with the accuracy of diffusion policies. The paper reports offline action-prediction results, a small ManiSkill PickCube-v1 study, solver and calibration ablations, and a qualitative dynamic bimanual assembly demonstration on a real robot.
Critical strengths
-
The paper targets an important problem in robot control: reducing action-generation latency without sacrificing fine-grained accuracy. The ADC mechanism is clearly described and provides a simple way to transform a flow proposal into an input compatible with a diffusion denoiser.
-
The offline evaluation includes latency measurements, Flow-NFE sweeps, and ADC-fraction ablations. Under the reported setup, the hybrid method obtains lower Joint MAE than one-step Flow and similar latency to the selected multi-step Flow baseline.
-
The manuscript is generally well organized, and the authors make a meaningful effort to state the assumptions and limitations of the theoretical analysis. The inclusion of closed-loop simulation and a real-robot demonstration is also useful as an initial feasibility check.
Critical weaknesses
-
The central motivation is not convincingly established. Flow matching can itself use multiple integration steps, so the paper needs to demonstrate why a diffusion refiner is preferable to simply using a stronger or multi-step Flow policy. The reported comparison with Euler-8 is not sufficient to isolate this question. In particular, the hybrid method combines two separately trained models and may benefit from additional model capacity, whereas the Flow baselines do not appear to receive a comparable parameter or training-budget allocation. The results therefore do not clearly show that diffusion refinement is intrinsically better than additional Flow computation.
-
From the reported numbers, Flow Euler-1 and Euler-8 imply approximately 4.6–4.7 ms per Flow evaluation, whereas Pure Diffusion-2 and Pure Diffusion-5 imply an incremental cost of approximately 32.6 ms per diffusion evaluation. Thus, a diffusion call is roughly seven times more expensive than a Flow call. This is difficult to reconcile with the statement that Pure Diffusion, Pure Flow, and FReD-VLA share the same DiT multimodal backbone. If the same backbone is executed on the same action chunk with the same conditioning, the per-call costs should be broadly comparable; the difference should not normally be an order of magnitude. The discrepancy may indicate that the compared methods use different action-generation modules, different parameter counts, different sequence lengths, different caching or conditioning paths, or non-equivalent timing procedures, but the paper does not specify which explanation applies.
-
The reported 37.0 ms latency for FReD-VLA is numerically close to one Flow call plus one diffusion call. Therefore, its speedup over five-step diffusion is primarily obtained by replacing four expensive diffusion calls with one such call and one much cheaper Flow call. This does not establish that Flow matching is intrinsically faster at the same number of steps, nor does it demonstrate that diffusion refinement is preferable to an equivalently budgeted multi-step Flow policy. The paper should provide synchronized per-module timing, exact architectures and parameter counts, FLOPs, action-chunk dimensions, precision and batching settings, feature-caching details, and end-to-end latency including multimodal encoding.
-
In the ManiSkill experiment, only nine fixed rollouts are used, and the Flow-conditioned variant achieves the same success rate as Pure Flow. The reported 10.8 mm distance result appears to correspond specifically to the Flow-conditioned Step50 variant, rather than unambiguously to the default FReD-VLA configuration. This makes the main task-level improvement claim difficult to evaluate.
-
No independent trial counts, success rates, failure cases, or controlled comparisons against Flow-only and Diffusion-only policies are reported. As a result, the evidence does not support broad claims about practical robustness or dynamic bimanual manipulation performance.
-
The theoretical analysis assumes a conditional Gaussian action distribution, an ideal denoiser, deterministic first-order sampling, and simultaneous diagonalization of the action covariance and temporal-difference operators. The appendix correctly acknowledges these restrictions, but the resulting bounds do not explain the behavior of the learned multimodal policy and do not establish that diffusion refinement should outperform additional Flow steps in the actual setting.
-
Only nine trajectory anchors with multiple stochastic samples are used in the offline evaluation. These samples assess stochastic variation but do not provide broad task or state coverage. In addition, the fairness of external baselines is difficult to assess because their training data, adaptation procedures, checkpoints, parameter counts, and computational budgets are not specified in sufficient detail.
Questions for authors
-
The main question is why diffusion refinement is needed at all when the Flow policy can be evaluated for additional integration steps. Can the authors provide a matched comparison against Flow policies with comparable parameter counts, training budgets, and wall-clock cost, including optimized multi-step solvers or a larger Flow model?
-
How can the authors reconcile the approximately seven-fold difference between the per-evaluation Flow and diffusion latency with the claim that the methods share the same DiT multimodal backbone? Which modules are shared, which modules are separate, and how do their parameter counts, sequence lengths, FLOPs, caching behavior, and timing boundaries compare?
-
How many independent real-robot trials were performed for each behavior? Please provide success rates, failure categories, and comparisons with Flow-only and Diffusion-only policies under the same demonstrations and execution layer.