- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper proposes a framework that jointly searches over robot morphology and motion given a natural-language task, the MJCF file of an initial robot, and a task scene. The system automatically constructs the design parameter space; a language model generates rewards, design constraints, and candidate designs, and proposes directions for modification based on failure feedback. The framework builds a regression surrogate using 33 physical descriptors and maps directions in the descriptor space to design parameter updates, then uses CEM-MPC to search for motions. The main contribution of this work is the system-level integration of a cross-robot design representation with language, physical feedback, and control search. The authors report five main tasks covering five robot families, additional tasks, and cross-task transfer, involving eleven tasks and nine robots in total. They also report a real-world climbing deployment on a Go2 with printed add-on parts.
Critical strengths
- The combination of language-based proposals and physics-based updates has a clear technical motivation and receives preliminary support from ablations. The design surrogate is built on interpretable physical quantities, and the finite-difference Jacobian maps the desired changes back to parameter space, enabling directed search without training a control policy or relying on differentiable dynamics.
- The integration of a cross-robot design representation with the manufacturing pipeline has substantial engineering value. The system can automatically parse MJCF and handle parameters, contact geometry, and structural operations across different robot families within a single pipeline.
Critical weaknesses
- The main comparisons are confounded by differences in budgets and evaluation environments and are not yet sufficient to establish the optimization advantage of the method itself. The language-driven comparisons fix only the language-model expenditure at $3.33 per seed, without also matching the number of design evaluations or the total simulation budget. Better performance at the same language-model expenditure is a valid system-level observation, but it does not, by itself, establish that physical feedback is more effective or that the total computational cost is lower.
- The evidence for broad automation, generalization, and hardware deployment is less substantial than the paper's central claims suggest. The method is described as requiring no per-task or per-robot tuning and using language to generate designs and motions. However, the experimental details indicate that several main tasks use fixed reward files. For bin picking and free throws, the initial motions generated by the language model failed to obtain any score, and the runs were restarted with task-specific scripted motions after approximately four hours. This does not negate the value of avoiding policy training, but it indicates that the sources of the rewards and initial motions, human intervention, and the actual scope of applicability must be disclosed.
Questions for authors
- Under the same MuJoCo version, task scene, frozen evaluation criteria, and initial states, does L2D retain its advantage over the other methods when both the number of actual design evaluations and the simulation budget for control search are matched?
- For each main task, are the final rewards, evaluation criteria, control configurations, initial motions, and structural operations generated by the system, supplied by existing task assets, or written or modified by humans? Please use this information to precisely define what is meant by "no tuning" and "zero-shot".
- How many real-world climbing trials were conducted with the Go2, how many succeeded, and how did the original robot perform under the same test conditions? Please report the deployed control method, any human adjustments, and the mass, maximum stress, displacement, and task success rate before and after optimization of the printed parts. Was a dynamics evaluation performed again using the optimized geometry?
Thank you and Revisions
We thank the reviewer for recognizing the technical motivation and the engineering value of the cross-robot design representation.
**Q0:**Does L2D retain its advantage when both the number of design evaluations and the simulation budget are matched?
A0: We agree that matching language spending is a system-level comparison. We reran every method with both the number of design evaluations (100 per seed) and the simulation and wall-clock budgets matched, on MuJoCo 3.11, with the same scenes, frozen judges, and control warm start. L2D keeps the best mean on the hurdle (20.2 against 16.1), the toss (43.8 m against 30.0 m) and bin pick (16.18 against 16.02), ties the free-throw ceiling, and sits on the pen-spin plateau with VLMgineer; its normalized gain is 1.00 against 0.76 for the next method. L2D therefore retains its advantage when both design evaluations and simulation budget are matched. Every final design, for L2D and every baseline, is also re-flown under a longer control search than the search episode and judged on that flight, so designs that overfit the short-horizon reward and fail as the episode runs on are not credited.
Q1: For each main task, are the final rewards ... or written or modified by humans? Please define "no tuning" and "zero-shot".
A1: In the matched rerun reported above, each component comes from the following source:
"No tuning" means that none of these is set per task or per robot by hand, except things we list explicitly: the user defined controller settings and the hand-added judge clauses. "Zero shot" means that the printed part and the controller solved in simulation run on the real robot with no on-robot tuning or training.
Human involvement and the prompt are now specified in the Method. The user writes a prompt that names one completion event observable in one episode. It may also say how the task must not be done and set a design scope. The user then signs off the judge and the design space. Constraints the prompt states are hard, what it leaves open is a soft default the user signs off (Sec. 2.2). The limitations (Sec. 5) state what this cannot guarantee a loophole in a signed-off judge, a pass the user did not intend, a badly scoped design space, or tasks without a graded signal.
Q2: How many real-world trials were conducted, how many succeeded, and how did the original robot perform?
A2: We replaced the single real world paragraph with two quantified comparisons against the stock robot (Sec. 4.1, Table 1):
Deployed control: The final design's motion is re-solved with DIAL-MPC under the robot's real motor and joint-speed limits and exported as a tape of joint targets tracked by the stock PD controllers.
Printed part before and after FEA co-design: 549 to 104 cm^3 (680 to 130 g), peak von Mises stress 15.6 to 14.4 MPa, below the 20 MPa limit, largest displacement 1.4 to 4.4 mm.
The optimized geometry is re-evaluated in dynamics. The blade is re-solved under the real motor limits and scored over 400 randomized worlds (2.78 m on average, against 1.90 m and 65% for the stock Go2).
Please let us know if additional detail would help.