- Rating
- 3
- Confidence
- 2
- Informativeness
- 3
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
The paper proposes a vision-language-action system for high-speed manipulation. The authors train a policy based on Qwen3-VL-4B and add three components. For training, they propose an intra-chunk smoothness and cross-chunk continuity loss. For inference, they use the same loss for gradient guidance. For execution, they utilize dynamics-aware trajectory generation and tracking under motion constraints. Experiments verify that the proposed DA-VLA achieves better performance and throughput across tasks than the baseline methods.
Critical strengths
- The problem is meaningful. Rather than focusing only on VLA inference latency, the authors consider the training objective, trajectory continuity, dynamics, and other factors within a unified high-speed system.
- The proposed system is comprehensive and sound. From the policy to the controller, the overall design is well integrated.
- The experiments are extensive, covering different tasks and baseline methods, and validate the effectiveness and efficiency of the proposed DA-VLA.
Critical weaknesses
- The ablation study is somewhat limited. The paper could benefit from separately evaluating motion capability prediction and trajectory interpolation, as well as dynamics-aware regularization and guidance.
- It is unclear why MinJerk produces much larger acceleration and jerk than linear interpolation in Table 2. The paper could benefit from a clearer explanation of this result.
- It is unclear why DA-VLA requires training a separate policy based on Qwen-VL. Could it instead start from a strong VLA such as π0.5? In addition, the proposed execution layer could potentially be directly applied to existing VLA models such as π0.5. Could such policies also benefit from it?
Questions for authors
See weakness 1-3.
4 comments
W2
Thank you for the question. The results in Table 2 arise from the relationship between the boundary conditions of piecewise MinJerk and high-frequency action references: the MinJerk evaluated in this paper constructs a quintic curve separately for each pair of adjacent VLA position points, with zero start and end velocity and acceleration, whereas Linear maintains a constant slope within each interval. Thus, the two methods place velocity changes differently: piecewise MinJerk accelerates and decelerates within every short interval, while Linear's velocity changes occur mainly at the boundaries between adjacent intervals.
Specifically, at a 50 Hz action-reference rate, MinJerk uses , where , , and ms. Given the start and end positions and zero velocity and acceleration at both ends, it minimizes the integrated squared jerk; Linear uses different boundary conditions, so its discrete transmitted sequence can have a lower jerk RMS without contradicting this optimality result. For example, in one segment of the original replay with a displacement of 0.019929 rad, the average velocity is approximately 0.996 rad/s in each interval for Linear, whereas for MinJerk it is approximately 0.413, 1.580, 1.580, and 0.413 rad/s, reflecting the acceleration and deceleration within each 20 ms interval.
Statistics over the same 10 trajectories further locate this difference:
| Metric | Linear interpolation | Piecewise MinJerk | DA-VLA |
|---|---|---|---|
| RMS of transmitted-velocity changes at 50 Hz point boundaries (rad/s) | 0.333 | 0.164 | 0.102 |
| RMS of transmitted-velocity changes within inter-point intervals (rad/s) | 0.089 | 0.506 | 0.084 |
| Transmitted jerk RMS () | 1,522.97 | 10,361.77 | 935.78 |
Piecewise MinJerk reduces velocity changes at point boundaries, but introduces larger velocity changes within the intervals. This also explains why its acceleration RMS is higher than Linear's: 54.46 versus 11.10 . These comparisons use the same discrete transmission and statistical protocol.
This comparison shows that the acceleration and jerk differences between MinJerk and linear interpolation should be interpreted in light of their respective boundary conditions and where velocity changes occur. DA-VLA uses cross-segment trajectory interpolation to handle transitions between adjacent action points, making velocity changes smoother during continuous execution instead of repeatedly performing a motion that starts and ends at rest within every short interval.
W3
Thank you for the suggestions. DA-VLA's design does not depend on the Qwen-VL backbone and can also be adapted to existing VLAs with the corresponding training and sampling interfaces. We chose Qwen3-VL-4B to establish a reproducible policy-execution research pipeline. Regarding whether the execution layer can be applied directly to and provide benefits, in the main table already uses our execution layer, and the new MinJerk comparison further validates this benefit.
First, choosing Qwen3-VL-4B allows us to connect public robot data, target-robot adaptation, continuous-action learning, and real-robot execution in one pipeline. Its accessible action head and training workflow support a unified implementation of dynamics-aware regularization and guidance, and provide a basis for open, reproducible research across the full pipeline. This is our research-design rationale for using this backbone; transferring the policy-side methods to existing VLAs such as requires integrating the corresponding regularization and guidance into their training objectives and action-sampling interfaces.
Second, the execution layer receives outputs from different VLAs through a shared action-reference interface. and the other baselines in the main table already use the same motion capability prediction, trajectory interpolation, and dynamics-compensated trajectory tracking, while retaining their respective policy-update mechanisms. We further fix the checkpoint, policy-update mechanism, and low-level tracking setup at the 100 Hz operating point on Table Clearing, and replace the combination of motion capability prediction and trajectory interpolation with piecewise MinJerk. With our execution combination, SR is 78% and ETS is 8.20; with MinJerk, they are 68% and 7.27, respectively. This directly demonstrates its value for high-speed execution with an existing VLA.
In summary, DA-VLA provides both a reproducible policy-execution research pipeline and an execution layer that existing VLAs can use. The deployment of and the new MinJerk comparison demonstrate the transferable benefits of the execution design, while the main-table comparisons under a shared execution layer further support the contribution of our coordinated policy and execution design.
Thanks for the response. It addressed most of my concerns. Therefore, I would llike to maintain my score to support the paper.
We appreciate your continued support for the paper. Your questions helped us explain more clearly what each component contributes, why the interpolation methods behave differently, and how the execution layer can benefit other VLA policies. Thank you for taking the time to follow up.
W1
Thank you for suggesting that we distinguish the contributions of the components more clearly. We separately evaluate dynamics-aware regularization and guidance on the policy side, and further distinguish the roles of motion capability prediction and trajectory interpolation on the execution side through a capability-bound comparison and an analysis of the interpolation submechanisms. In the original manuscript's combined ablations, disabling both dynamics-aware regularization and guidance changes the average SR across the five tasks from 80.6% to 51.8%; replacing the combination of motion capability prediction and trajectory interpolation with piecewise MinJerk changes the average SR to 70.8%. Building on this, we add experiments that independently toggle training regularization and inference guidance, as well as a capability-bound comparison that keeps trajectory interpolation unchanged. Together with the tracking-error, motion-smoothness, and latency analyses already reported in Table 2, these experiments associate the combined gains with the specific roles of each stage.
First, for dynamics-aware regularization and guidance, we independently toggle training-stage regularization and inference-stage guidance on Book Insertion. The results are as follows:
The results show that enabling either factor when the other is off also yields consistent improvements. These results support their complementary roles: dynamics-aware regularization improves the predicted action distribution, while guidance adjusts the action chunk generated at each update according to the current observation and the motion already committed for execution. We also separately remove intra-chunk training smoothness on Book Insertion while retaining cross-chunk continuity and inference guidance. With intra-chunk smoothness enabled, the lateral-deviation RMS is lower at all three local reference scales, and the back-and-forth rate under a 5 mm threshold decreases from 0.701 to 0.470 times/s. This provides further evidence of the motion-quality benefits of an individual term in the training regularizer.
Second, regarding motion capability prediction and trajectory interpolation, the former provides state-dependent acceleration bounds, while the latter uses these bounds to connect discrete action targets. The piecewise MinJerk evaluated in the paper does not use the predicted bounds; the original MinJerk ablation evaluates the task-level benefit of the combined motion capability prediction and trajectory interpolation. To further test the role of capability prediction, we keep trajectory interpolation and the low-level tracking setup fixed, and compare results with and without state-dependent acceleration bounds. The mean acceleration RMS and the estimated torque-demand RMS reduces approximately 12.6% and 4.7%, respectively. This evaluates the role of the capability bounds separately from the task-level benefit of the full interpolation combination.
Finally, the main text already gives a detailed analysis of the mechanisms and roles of the execution-layer components. Table 2 further analyzes trajectory interpolation and its submechanisms in terms of tracking error, motion smoothness, and latency; all interpolation methods use the same underlying dynamics-compensated trajectory tracking setup. Chunk Fusion corresponds to the intermediate-reference insertion and continuous bridging at larger target changes in Figure 3 ("bridge large gap with c3"). Inheritance corresponds to "terminal velocity estimation": it lets a new segment continue the motion trend already in progress, and computes the next desired velocity jointly with the trend of subsequent targets. In the original manuscript, removing Chunk Fusion increases acceleration and jerk RMS by 18.1% and 7.1%, respectively; removing Inheritance increases alignment latency by 126.2%. These results further associate the gains from trajectory interpolation with continuous bridging and motion-state inheritance. The specific design and how these components connect are described in Appendix B.
These analyses separately present the roles of dynamics-aware regularization and guidance, motion capability prediction, trajectory interpolation, and its submechanisms: training regularization improves action generation, guidance adapts to the current handoff state, capability prediction provides state-dependent bounds, and trajectory interpolation connects discrete targets into continuous references. The independent toggles, bound comparison, and interpolation-submechanism analysis together explain the task-level gains of the complete combination and each stage's contribution to continuous execution.