- Rating
- 1
- Confidence
- 3
- Informativeness
- 3
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper presents a hierarchical system for collaborative manipulation. A vision-language coordinator selects robots, skills, and targets using observations, structured physical-state feedback, capabilities, and execution history. A common execution interface validates prerequisites, dispatches skills, and returns outcomes for subsequent decisions. The evaluation examines sorting, direct handover, interrupted-task continuation, and replacement of coordination models and skill backends in a four-robot simulation.
Critical strengths
The experimental reporting is transparent. The paper distinguishes destination selection, handover completion, final delivery, and appropriate stopping. It retains earlier failures and timeouts in relevant denominators and reports paired comparisons and confidence intervals.
The controlled-drop experiment demonstrates the value of execution feedback within the evaluated system. With the execution components held fixed, the closed-loop agent completes 15/45 recoverable-drop episodes, compared with 0/45 for the one-shot planner.
The implementation boundaries are described explicitly. The paper discloses simulator-derived state, manipulation assistance, and backend-specific execution configurations. These details help readers interpret the demonstrated capabilities.
Critical weaknesses
exceed the agent in most reported conditions: both achieve 59/75 normal deliveries; rules achieve 17/45 recoverable-drop deliveries versus 15/45 for the agent, and 23/24 B-held takeovers versus 18/24. Sorting differs by only one successful delivery. The rule controller also has lower runtime costs. These results establish the usefulness of feedback relative to one-shot execution, but provide limited evidence that the proposed model-based coordinator contributes additional capability.
The evaluated collaboration setting is narrow relative to the paper’s scope. Although the workcell contains four robots, each episode involves robot A, one receiver, and one object. Initial-state variation is restricted to translation within a 1 cm-radius disk, with fixed height and orientation. This provides limited evidence about more complex dependencies, concurrent collaboration, or adaptive reassignment.
Much of the task structure is supplied through state representations and execution contracts. Possession, readiness, docking, and delivery progress are derived from simulator geometry and executor state, while the interface explicitly checks prerequisites. Execution also includes attachment maintenance, release assistance, and modified collision constraints. These are legitimate engineering choices, but the paper needs to establish what the coordinator contributes beyond following the resulting state-transition structure, and how this advances the feedback-based planning approaches discussed in Section 2.2.
Questions for authors
-
Can the authors identify a task variation, within the existing workcell, where the agent handles a changed instruction or capability configuration without modifying the controller, while the feedback-rule baseline requires additional programming?
-
In the frozen-log evaluation, how does the coordinator perform when the overview RGB image is removed and only structured state and history are retained? This would clarify the contribution of visual reasoning.
-
In the no-recovery-skill condition, all 24 fault-exposed agent episodes initially request unsupported retrieval before most eventually terminate. Given that the capability catalog is supplied, how should this behavior be reconciled with the claimed state-consistent coordination capability?