- Rating
- 2
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 1
- Soundness
- 1
Read review
Paper summary
This paper presents an embodied synthetic data generation framework, named EmbodiedSmith. EmbodiedSmith turns the task and robot description into a scene graph, retrieves or generates the objects, and converts the graph into object poses. It then turns existing robot skills into an execution plan. After execution, the framework will inspect failures and revise the execution plan or change the scene instead. Experiments evaluate scene quality, demonstration generation on 16 fixed-base and mobile manipulation tasks, and downstream policy training on generated demonstrations. The results show improved demonstration-generation success better than previous methods.
Critical strengths
- The system tries to address a practical challenge that exists in the simulation generation: a generated scene ought to be valid for a robot to execute, and a proposed task in the scene should be able to find solutions. Combining task grounding, motion planning, execution feedback, and explicit acceptance checks provides a useful approach to automated data collection. The held-out-seed evaluation and inclusion of failed generation sessions in ASR are positive aspects of the protocol.
Critical weaknesses
-
The major issue of the paper is that the experiments do not sufficiently isolate the claimed scene–task self-improvement contribution: Appendix C.4 states that scene assets and object layouts remain fixed during the main demonstration-generation evaluation. The ablations therefore establish the importance of execution-feedback-based plan repair and robot placement validation, but do not directly establish the benefit of the proposed mutual scene–task refinement loop. Furthermore, the scene baselines retain different asset pipelines, and the policy experiment compares randomized with fixed-layout data rather than with another randomized collection method. Spatial domain randomization can help the robot policy generalize to new layouts has been studied before. Therefore, these results support system utility but leave the source of the improvement insufficiently resolved.
-
The technical specification and validation are insufficient for several central claims as well. Section 3.1 names Beam-DFS layout optimization without adequately specifying its objective, candidate generation, search procedure, or connection to visual scene-graph refinement. The described task generator composes predefined atomic skills, leaving the claimed creation of new skills unclear. Likewise, the presented embodiment demonstrations and physics descriptions do not establish human-level dexterity or improved physical fidelity. These gaps make it difficult to assess the methodological contribution over existing task-conditioned, simulation-ready generation systems such as SceneSmith and EmbodiedGen V2.
-
The paper writing and figure generation seem to use widely used AI and are hard to follow. For example, the figure 1 and 2 have various arrows and hard to follow the full pipeline. Moreover, it is hard to tell which parts are new compared with previous methods, since the pipeline lists many components and most of them have been discussed in previous methods.
Questions for authors
-
How does the generated scene image inform scene-graph refinement? Please specify the layout solver’s objective, pose-candidate generation, search and pruning procedure, and treatment of reachability constraints.
-
Which quantitative experiment isolates execution-driven scene editing? A comparison with scene editing enabled versus disabled, using identical assets, initial scenes, tasks, and generation budgets, would materially affect my assessment of the central contribution.
-
Does the system generate new atomic skill implementations, or compose and parameterize the primitives in Table 5? What quantitative evidence supports the claims concerning human-level dexterity and deformable/fluid interaction fidelity?
-
Can the downstream gains be compared against conventional layout randomization using the same demonstration budget and execution backend? This would help establish the benefit specific to the proposed generation framework.