- Rating
- 2
- Confidence
- 4
- Informativeness
- 1
- Presentation
- 1
- Soundness
- 2
Read review
Paper summary
HistCAD presents a dataset containing 180,495 parametric construction histories along with code to import and manipulate them in Fusion 360. The paper presents metrics which measure how well the parametric models retain design intent when edited. Withholding the sketch constraints is shown to decrease the metrics. A Qwen3-8B model is also fine-tuned to generate the models, with parametric history, based on text descriptions.
Critical strengths
It’s great to see a paper which combines both constrained parametric sketches and the 3D features built from them. Most previous works have created “dumb tool bodies” or predicted sketch geometry and constraints, but never studied how well these constraints capture design intent when edited. HistCAD is the first study I have seen which combines parametric sketches, 3D modelling and studies how design intent is preserved as the sketch parameters are varied.
The dataset of 180,495 parametric construction histories is massive benefit to the community.
Removing the DeepCAD duplicated boundaries (Appendix A.2) is super useful. I always wanted to write code to do that!
Critical weaknesses
The paper is badly written and very hard to understand. It looks like the authors might have run out of space and moved too much information into the appendices. The main paper doesn’t link to the appendices and the whole thing is very hard to follow.
The paper says “We introduce an executable representation” but this is not really described. It sounds like you use Fusion 360 to do the actual parametric modelling. Given a sketch on a planar face of a previous extrusion, would the sketch plane move if the planar faces moved (i.e. do we have inter-feature constraints)? If so, how are these inter-feature references stored? Perhaps too much critical detail was moved into appendices and the main paper no-longer makes sense.
Figure 2 isn’t helping me understand the metrics. The text around this is quite hard to parse as well. It would be good to see examples of cases where the pre-edit match, T, P and V are failing. Understanding the metrics becomes very hard. Looks like there is something in the appendix, but I’m not sure I understand.
Text-conditioned inputs are documented in Appendix A5. This needs to be referenced from main paper. It would be useful to see some examples in the Appendix.
It’s not clear if the results in Table 2 are related to the fine tuned model or experiments with the dataset.
Questions for authors
Description–history correspondence
I don’t follow why the “shuffled history” gives such high metric numbers. 20% is OES, even though the model was prompted with a different text description. Is there no geometry matching check? Why isn’t Pres low?
Target-sketch controls, Table 3
I’m struggling to follow this section
- Are you reporting results for the Qwen3-8B output or the training dataset?
- The text which tries to explain the results doesn’t add any understanding beyond what we have in the table. Are you saying something like “When we don’t use the constraints then 64% of the models are deformed in a way which doesn’t retain the design intent”?
- I would have thought that OES would fall to zero without constraints. Perhaps there are lots of pairs of concentric circles which the coincident constraints cover It sounds like section 7 is trying to give some explanation of this. After reading it carefully I still don’t have a clue what it’s trying to say
Section 6.2 Table 4 I don’t understand at all. We need images showing an example of what is being modified
With the target-sketch prediction fixed, restoring the history’s constraints in other sketches enables additional models to reproduce the required initial geometry I can’t parse this sentence. Are you saying you fix one sketch and predict the rest of the history? Is the prediction with the network or using the parametric recipe?
Q1. Research contribution and the “overall pipeline” comparison
HistCAD provides a representation, dataset, and executable benchmark to study whether sketch constraints support dimensional editing while preserving specified relations and unedited dimensions. Two models can have identical initial geometry and still behave differently under the same edit. For example, two lines may initially form a right angle in both models, yet remain perpendicular in only one after a length change. Reconstructing the initial shape does not establish whether the constraints will preserve the required relationships during editing.
HistCAD represents sketch geometry, explicit constraints, and feature operations within an executable construction history. Each constraint identifies the sketch entities or points it acts on, such as the two lines required to remain perpendicular. The dataset provides 180,495 such histories from Academic and Industrial collections. Its stored constraints supply training targets for constraint prediction, while the associated geometry and feature operations allow the predictions to be tested through model construction and editing. Because the constraint sets are stored separately, we can replace them while keeping the stored geometry definitions, feature operations, and feature references fixed. The representation and dataset thus let us test different constraint sets on the same construction history.
In the prediction experiments, we remove all explicit sketch constraints from an existing history and ask Qwen to predict a constraint set for every sketch. Qwen receives the stored geometry and feature operations, but not the later edit request. Its output specifies constraints on the existing sketch entities or points. Fusion 360 then solves the sketches with those constraints and executes the stored feature operations. The learned constraints are therefore tested on a subsequent edit that the predictor has not seen.
Different predicted constraints can change the solved geometry even when the stored geometry definitions are unchanged. The benchmark first checks whether the reconstructed model matches the initial geometry built with the stored constraints. For a matching model, the evaluator applies a prescribed dimension change and checks whether the target is reached, the specified relations and unedited dimensions are preserved, and every feature operation executes successfully. This separates reproducing the initial model from preserving its required behavior after an edit.
Pointer-CAD generates CAD commands using B-Rep-based entity selection, while Seek-CAD studies feedback-driven CAD generation. HistCAD compares how models built from the same construction history with different explicit sketch-constraint sets respond to the same prescribed edit. Similarities in using CAD histories or executing feature operations do not establish that these works evaluate this constraint-preserving behavior.