- Rating
- 1
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
Existing VLA models often focus on completing the task but may not follow fine-grained requirements. The authors formulate this problem as "execution-constraint following". They use the "bi-level RVQ-VAE" to decompose actions into "goal-level" and "execution-level", where the former represents the task objective and the latter represents execution constraints. The authors also construct datasets with fine-grained execution constraints, including LIBERO-based simulation datasets and a real-world Realman-75 robot dataset, and achieve promising results on these benchmarks.
Critical strengths
- The authors focus on the problem of fine-grained execution constraints in VLA models. Rather than merely requiring robots to finish high-level task goals, this setting further requires the model to understand the task details.
- I believe this paper shows substantial human involvement; at least in some aspects, the authors did not simply delegate all of the work to AI.
Critical weaknesses
The authors do not provide an AI USE STATEMENT. Meanwhile, the paper contains several serious inconsistencies and figure issues, which raise substantial concerns about whether the manuscript was carefully checked, including:
- Figure 4 cheats reviewers and contains multiple inconsistencies between the bar heights and the reported values. Numbering the groups from left to right, with 1–3 on the top row and 4–5 on the bottom row:
- In (1), there are visible image-editing artifacts around 76.5 and minor similar artifacts above 71.2 (I believe this is strong evidence for subjective editing);
- In (2), the bar labeled 63.2 is clearly below the midpoint of 50 and 75, i.e., 62.5;
- In (3), the bar labeled 61.5 is lower than the 61.5 bar in (2);
- In (4), the bar labeled 92.6 is higher than the one labeled 93.2;
- In (5), the bar labeled 92.2 is higher than the 93.2 bar in (4).
- The method name is inconsistent across figures. Figure 1 refers to the proposed method as “Kinematics-Aware VLA (Ours),” while the paper uses “ExecVLA”; Figure 4 instead uses “KineVLA (Ours).”
For the paper:
- The mathematical formulation is not sufficiently clear, and this's not conducive to the understanding of the paper:
- is introduced but not defined.
- The roles and architectures of and are not specified.
- is used for both robot time steps and text/action token positions, while denotes sequence length but also appears in the undefined , which seems to refer to text or reasoning.
Questions for authors
- Could the authors explain the inconsistencies between the reported values and the bar heights in Figure 4? Please provide the exact numerical results and clarify how the figure was generated.
- Could the authors provide a more detailed analysis of the individual contributions of and ?
- Given the number of inconsistencies identified above, could the authors commit to a thorough re-check of the manuscript, including the figures, notation, and methodological descriptions, and ensure that these issues are carefully addressed in the revision?