- Rating
- 4(+1)
- Confidence
- 4
- Informativeness
- 3
- Presentation
- 3
- Soundness
- 3
Read review
Paper summary
This paper proposes StandReady, a framework for predicting manipulation-ready terminal standing poses in last-meter mobile manipulation. Given a single egocentric RGB-D observation and a task instruction, StandReady predicts floor-level standing affordances together with the corresponding mobile-base orientations.
Critical strengths
-
The paper addresses a meaningful and practically relevant problem. A navigation-valid pose does not necessarily provide a suitable initial condition for downstream arm execution. Explicitly modeling the relationship between terminal base placement and subsequent manipulation is important for reliable mobile manipulation.
-
The proposed training-time refinement is well motivated and practically appealing. Compared with direct floor-level affordance prediction such as NavAff, StandReady incorporates trajectory-level, embodiment-aware feasibility signals, including reachability, IK feasibility, manipulability, Jacobian conditioning, and base compatibility. These signals are used during training while preserving a simple single-forward inference procedure at deployment.
-
The empirical results provide reasonable support for the proposed idea. StandReady improves the average RoboCasa success rate over NavAff and shows gains across the five evaluated tasks. The reward-component ablations, controlled arm-tracking study, and real-world terminal-pose evaluation further support the claim that unfavorable arm-motion conditions can affect downstream execution. The comparison with Mobi- also demonstrates a clear test-time efficiency advantage.
Critical weaknesses
-
The evaluation scope is still relatively limited. The main experiments focus on five atomic tasks in RoboCasa and use a fixed downstream policy. The paper does not evaluate generalization to unseen tasks, objects, environments, robot embodiments, or substantially different manipulation policies. The real-world study measures whether the terminal pose appears manipulation-ready rather than whether the robot completes the actual drawer-closing or door-closing task. Thus, the current results support the effectiveness of StandReady in the evaluated setting, while broader generality remains less established.
-
The method contains several heuristic design choices that are not fully analyzed. The refinement procedure samples candidates primarily from regions already assigned high affordance scores, which may limit its ability to recover feasible poses missed by the initial VQA prior. The paper does not provide sensitivity studies for the candidate budget, search radius, affordance threshold, reward weights, refinement coefficient, or number of refinement rounds. Stronger comparisons with an oracle feasibility search, a direct analytical IK-based baseline, or direct distillation from the best feasible candidate would also help isolate the contribution of the proposed iterative refinement procedure.
Questions for authors
See weakness.
7 comments
Response to Reviewer NSZ4[Part 2]
The table below summarizes our expanded simulation benchmarking across seen and novel unseen task distributions:
Table R1: Task generalization across seen and novel unseen benchmarks under and XR-1 policies (RoboCasa Seen pools 2,130 episodes across 15 tasks and 3 robot arms; RoboCasa Unseen pools 1,410 episodes across 10 novel tasks and 3 robot arms; ManiSkill3 evaluates 120 episodes across 6 novel tasks with Panda):
| Benchmark Split | Policy | LeLaN | NavAff | GPT-6.1 Sol | N2M | StandReady (Ours) | VLA Baseline |
|---|---|---|---|---|---|---|---|
| RoboCasa Seen (15 tasks) | 4.32% | 11.03% | 22.02% | 28.54% | 34.04% | 37.14% | |
| XR-1 | 4.55% | 8.69% | 22.25% | 30.09% | 32.44% | 44.98% | |
| RoboCasa Unseen (10 tasks) | 9.08% | 11.84% | 21.49% | 29.65% | 41.77% | 46.17% | |
| XR-1 | 10.99% | 12.41% | 18.87% | 29.86% | 42.48% | 49.22% | |
| ManiSkill3 Unseen (6 tasks) | 19.17% | 40.83% | 42.50% | 50.83% | 63.33% | 47.50% | |
| XR-1 | 15.00% | 70.00% | 60.83% | 77.50% | 80.00% | 72.50% |
As reported in Table R1, StandReady maintains consistent gains across all benchmark splits. The framework exhibits a particularly pronounced advantage on novel unseen tasks, where StandReady raises success over N2M from 29.65% to 41.77% under (an improvement of 12.12 percentage points) and from 29.86% to 42.48% under XR-1 (an improvement of 12.62 percentage points). This confirms that the framework generalizes well beyond its initial training distribution.
Manuscript Revisions: Updated Section 1 (Paragraphs 5–6) and completely replaced the preliminary evaluation in Section 4.5 (Paragraphs 2–3) to reflect the expanded multi-task, multi-embodiment, and physical evaluation suite:
Section 1 (Introduction, Paragraph 5): "Finally, we evaluate StandReady in simulation and on a physical mobile manipulator. Simulation results demonstrate improved downstream manipulation success, and real-world experiments further validate physical transfer through downstream policy execution and task-completion evaluation across six household tasks."
Section 1 (Introduction, Paragraph 6, Item 3): "We evaluate StandReady on 25 RoboCasa365 tasks across three robot embodiments and two VLA policies, with additional cross-simulator experiments in ManiSkill3 and trials on a physical mobile manipulator, demonstrating improved downstream task success over representative baselines and validating the proposed refinement through ablation studies."
Section 4.5 (Real-World Experiments, Paragraphs 2–3): "We evaluate three articulated-object tasks and three pick-and-place tasks. For each task, each autonomous method predicts one terminal standing pose from a single observation at each of four or five initial approach locations. Each selected pose is evaluated in two trials, in which the robot navigates to the pose and executes the manipulation with XR-1."
"As shown in Table 4, StandReady achieves the highest overall success rate among the autonomous methods at 59.3% (32/54), followed by N2M at 53.7% (29/54) and NavAff at 35.2% (19/54). StandReady records one additional success over N2M on each pick-and-place task, accounting for all three additional successes overall. Human-selected poses yield 77.8% (42/54). Figure 6 shows that StandReady's predicted poses generally cluster in front of the target fixtures. N2M also produces clusters, while NavAff's poses are more dispersed. These results suggest that trajectory-feasibility priors learned in simulation can support standing-pose selection for real-world VLA execution."
(Continued in the next comment)
Response to Reviewer NSZ4[Part 3]
W2: Heuristic design choices, sensitivity analysis, and comparative baselines (analytical IK, oracle search, direct distillation). "The method contains several heuristic design choices that are not fully analyzed. The refinement procedure samples candidates primarily from regions already assigned high affordance scores, which may limit its ability to recover feasible poses missed by the initial VQA prior. The paper does not provide sensitivity studies for the candidate budget, search radius, affordance threshold, reward weights, refinement coefficient, or number of refinement rounds. Stronger comparisons with an oracle feasibility search, a direct analytical IK-based baseline, or direct distillation from the best feasible candidate would also help isolate the contribution of the proposed iterative refinement procedure."
Response: Your feedback highlights the need to systematically analyze the algorithmic mechanics of Stage-II refinement. We agree that relying on heuristic hyperparameters without sensitivity analysis leaves their stability uncertain, and that understanding the exact benefits of iterative refinement requires rigorous comparisons against analytical IK, oracle bounds, and direct distillation.
To address these concerns thoroughly, we structure our response into three complementary parts:
- Candidate sampling mechanics and hyperparameter sensitivity sweeps.
- Comparison against analytical IK filtering and oracle feasibility placement.
- In-depth analysis of iterative refinement compared with direct distillation on seen and unseen tasks.
Part 1: Candidate Sampling Mechanics and Sensitivity Sweeps
You raised a valid concern regarding whether sampling candidates from high-affordance regions might trap the search in suboptimal basins if the initial VQA prior misses the globally optimal standing area. In our framework, candidate sampling is explicitly designed to balance visual-semantic guidance with continuous kinematic exploration. Rather than collapsing onto a narrow peak, Stage I provides coarse semantic grounding that establishes a broad, permissive interaction zone across the floor in front of the target fixture while filtering out irrelevant open-scene areas. Within this task-relevant floor support, each refinement round allocates a budget of candidate standings across two complementary spatial scales: while 75% of the budget performs local exploitation within a near radius of 0.5 m around the incumbent prediction, 25% is strictly reserved for broader spatial exploration up to an outer search radius of 2.0 m (as formulated in Section 3.3 andAppendix D of the revised manuscript). This deliberate non-local allocation prevents the search from getting trapped in local extrema and allows Stage-II feasibility scoring to discover kinematically favorable floor locations even if they deviate from the initial VQA center.
To evaluate the operational stability of these design choices, we conducted controlled sweeps on a 5-task subset of RoboCasa Seen tasks across 250 evaluation rollouts, as detailed in Appendix E, Table 6 of the revised manuscript:
Table R2: Sensitivity analysis of Stage-II refinement hyperparameters across five categories (evaluated on the 5-task RoboCasa Seen Panda subset across 250 rollouts per setting). The default configuration uses candidate budget , refinement rounds , outer search radius 2.0 m (near radius 0.5 m), risk-to-dexterity weight ratio 0.7:0.3, and base-footprint penalty weight , achieving Avg. and 46.0% policy success. Each block varies one factor from this default baseline. Relative Step Time measures the training time per refinement step normalized to the default configuration (100%). In the table, dashes under Success Rate indicate settings where rollouts were omitted to conserve compute, while dashes under Avg. indicate altered reward weights whose raw values lie on a different scale:
(Continued in the next comment)
Response to Reviewer NSZ4[Part 1]
Dear Reviewer NSZ4,
Thank you for your constructive, thorough, and encouraging review. We are delighted that you found our paper clear and easy to follow, recognized the practical value of incorporating trajectory-level feasibility without test-time optimization, and appreciated the motivation behind bridging the gap between navigation and downstream manipulation.
Your feedback provided the primary roadmap for substantially strengthening our revision. Specifically, we have:
For a fully rendered version comparing our revisions against the initial submission, please refer to
Revision_Summary.pdfin the Supplementary Material. In this document, newly added or substantially revised text is highlighted in blue, removed text is indicated in red strikethrough, and updated tables and figures are marked with blue revision tags in their captions.Below, we address each weakness in detail.
Response: You raise a critical observation regarding the generality of our framework. We fully agree that evaluating only five atomic tasks on a single arm with static readiness checks leaves open questions about broader applicability. A robust mobile manipulation system must generalize across novel task instructions, diverse mechanical embodiments, different downstream policies, and messy physical environments.
In our original submission, we focused on five atomic tasks to validate the core mechanism of feasibility refinement in a controlled environment. Prompted by your critique, we recognized the necessity of establishing broader generality. In the revised manuscript, we substantially expanded our experimental suite across four operational axes:
(Continued in the next comment)