- Rating
- 1
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 1
Read review
Paper summary
This paper proposes ArticulateCode, a method for generating 3D articulated objects using programs as an object representation. ArticulateCode is a processing pipeline that first takes reference images and an interaction request as input and uses VLMs to generate code that can build the required 3D object. The model-generated code C first produces named geometry, and a physical baking process then produces the asset. The initially generated components must first be audited and then corrected within a specified inference budget. Experiments tested the effectiveness of the modules, yet revealed limitations in the method’s generalizability and robustness compared with other code-based methods.
Critical strengths
- This paper proposes a code-as-representation method to generate 3D articulated objects, which can leverage the strong capabilities of modern LLMs to improve generation quality while keeping the core idea simple and effective. As the capabilities of LLMs expand, this type of method also has the potential to evolve.
Critical weaknesses
- The method’s generalizability across different foundation models has not been established, which limits its contribution. As mentioned above, the generalizability of such code-as-representation methods for 3D generation is expected to be critical, as LLMs continue to evolve. If a method can only be used with a certain configuration, it could quickly become outdated and need to be redesigned for new models, which would require substantial effort. However, the results in Table 4 (Section 4.4) show limited generalizability, indicating that this method only works with GPT-5.6 Luna and cannot be adapted to Qwen models.
- The method did not show remarkable advantages over similar methods. As shown in Table 4 (Section 4.4), Direct Code and SceneCode are both more flexible in their choice of foundation model and yet demonstrate performance equal to or better than ArticulateCode, even when ArticulateCode uses its best GPT configuration.
Questions for authors
- Could the authors establish this work’s contribution beyond what can be attributed to the underlying LLMs? For example, if the method is consistently effective across a variety of foundation models and produces better results as these models become more capable (with most results better than direct model generation), then the work’s independent contribution can be substantiated.
- Could the authors provide more empirical results to demonstrate the advantages of this work over SceneCode and Direct Code?
- Could the authors resolve the two issues raised in Section 4.4, namely “Motion is the shared bottleneck” and “Interface sensitivity” (especially the latter, as other methods do not exhibit similar problems)?
- Could the authors provide more examples to demonstrate the diversity of the method’s 3D reconstructions and prove its ability to handle the wide range of object categories and geometries that may be encountered in scene simulation?