- Rating
- 2
- Confidence
- 2
- Informativeness
- 1
- Presentation
- 1
- Soundness
- 2
Read review
Paper summary
This paper proposes a new method for articulated object generation. The main idea is to leverage agents to derive the articulated part relations. And then condition the generation on the derived relations. Small scale experiments show the benefit of the proposed approach. However, the overall process does not surprise me given that the agentic 3D reconstruction pipeline has already been widely adopted, and the main competitor/baselines listed in the experiments are at least one year old.
Critical strengths
The paper includes a lot of details in the main document and appendix, though many of them are a bit hard to fully digest. The experiments are clearly organized and described, making it easy to understand. The ablation in the appendix did show the benefit of each proposed component under the framework of current method.
Critical weaknesses
-
Lack of novelty. It is not novel to use agents for 3d or articulated object generation. Though the overall framework in this paper looks complex, the core idea is not too different from existing works such as (https://arxiv.org/pdf/2604.10992 and https://arxiv.org/pdf/2410.13882), which are missing in related works and the baselines.
-
The experiments only include old methods without agents. I think comparing against other agentic approaches or simple GPT-style agents is important to prove the advantages of the proposed method in practice and distinguish with more SOTA methods.
-
The experiments are done on partNet only, which is synthetic and very small scale. There are other datasets like ACD, GAPartNet and AKB-48 that ca be used for verifying the effectiveness of the method either in larger scale or in zero-shot fashion.
Questions for authors
See the weaknesses part for my major concerns.
W1. Novelty relative to ArtiCAD and Articulate-Anything. We appreciate these comparisons and agree that using an agent is not itself a contribution. Our contribution is how the same typed part relations are used in repair and geometry synthesis: we trace failed checks to editable template parameters, then pair the current part's relations with the actual geometry of previously generated neighbors. ArtiCAD instead plans connectors before generating CAD parts and uses cross-stage rollback for design and code errors. Articulate-Anything's retrieval pipeline places existing meshes and iteratively refines their articulation. The main distinction is how the relations guide part-by-part generation, rather than the presence of an agent or a feedback loop.
In the shared-prior comparison, all generators receive the same image and executable structure: part roles, hierarchy, joints, interfaces, and the fixed relation graph. Each keeps its generation backbone; only the input representation differs. For example, NAP receives graph nodes and edge attributes, and MeshArt receives the hierarchy and joint edges with projected relation attributes. No method receives the target mesh or extra annotations at test time.
These scores are unchanged from the original submission. The comparison with global fusion at comparable capacity holds the graph and training setup fixed and uses neither induced relations nor prior repair. Step-wise retrieval improves F-score from 0.764 to 0.788, interface distance from 0.025 to 0.019, and motion success from 0.816 to 0.869. See Sec. 5.2, L354–374 (Table 2, originally Table 1); App. A.7.1, L992–1011 (Table 9); A.7.2, L1198–1212 (baseline inputs); Sec. 5.4, L472–473 (Fig. 4).
W2. Baseline recency and the requested agent comparisons. We agree that dedicated agent baselines strengthen the comparison. The original submission already evaluated URDF-Anything+, posted in March 2026, in Tables 3 and 4 (pp. 19–20), but did not include these agent comparisons. The revision adds recent agent systems and simple LLM constructors. The latter share templates, examples, adapters, the LLM, and budgets, with 200 proposals per method. Coverage uses 104 template groups. The feedback baseline can edit any valid parameter but does not use induced predicates or dependency scopes.
Table 27 uses method-specific inputs. Articraft and ArtiCAD receive an image and object description; RelArt receives an image and a verified prior. Articulate-Anything is a retrieval-and-articulation reference, not a geometry generator in Table 2. Both rates use all attempts in the corresponding row.
On the same 120 web photos, RelArt instead estimates its prior from each photo. With the same reference-motion check, motion success is 54.2% for Articraft and 80.8% for RelArt. Table 5 compares the complete pipelines; Table 2 isolates geometry generation by holding the image and prior fixed. New results: Sec. 5.3, L425–446 (Table 4); App. A.8.5, L1614–1630 (Table 27); Sec. 5.4, L486–503 (Table 5).
W3. Dataset scale and transfer. We agree that the suggested datasets would be useful for testing transfer. Our benchmark uses the kinematically annotated PartNet-Mobility dataset, with 391 objects in the main test split. For context, the full releases contain 2,346 objects in PartNet-Mobility, 354 in ACD, 1,166 in GAPartNet, and 2,037 in AKB-48. These are release sizes, not test counts. GAPartNet reuses PartNet-Mobility assets, so a transfer test would need to exclude training-set objects.
In Table 19 we exclude each test category and its templates during training but allow the same kinds of parts, joints, and relations to occur in other categories. With the same prior at test time and neither relation induction nor prior repair, retrieval improves F-score from 0.695 to 0.755 and motion success from 0.689 to 0.821 over the base model. It also reduces interface distance from 0.035 to 0.026 relative to flat relations. This tests new combinations within PartNet-Mobility. Neither this test nor the web-photo study establishes transfer to the proposed datasets. See App. A.7.7, L1364–1387 (Table 19, originally Table 15); A.11, L1751–1757.