- Rating
- 1
- Confidence
- 3
- Informativeness
- 1
- Presentation
- 1
- Soundness
- 1
Read review
Paper summary
The proposes a method to predict the parenthood relationships between parts of a 3D object. It does so through a transformer architecture that combines both local patch features with object-level context, training on a synthetically generated dataset in which relationships have been inferred by geometric positions.
Critical strengths
Frankly, it is hard for me to identify a strength of this paper. If pressed, I would say that the problem it studies is important, and that I do believe that predicting object parenthood is a worthwhile effort that could have a myriad of applications if done correctly.
Critical weaknesses
One critical weakness of this manuscript is the writing, which is consistently vague, repetitive and bordering on meaningless. At times it seems to reference missing context, as if there were parts of the text that were edited out but their references remain. Almost every paragraph reads as unnecessarily defensive, comparing every introduced concepts to separate, irrelevant concepts. Terminological choices are non-standard and often confusing. Here are some examples from the first pages, though they are by no means exhaustive and this writing issue persists through the entire text:
- L30 "not merely a nearby handle" what is the meaning of this aside? is this referring to the door handle? the door handle is obviously connected by parenthood to the door, though in the reverse direction.
- L34 "rather than surface reconstruction" why bring up surface reconstruction at all? this seems completely irrelevant to the task at hand.
- L46-47 "ShapeNet patches supply estimated connection labels without parent annotations" this sentence cannot be understood at the point of the paper at which it appears. What does "supply" mean in this sentence? Are they part of ShapeNet? Inferred from ShapeNet? Learned?
- L51 "The ShapeNet CAD meshes used for training" this is the first time these meshes are introduced.
- L58 the method's name is never introduced before the acronym is used
- L88 "address related geometry and structure problems" this is a very vague sentence. Isn't the point of this section to tell the reader how they are related?
- L97 "both use assembly supervision and output joint/mate information [...] accuracies are not directly comparable". This makes sense, but it seems like joint/mate relationships can lead to parenthood relationships, so why not attempt to extract them from it? More critically, if assembly datasets are available and can be used to learn very similar relationships, why not use those for this method instead of inferring relationships geometrically?
- L110 "A surface patch (a chart in the implementation)" why is this referencing the implementation? why the need for two separate names?
- L115 "A physical component is a supplied rigid link" Supplied by whom?
- L116 "ShapeNet validation selects checkpoints" what does this sentence mean? Selects how?
I'll stop enumerating here, as this poor writing makes it quite hard to understand the contributions of the following sections if there are any. The steps of the method are not clearly stated at any point, and notation and nomenclature regularly appear without or with minimal explanation (e.g., "geometry derived center", "nominal radius", what do these things mean?)
While the above is reason enough to reject a paper (indeed to desk-reject it, in my humble opinion), I also believe the paper contains a fundamental theoretical weakness: namely, it derives attachment rankings geometrically using simple geometric heuristics and then trains a model to predict these rankings instead of using the geometric heuristics directly (a "cannonball to kill a fly" approach). I realize Section 5.4 intends to address this, unfortunately, the results are not conclusive and the section is mostly unreadable (see examples above).
I do not know if any human was involved in the production of this text or these results; if they were, I would encourage them to keep working on this research problem, but perhaps with a different approach entirely.
Questions for authors
I don't have questions for the authors.