- Rating
- 1
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 1
Read review
Paper summary
This paper proposes VLA-MOPD, a multi-teacher on-policy distillation protocol that consolidates multiple VLA specialists into a single shared policy by querying task-specific teachers on student-induced observations and intermediate flow states. While the research direction of VLA policy consolidation is important, the paper currently suffers from incremental technical novelty and insufficient experimental support.
Critical strengths
-
The paper addresses multi-task VLA capability consolidation and continual evolution, which is of strong practical significance.
-
Supervising on student-induced states intuitively mitigates distribution shift compared to offline distillation.
-
The evaluation spans simulated environments (LIBERO, RoboTwin 2.0) and real-world experiments on a Piper robot, demonstrating applicability across diverse settings.
Critical weaknesses
-
The proposed methodology primarily combines existing ideas from DAgger, VLA-OPD, and Flow-OPD. The independent contribution and necessity of per-flow-step transition matching have not been fully substantiated, especially on tasks with high baseline success rates.
-
The ablation studies rely heavily on LIBERO suites where performance is close to saturation. Here, VLA-MOPD achieves only a marginal improvement (~0.75 percentage points) over endpoint distillation.
-
On RoboTwin 2.0 and the real-world Piper robot, the consolidated student policy consistently lags behind the specialist teachers, indicating that the method has not yet proven its ability to achieve lossless capacity consolidation across multiple specialists.
Questions for authors
-
Compared with endpoint action distillation, VLA-OPD, and Flow-OPD, does per-flow-step transition matching yield consistent and significant independent gains on non-saturated or highly compositional tasks?
-
What are the primary bottlenecks causing the student to slightly surpass teachers on LIBERO while lagging behind by 4–6 percentage points on RoboTwin and Piper? Is it due to task interference, dual-arm coordination challenges, long action horizons, or model capacity limits?
-
What is the precise primary objective of this method—performance improvement, capability retention, or specialist compression? Could the authors explicitly report teacher–student capability coverage, forgetting rates, as well as the additional storage and inference overhead?