- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
The paper clarifies terminology for AI-driven CAD datasets by distinguishing geometric representations from executable modeling procedures, and adjustable parameters from retained feature relationships. Drawing on established CAD literature, it compares the documented representations of DeepCAD and WHUCAD in terms of sketches, constraints, feature organization, selection, and topological naming. An illustrative editing example explains why matching geometry or preserving construction order does not necessarily preserve design intent.
Critical strengths
-
The paper explains why geometric similarity and executable construction histories do not by themselves establish meaningful parametric editing. This is useful for assessing what CAD datasets actually support.
-
The comparison distinguishes what a representation can express from what individual dataset models actually contain (Secs. 4.1 and 4.5). It also acknowledges documentation limits, such as explicit sketch constraints not being separately specified in WHUCAD’s original schema (Table 2). These qualifications make the comparison more credible and help avoid overstating the datasets’ capabilities.
Critical weaknesses
-
Although the paper explicitly focuses on DeepCAD and WHUCAD, it aims to guide the description of AI-driven CAD datasets more broadly. The two examples do not sufficiently show how the proposed distinctions apply to datasets that preserve only some constraints or feature relationships. This limits the practical guidance the paper offers beyond the selected comparison.
-
The paper mainly organizes established CAD concepts and compares representations already described in the original dataset papers. Figure 2 also adapts an existing example. While the discussion is useful, it does not clearly identify specific misleading claims in AI-CAD research or explain how correcting them changes existing conclusions. The contribution beyond a useful summary therefore remains limited.
Questions for authors
-
Using the proposed criteria, how would you classify SketchGraphs, Fusion 360 Gallery, and ABC? Would these cases require any changes to the distinctions presented in the paper?
-
Which components are necessary to classify a representation as parametric feature-based?
-
How should representations with feature references but no explicit sketch constraints, or constraints but no model-level references, be described?