- Rating
- 3(+1)
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper proposed an autoregressive representation that maintains the evolving mesh frontier as an explicit structured state. A Trie maintains a canonical lexicographic frontier state for deterministic expansion. To avoid inconsistencies caused by re-predicting known vertices.a dual-mode inference strategy that generates a full face when the frontier is empty and otherwise reuses the two frontier vertices to predict only the new vertex.
Critical strengths
The paper addresses an interesting question about frontier representation and extends FACE with explicit frontier modeling.
Critical weaknesses
- The results lack a direct comparison with FACE to demonstrate the benefits of frontier modeling.
- The paper lacks comparisons of memory usage and generation time under the same hardware conditions.
Questions for authors
- What do (n) and (d) denote in Table 1?
- Would Figure 4 be more appropriately presented as a table?
3 comments
Thanks for the provided results, and my main concern has been addressed. I would suggest the author to add these results into the main paper. I increases my score to 3.
Official Comment by Authors
We sincerely thank the reviewer for the positive feedback and constructive suggestion. We are glad that the additional results have addressed your main concern. We will incorporate these results into the main paper as suggested. Thank you again for your time and thoughtful review.
Response to Reviewer KTbw
We thank the reviewer for their constructive feedback and thoughtful questions. We address each point below.
We would like to clarify that a direct comparison with FACE is already provided in Table 3 of our manuscript(originally labeled as “ZYX,” and now explicitly renamed to “ZYX (FACE)” in the revised manuscript). Please kindly refer to Concern 1 (“Comparison with FACE”) of our General Response for detailed explanations and the reproduced table. As shown there, under identical training and evaluation settings, TrieMesh reduces Hausdorff distance from 0.124 to 0.112 and Chamfer distance from 0.061 to 0.053 compared to ZYX(FACE), directly demonstrating the benefits of our frontier modeling and dual-mode decoding.
To further evaluate the inference efficiency of TrieMesh, we benchmarked all methods on our test set using their 7-bit versions on a single NVIDIA A100 (80 GB) GPU, ensuring a consistent quantization resolution across methods. The results are summarized below.
As shown in the table, all methods exhibit comparable inference-time GPU memory consumption (3.2–4.6 GB), and most operate at a similar parameter scale. More importantly, we observe a general trend that methods with more compact tokenization (i.e., lower compression ratios) tend to achieve higher generation throughput. This is expected, as a lower token-to-face ratio requires fewer autoregressive decoding steps to generate the same number of faces. While actual throughput also depends on model architecture and implementation details, the compression ratio serves as an important indicator of inference efficiency in autoregressive mesh generation.
Notably, TrieMesh achieves a compression ratio of 0.12, close to the 0.11 of FACE, while maintaining a comparable generation throughput (47.2 vs. 52.7 faces/s). Moreover, both methods consume the same GPU memory (4.6 GB). These results demonstrate that our structured frontier representation and dual-mode decoding introduce little additional inference overhead while preserving the efficiency of compact autoregressive mesh generation.
In Table 1, (O(n)) indicates that querying or deleting a specific frontier edge in a standard stack or queue requires linear time in the number of active frontier edges (n). In contrast, TrieMesh represents frontier edges using a Trie with a fixed key length of (d=6), enabling key-based lookup and deletion in (O(d)) time, which is effectively constant. We will explicitly clarify these notations in the table caption.
Thank you for pointing out this LaTeX formatting error, which was caused by an incorrect use of the LaTeX
minipageenvironment. We will correct this issue in the revised manuscript to ensure that the table is properly labeled and referenced as Table 2.