- Rating
- 2
- Confidence
- 3
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
Sketch-Solver proposes a new framework for the generation of parametric CAD models. Rather than interleafing numerical values and geometric constructions, the new framework defines symbolic “construction skeleton” first and then assigns numerical values to the variables in a second step.
A new dataset is created which decomposes the CADQuery scripts from the Text-to-CadQuery dataset into a “construction skeleton” and set of variable values. Named parameters are the assigned to groups of values. Qwen3-4B, Qwen3.5-2B and Ministral 3 3B LLMs are then fine-tuned and evaluated on the dataset. The Sketch-Solver framework is shown to have superior results to direct generation when evaluated on this dataset.
Critical strengths
Great to see a new perspective on CAD generation. It’s good to see that people are starting to think more about how to parameterize this kind of CAD program.
The hypothesis that when two values are equal in a CAD program, this almost always suggests that a single parameter value can be used for both of them. While some exceptions exist, I believe this does hold in the majority of cases.
All the numerical results in the paper look great.
Critical weaknesses
There are no figures showing the kinds of geometry which can be generated. The B-Rep bodies in the editing results in Appendix H Figure 3 are all very simple. Frontier models are starting to produce large and complex assemblies (see for example “Articraft: An Agentic System for Scalable Articulated 3D Asset Generation”). While I appreciate that the suggested architecture does beat GPT-5.6-Terra on the given metrics, I don’t have confidence that the dataset used for evaluation is able to measure success. About 50% of the original DeepCAD data was single extrusions. When bodies from DeepCAD are rendered individually, they are hard to describe by humans. This may make them difficult from a text-to-cad perspective. The fine-tuned model may learn to cheat by recognising phrases which the VLM uses for specific shapes.
The value of having a parametric model is that it can potentially be used to generate a family of related and useful shapes. To understand the parametric behaviour of shapes, one needs images of how they evolve as parameters are changed. I believe this is what the authors were trying to show with the editing examples. In this case only the hollow pipes have obvious design intent, and these behave correctly. More illustrations are required and these need to be higher complexity to make this work publishable.
Information about what dataset was used appears very late in the paper. Section 3.2 (CONSTRAINT-AWARE REPARAMETERIZATION) is quite hard to follow without knowing the source dataset. Figure 1(b) doesn’t show what the input was like.
Questions for authors
Line 160 If η(i) = η(j), both sites read the same binding. I found this very hard to understand. What does “site” mean in this context? Numerical occurrences are defined in the abstract. How does a site map to a numerical occurrence?
Thank you for the constructive review, and for recognizing the value of shared parameters. We agree that introducing the source data late made the method harder to follow. Section 3 now introduces the data first, and Figure 1 shows a fuller user instruction and clarifies the reparameterization input.
Your review asks for evidence that the numerical gains correspond to useful geometry and parameter behavior, including on more complex parts, and that they do not depend on recurring phrases in the generated descriptions. We have added multi-feature generation and parameter-family examples, evaluated harder parts, and tested reworded and shorter descriptions. We also added Sketch–Solver inference experiments with API LLMs without further fine-tuning.
1. Parametric behavior. Figures 6–7 (Appendix E.6) show families of shapes from four multi-feature parts using Qwen3.5-2B, rendered at a common scale. Figure 6 changes one parameter in a fixed predicted program and re-evaluates its dependent expressions. For example, changing plate thickness also updates the boss and four ring cuts that share this value, keeping them attached across the sweep. This illustrates how one generated program can produce related shapes through its parameters.
Figure 7 changes the instruction and lets Solver update the assignments while retaining the construction. Direct regeneration drops the first part's ring cuts at every value, while reuse retains them. Missing dependencies remain visible in Figure 6: a pin whose vertical position is independent of the block height floats when the block is halved. When the edited instruction also specifies the pin position, Solver updates it in Figure 7 and keeps it attached.
Figure 4 shows eight selected edits, including frames, boxes and drilled parts; Direct can change the construction when only a dimension is edited. Over all 3,366 construction-preserving edits, Qwen3.5-2B reuse lowers FR100 from Direct's 8.67% to 4.25% (Table 6). Figure 2 brings generation and editing examples into the main text.
2. Part complexity. Figure 5 shows twelve generated parts from the original Text-to-CadQuery test split (Qwen3-4B); seven have two or three source extrusions. These examples show the generated geometry alongside the reference and Direct outputs.
The quantitative gains also extend to harder parts. On the 621 hardest validation parts, FR100 falls from 15.78% to 9.98% for Qwen3.5-2B and from 17.87% to 14.98% for Qwen3-4B (§4.3). Table 16 groups parts by source extrusion count (2,273 / 424 / 229 with one, two, and three or more). Qwen3.5-2B improves in every group, including 8.30% to 6.11% for three or more extrusions. These results use an independent OCCT rebuild of the original DeepCAD JSON as reference; Appendix B describes the source-program audit, and Table 14 also evaluates all systems against this reference. The experiments cover individual DeepCAD parts; articulated assemblies such as Articraft remain a further setting to evaluate.
3. Robustness to instruction wording. We reworded 2,883 validation instructions while retaining every number. The paraphrases retain only 4.2% of the original word 4-grams on average, and "Start by creating a new coordinate system" drops from 23.0% to 0.0% of instructions. With the trained Qwen3.5-2B models unchanged, FR100 rises from 5.34% to 8.53% for Direct and from 3.71% to 6.90% for Sketch–Solver (Table 17). Both models are sensitive to wording, but the 1.63-point advantage remains after substantial rewording.
On the shorter, less specific Text2CAD beginner descriptions, Sketch–Solver also retains lower IR and FR100 on both backbones; for Qwen3.5-2B, IR is 1.81% versus 4.10% and FR100 is 12.79% versus 14.53% (Table 18).
The new API experiments provide evidence beyond our locally fine-tuned models. On the same 2,926 verified validation instructions, prompted Sketch–Solver lowers both invalid-program rate and severe-failure rate relative to Direct for all three API LLMs, without further fine-tuning (Table 2). Appendix D.3 provides details of these pipelines.
4. Source data and notation. Section 3 now opens by naming the training data: intermediate-level Text2CAD descriptions of DeepCAD parts, paired with their Text-to-CadQuery programs; Appendix B.1 describes these sources. In Figure 1(a,c), we replaced the abbreviated dimension list with a natural-language modeling instruction. Figure 1(b)'s caption identifies the corresponding source CadQuery program as the input to offline reparameterization.
On line 160: a "site" was one numerical occurrence, that is, one position in the program where a numeric literal appears. The revision defines occurrences as these positions, uses "occurrence" throughout, and the sentence now reads: "If η(i)=η(j), the literals at positions i and j are replaced by the same parameter name, so both uses take the same value."