- Rating
- 2
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
The paper introduces PartCoder, a framework for reconstructing multi-file CAD code assemblies directly from point clouds. It uses PartField and hierarchical clustering to progressively decompose the input geometry, completes missing interfaces introduced by decomposition, and reconstructs each part independently using an existing CAD generation backbone. The resulting parts are combined through a central assembly file. Chamfer distance between the assembled reconstruction and the input point cloud determines whether a split is accepted and decomposition continues, without additional backbone training. The authors also introduce PrIMe3D, a benchmark for converting AI-generated 3D assets into CAD models. Experiments with three generation backbones across three datasets show improvements in geometric reconstruction quality, with larger gains on more challenging datasets.
Critical strengths
-
Practically relevant framework. The paper introduces PartCoder, a framework for reconstructing multi-file CAD code assemblies directly from point clouds. By hierarchically decomposing a dense input point cloud into geometrically coherent parts and reconstructing them independently, PartCoder enables existing CAD generation backbones to handle more complex objects without additional training.
-
Consistent empirical improvements. Experiments across three backbones provide evidence for the effectiveness of PartCoder. Averaged across these backbones, the reported mean IoU improvements over the corresponding monolithic baselines are 7.7 percentage points on OmniCAD and 11.1 percentage points on PrIMe3D. These results support the value of decomposing difficult reconstruction tasks into simpler part-level problems.
Critical weaknesses
-
Insufficient ablation of the main components. The experiments do not adequately isolate the contributions of the method’s key components. The maximum-part-count ablation does not establish the individual importance of PartField-based decomposition, interface completion or adaptive stopping. Comparisons with simple spatial clustering or planar partitioning, reconstruction without interface completion and fixed decomposition granularity would help identify which design choices account for the observed gains.
-
Limited validation of structural quality and practical editability. Although the decomposed parts need not correspond to the original manufacturing components, the current evaluation primarily measures geometric similarity and does not directly assess the quality of the modular organization or its usefulness for editing. Concrete part-level editing examples or evaluations, including modification, removal and repositioning, would strengthen the claims of controllability. An analysis of unintended overlaps, gaps, and interface misalignment would also help establish the engineering applicability of the resulting assemblies.
Questions for authors
-
Contribution of the decomposition method: How much improvement does PartField-based decomposition provide over simpler alternatives, such as spatial clustering or planar partitioning? Could the authors provide controlled comparisons to establish the importance of the chosen decomposition method?
-
Contribution of interface completion: How do reconstruction quality and code validity change when interface completion is removed? What are the typical failure cases of the current plane-and-convex-hull approximation for curved, non-convex, or perforated interfaces?
-
Contribution of adaptive stopping: What advantages does adaptive stopping offer over reconstruction with a fixed number of parts in terms of quality and efficiency? Could continuing to evaluate deeper decompositions after the first non-improving split yield better results?
-
Validation of practical editability: Could the authors provide concrete examples or task-based evaluations of part modification, removal, and repositioning to demonstrate the practical value of the modular outputs? Could they also analyze unintended overlaps, gaps, and interface misalignment between parts?