- Rating
- 3(+1)
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper proposes Kinematics-informed VLA,which is a flow-matching robot policy. it treats the policy's end effector action chance as a noisy kinematic observation of an underlying joint-increment trajectory. The paper has several contributions:
- The paper uses Jacobian observation model and differentiable Kalman/RTS inference to estimate smooth joint-increment trajectories, then map them back to action space with bounded corrections.
- It interleaves correction with flow-matching updates and support sparse schedules that trade computation for performance, while keeping the base policy frozen.
- the paper evaluate the controlled end-pose VLA comparison on eight RoboTwin 2.0 tasks and four real-robot tasks, measuring task success and command-level motion.
Critical strengths
The research problem is interesting. Though I have seen some same topic papers already in this field. The integration of joint space kinematic consistency into intermediate flow matching is kind of novel.
Critical weaknesses
What's the intuition to insert Kalman smoothing between flow machine steps. The generalizability needs further investigation and demonstration. Are you training separate models for different tasks? or train a single model for different tasks?
Questions for authors
-
Have you ever tried pi_0.5 as baseline? I think pi_0.5 is considered as a stronger model than pi_0. but table 1 only compare pi_0. I am wondering if Pi_0.5 this paper can beat the pi_0.5 model.
-
Evaluating the method on another flow-matching policy could help demonstrate its generalizability beyond pi_0 backbone.
-
It may worth testing on diffusion based policy
-
Looks like this model takes both language instruction and RGB image as input, are they both input of the frozen flow policy module. I am wondering if it working well without a language encoder?
Thanks for the detailed responses and additional experiments. I appreciate the new results with π0.5 and the comparisons using the same number of correction steps. These address some of my questions and provide stronger evidence that the method can help. However, I’m still not convinced that the full pipeline is sufficiently justified.
My main concern is how much the kinematic component actually adds. The same interleaved smoother in action space gets 48/31, compared with 51/35 for the full method—a difference the response acknowledges is within noise. The analytic Jacobian also performs almost identically to the learned one. Given that these ablations are mainly on one task, I still find it hard to tell which parts of the pipeline are necessary and whether the added complexity brings a reliable benefit over simpler smoothing.
I’m also still concerned about how intermediate flow samples are treated. The response acknowledges that these drafts have a progress-dependent shrinkage that the observation model does not account for. Giving early drafts less weight does not resolve that mismatch. The new experiments suggest that interleaving corrections helps on Turn Switch, but they do not fully justify this particular observation model. Correcting the predicted endpoint seems like a relevant alternative, but it remains untested.
The practical benefit under normal execution also remains unclear to me. The simulation gains across two backbones are encouraging, but clean real-robot success only changes from 68.5% to 71.0%, without a statistically significant improvement. The larger gains under an injected disturbance are useful evidence, but they do not show how often this issue causes failures in normal execution. The gain also disappears at 50 flow steps on Turn Switch, which leaves questions about how broadly the method is useful.
Finally, I still find the paper difficult to follow. The rebuttal makes several points clearer, but the paper itself needs to explain more directly why each component is needed and which results support it.
Overall, I appreciate the authors’ efforts, but my main concerns remain unresolved, so I will keep my original rating