- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
TextMani connects foundation-model task reasoning to robot execution through explicit constraints and a shared grounding, solving, and control backend. Experiments in simulation and on real robots compare multiple models, separately evaluating initial execution, blind failure diagnosis, and repair given a failed subgoal. The main contributions are an inspectable common interface and a cross-model study of execution and correction.
Critical strengths
- The common constraint specification and execution backend make intermediate outputs inspectable and comparable across models, extending the analysis beyond final success rates.
- The experiments span multiple models, simulation, and real robots, with execution, blind diagnosis, and known-subgoal repair evaluated separately. Differences between error recognition and subsequent subgoal matching provide concrete evidence about the diagnostic bottleneck.
Critical weaknesses
- Constraint-level attribution and selective repair are not evaluated at the claimed granularity. Equations (5)–(8) use stable addresses to identify constraints for revision while preserving the rest, and this is listed among the main contributions. However, diagnosis measures error detection and agreement with a reference subgoal, while robot repair regenerates the entire specification of an already identified failed subgoal. The recovery rates of 24.5% and 47.7% establish that subgoal specifications can be repaired, but do not test erroneous-constraint localization, selective editing, or preservation of unaffected constraints. The distinctive repair mechanism therefore remains a method description rather than an empirically established contribution.
- The shared execution interface is insufficiently defined. The paper represents features, constraints, and mathematical expressions as a tuple and maps it to robot targets through a shared backend. It does not define a complete specification grammar, the scope and validity rules of MathIR, or the compilation and numerical-solving procedure. Figure 2 gives a useful example but does not replace these definitions, and the appendix mainly adds evaluation and accounting details. These omissions prevent readers from checking the executable contract followed by model outputs, identifying how much behavior is supplied by the backend, and reconstructing the mapping from constraints to motion targets.
Questions for authors
- Please provide an actual constraint-level repair trace showing the identified constraint addresses, expressions before and after revision, and the constraints left unchanged. Which reported results evaluate repair satisfying Equation (8)? If all current statistics come from regenerating the failed subgoal specification, please identify which fine-grained repair functions have been implemented and validated?
- Could you give a complete example for the grasping task in Figure 2: the actual structured model output, its compilation and solution into numerical targets, and the handling of invalid expressions or conflicting constraints? Please also identify which geometric features and action templates are supplied by the system and which elements the model selects or generates.