- Rating
- 3(+1)
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper addresses geometric ambiguity in CAD assembly tasks and proposes ResCAD, a language-grounded CAD assembly framework that explicitly separates geometric feasibility filtering, component and interface grounding, and CAD execution. It first applies geometric rules to filter infeasible candidates, then translates natural-language assembly instructions into structured assembly relationships and geometric constraints and employs a dual-branch grounding module based on B-rep graph neural networks to identify the appropriate components and locate their geometric interfaces. Finally, it executes the assembly using a CAD kernel and performs collision detection to verify the geometric feasibility and global consistency of the resulting assembly.
Critical strengths
- The language-grounded CAD assembly task is interesting and practically valuable.
- The motivation for separating feasibility filtering, grounding, and execution is well justified.
Critical weaknesses
- The Overview is fragmented and fails to provide a coherent understanding of the overall method. I recommend rewriting Section 4.1 (Overview). First, it should establish an overall understanding of the method. For example, the core idea is to separate feasibility, grounding, and execution, and a four-stage framework is designed to realize this idea. Next, the relationship between the core idea and method should be clearly articulated, along with the purpose of each stage. For instance, the authors could explicitly explain that feasibility is implemented through Language Compilation and Geometric Filtering, which perform preliminary screening of candidate components.
- The figure and the textual description are inconsistent, which leads to confusion. In Figure 2, the Language Compilation stage appears to take only the request q as input. However, Section 4.2 states that both the request q and the component entities V serve as inputs to Language Compilation. Furthermore, Figure 2 presents Geometric Filtering as a standalone Stage 2, whereas the method description incorporates it as part of the original Stage 3, Two-Branch Grounding. These inconsistencies between the figure and the text make the method considerably more difficult to understand.
- Some results in Table 1 show that the full ResCAD performs worse than ablated variants (e.g., ResCAD w/o interface rule and Rules + executor) on some metrics. Could the authors explain the reasons for these performance differences?
- The metrics described in the text do not correspond to those reported in Table 1. The meanings of “@1%,” “F@1%,” “Coll.-free,” “All parts,” and “Exact” in Table 1 are not explained. In addition, why is “Exact” uniquely highlighted in bold in the table?
- Some recent works on CAD generation [1–3] should be included and discussed in the Related Work section.
[1] Seek-CAD: A Self-refined Generative Modeling for 3D Parametric CAD Using Local Inference via DeepSeek.ICLR 2026
[2] CAD-Tokenizer: Towards Text-based CAD Prototyping via Modality-Specific Tokenization. ICLR 2026
[3] Plan-then-Act: Bi-level CAD Command Sequence Generation. ICLR 2026
Questions for authors
Please revise the writing issues based on the weaknesses.
3 comments
Thanks for the responses. These have resolved my concerns. I hope the authors will incorporate these adjustments into the revised version of the paper to improve its completeness and readability. I will raise my score to 3.
Dear Reviewer AHrf,
Thank you for appreciating our responses and for raising your score. Based on your suggestions, we have incorporated the corresponding changes into the revised manuscript, including improvements to the presentation and additional experimental results in Appendix J.4. The revised PDF has been uploaded, with all textual changes highlighted in blue.
Thank you again for your constructive suggestions and time.
Best regards,
The Authors
Thank you for recognizing the task's practical value and for the concrete suggestions on presentation. We would like to address your questions individually as follows.
Q1: Please rewrite the Overview to explain how the four stages implement feasibility, grounding, and execution, with a clear purpose for each stage.
A1: Thank you for your detailed suggestions on making the Overview more readable. We have rephrased the passage below to first introduce the separation of feasibility, grounding, and execution, and then explain how the four stages implement these principles:
“ResCAD separates geometric feasibility, language grounding, and assembly execution: satisfying local geometric requirements does not uniquely identify the requested parts or interfaces, and selecting them does not guarantee a realizable assembly. Four stages address these distinctions. First, an LLM translates the request and component entity names into a connection graph and geometric requirements. Second, geometric filtering removes candidates lacking interfaces that satisfy these requirements. Together, these stages define the search space for grounding. Third, two learned B-rep rankers resolve the remaining ambiguity by ranking complete component combinations and their connection interfaces. Finally, a CAD kernel computes component poses and checks whether the selected connections can be realized together. Thus, geometry restricts the choices, learning identifies those matching the request, and execution checks the resulting assembly.”
Q2: Please reconcile Fig. 2 and the text regarding the compiler inputs (q versus q and V) and whether Geometric Filtering is a separate stage.
A2: Thanks for pointing out the presentation of Figure 2 in describing the compiler inputs and geometric filtering. In fact, the compiler receives the request q and component entity names V, not candidate CAD geometry. The names identify the entities to connect, while geometric filtering screens their candidates before learned grounding. We will modify Figure 2 accordingly, and clarify this part in our next version.
Q3: Why do some ablated variants outperform full ResCAD on certain metrics in Table 1?
A3: We understand the reviewer’s concern that ResCAD w/o interface rule achieves lower CD (15.07 vs. 18.35), while Rules + executor achieves higher STEP validity and collision-free rates (98% vs. 96%). Actually, removing the interface rule allows alternative alignments that can bring large surface regions closer to the reference while misaligning the requested interfaces; CD averages surface distances and can therefore favor these alignments. Similarly, Rules + executor can produce valid, collision-free assemblies using incorrect components. However, their reported Exact scores are 44% and 10%, respectively, versus 82% for ResCAD. Overall, these gains reflect surface similarity or geometric validity, not more accurate recovery of the requested assembly.
Q4: Please define “@1%,” “F@1%,” “Coll.-free,” “All parts,” and “Exact,” align the text with Table 1, and explain why Exact is bold.
A4: It is worth mentioning that Shape Acc.@1%, F@1%, and Coll.-free measure geometric fidelity and compatibility through shape agreement, surface accuracy and completeness, and inter-part non-interference, respectively. Distance- and precision–recall-based geometric evaluation is also adopted in recent CAD work [1,2]. Here, “@1%” denotes a distance threshold of 1% of the reference assembly’s bounding-box diagonal: Shape Acc. counts component roles within this mean surface-distance threshold, while F measures surface precision–recall at the same threshold; Coll.-free counts requests with collision-free outputs.
On the other hand, All parts and Exact measure recovery of the requested assembly: All parts requires every selected component to match the target, whereas Exact additionally requires matching connection labels and execution acceptance.
Note that we have bolded the Exact values in Table 1, as it is our primary metric for overall assembly correctness.
[1] Wu et al. CMT: A Cascade MAR with Topology Predictor for Multimodal Conditional CAD Generation. ICCV 2025.
[2] Liu et al. Point2CAD: Reverse Engineering CAD Models from 3D Point Clouds. CVPR 2024.
Q5: Please include and discuss Seek-CAD, CAD-Tokenizer, and Plan-then-Act in Related Work.
A5: We would like to note that the mentioned works Seek-CAD, CAD-Tokenizer, and Plan-then-Act are related to our work from the perspectives of self-refinement, modality-specific tokenization, and planning-based CAD generation, respectively. Different from these works, our work grounds language-specified assembly requests to component choices and B-rep interfaces on existing geometry, rather than generating or editing the component geometry itself. We will include these works and discuss them in the Related Work.