- Rating
- 2
- Confidence
- 3
- Informativeness
- 1
- Presentation
- 1
- Soundness
- 2
Read review
Paper summary
This paper presents CALIPER, a point-cloud-text dual encoder for CAD model retrieval with dimension annotations. This system adapts the pre-trained text encoder and point-cloud encoder through contrastive learning while retaining detailed CAD description information and geometric scale features at the level of the corpus. Additionally, this paper analyzes the "near duplicate data leakage" problem existing in the official Text2CAD data division and introduces a set of evaluation schemes based on component non-overlap.
Critical strengths
-
This paper points out that there are differences between the general text-to-3D retrieval and CAD retrieval; in CAD retrieval, numerical dimensions are crucial for distinguishing parts with similar geometric shapes.
-
The author discovered that there is a significant problem of near-duplicate data leakage in the official Text2CAD dataset. The component-disjoint split method proposed in the paper, as well as the introduction of two evaluation indicators, cluster-credit and exact-uid, have enhanced the rigor of the evaluation.
Critical weaknesses
-
The Introduction and Method sections are presented in a largely pipeline-like, sequential manner, rather than providing a coherent and integrated description, analysis, and comparison of the overall problem. As a result, reviewers and readers must invest considerable effort in reconstructing the problem formulation and understanding the overall narrative of the paper. This fragmented presentation makes the manuscript unnecessarily difficult to follow and significantly undermines its readability.
-
The proposed approach combines several established components, including pretrained text and point-cloud encoders, contrastive alignment, scale-preserving preprocessing, and staged fine-tuning. However, the method does not introduce a clearly novel architecture or learning objective. The primary contribution appears to lie in the empirical analysis and evaluation protocol rather than in the model itself. The authors should more clearly articulate the methodological novelty of their approach and explain how it advances beyond existing techniques.
3.The headline comparisons against the zero-shot Uni3D and OpenShape baselines involve substantial differences in domain adaptation and input coverage, which complicates the interpretation of the reported performance gains. Notably, the fully adapted Long-CLIP baseline with a 512-token input achieves an R@10 of 0.909, compared with 0.957 for CALIPER under the strict validation setting. This relatively small performance gap raises an important question: could comparable performance also be achieved by replacing the language encoder and applying supervised fine-tuning to the aforementioned zero-shot methods? The authors do not provide a sufficiently detailed analysis to address this possibility. Additional controlled experiments or a more thorough discussion are needed to establish whether the observed improvements stem from the proposed method itself or primarily from domain adaptation and fine-tuning.
4.The evidence supporting fine-grained dimensional grounding remains insufficient. Although the model exhibits strong sensitivity to uniform numerical perturbations, doubling an individual decimal value has little effect on retrieval performance, and swapping the length and width values does not lead to a measurable degradation. These findings raise concerns about whether the model genuinely grounds individual dimensional values and their semantic roles, rather than merely exploiting coarse-grained numerical patterns. The authors should provide further evidence to substantiate their claims regarding fine-grained dimensional understanding.
- The authors consulted Fusion360 geometry during model development, although they subsequently evaluated the model on sealed query sets. While this evaluation provides some evidence of transfer to held-out queries, it does not fully resolve concerns regarding broader generalization. In particular, the extent to which exposure to Fusion360 geometry during development may have influenced model design, data selection, or evaluation outcomes remains unclear. The authors should clarify the relationship between the development data and the evaluation sets and provide additional evidence of generalization to unseen geometries or domains.
Questions for authors
see above
Reply to Reviewer z3ZP
Thank you for the review. We answer W1–W5 in order. Unless marked, retrieval numbers are cluster-credit R@10 on our strict validation split.
W1 — Presentation. We agree. The introduction and method follow the pipeline and leave the reader to reconstruct the problem and the argument. The paper needs to be restructured around the problem, what it requires, and how each requirement is tested.
W2 — Novelty. We agree that the method introduces no new architecture or objective, and that the contribution lies in the empirical analysis and the evaluation protocol. A new full-chain control also shows that the results do not depend on the cluster-aware loss (0.957 vs 0.958 with plain InfoNCE).
W3 — Could replacing the language encoder and fine-tuning reach comparable performance? Yes. We swapped the text tower and trained each variant with our full recipe. The table gives R@10; its first row is the untrained zero-shot baselines.
A dash marks a setting that was not evaluated. The CADPrompt column uses the seen-geometry protocol of our appendix table for the trained rows (the CADPrompt shapes are in their training data) and Table 6 for the zero-shot rows. TULIP is single-seed.
The adapted towers that read (almost) the whole caption land within about three points of CALIPER on machine captions and about five on human prompts. The improvement over the zero-shot baselines therefore comes from domain adaptation and input coverage, as you suspected, and not from the specific encoders. The zero-shot rows of Table 1 show how far off-the-shelf models are from this task; they are not a controlled comparison, and the paper should say so more clearly. We did not fine-tune Uni3D or OpenShape end to end. The closest evidence on the point side is that frozen Uni3D-g features with our heads outperform frozen Utonia (0.517 vs 0.471).
W4 — Fine-grained dimensional grounding. We agree that the evidence in the submission was insufficient, and one of its probes was flawed. New results:
This supports sensitivity to individual overall dimensions, bound to the correct axis through their position in the caption. It does not show that the model reads the dimension words themselves.
W5 — Fusion360 exposure during development. The concern is valid. The Fusion360 gallery shapes were seen during development; only the query text of the sealed probe was new. The dev-consulted number (0.761) is not used as evidence. In the sealed probe, the caption queries passed their pre-declared bar (0.129, 108× random) and the dimension-only queries failed theirs. Our evidence for unseen geometry is the CADPrompt chain, retrained with the 190 target shapes and their 3,241 near-duplicates removed. All of it is DeepCAD-family geometry. We have no clean evaluation on a different CAD domain, and that is a real limitation.