- Rating
- 3
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
PointCRO is a fine-tuning framework for point-cloud semantic segmentation. CGRO derives class-wise rewards from an epoch-frozen reference model using ground-truth confidence, the strongest incorrect competitor, and their margin, then optimizes normalized advantages through clipped probability ratios. RFKL uses the resulting advantage gaps to weight same-class feature references in a KL objective. Experiments cover multiple indoor and outdoor datasets and backbones, with matched continued-training baselines.
Critical strengths
The correction-versus-degradation analysis provides a useful view of why similar aggregate regularization objectives can have different segmentation outcomes.
Critical weaknesses
-
The closest simple alternative to CGRO is not isolated by the existing controls. Table 7 compares scalar point-wise CE reweighting, while CGRO changes class-wise optimization directions through all-class probability ratios. Appendix A.6 discusses focal-style and margin objectives conceptually, but does not provide a matched direct class-wise objective using the same frozen-reference reward information without the ratio construction. Removing clipping or normalization changes individual ingredients rather than testing that alternative. Given the many reward-design choices and the 0.5 mIoU advantage over RWCE+RFKL in Table 7, the evidence establishes effectiveness more clearly than the necessity of this particular relative-optimization formulation.
-
The representation analysis is conditioned on different success-selected point sets. Table 9 and Appendix A.10 evaluate each method on its own corrected points. The much larger same-class similarity change for PointCRO therefore mixes representation changes with differences in which points each method corrects. As Appendix A.10 explicitly acknowledges, this analysis cannot by itself establish that reward-guided feature support explains the extra corrections or stabilizes them during training. The uniform-KL ablation supports an aggregate contribution from weighting, but the stronger mechanistic interpretation requires a comparison on common point populations; endpoint transitions alone do not resolve this selection effect.
Questions for authors
-
What evidence distinguishes CGRO from a direct class-wise optimization objective using the same frozen-reference rewards and matched tuning budget?
-
Does the feature-support advantage persist on a common point set rather than each method's separately selected corrected points?
4 comments
Dear Reviewer cfSd,
We sincerely appreciate your valuable suggestions. As the discussion period is nearing its end, with only a few days remaining, and to ensure that we have sufficient time to provide additional materials later, we kindly ask whether our responses have addressed your concerns. We are eager to address any remaining issues to improve our work.
Thank you for your time and effort in reviewing our paper.
Best regards,
Response to the Authors
Thank you for the detailed rebuttal and additional experiments. The new results substantially address my original concerns, although some mechanistic interpretations still require more cautious wording.
Regarding R3W1/R3Q1:
The newly introduced adv_logprob baseline provides a relevant and well-controlled comparison, directly addressing the missing class-wise alternative identified in my initial review.However, the 0.4-point improvement is relatively modest, and its robustness remains unclear without run-to-run variability. Moreover, the claim that probability ratios and clipping prevent destructive gradient updates is not directly established by this comparison. I suggest including the precise objective and experimental details while presenting the stability explanation more cautiously.
Regarding R3W2/R3Q2:
The fixed-population analysis effectively addresses my concern about selection bias. PointCRO consistently achieves larger ground-truth class feature-support increases across identical point sets, providing stronger evidence for the reported representation differences. Although, these results demonstrate consistent feature differences but do not establish that RFKL-induced support directly causes additional corrections or improved training stability.
Overall Assessment:
The rebuttal and additional experiments have strengthened the paper's empirical support to some extent. I maintain my weak accept recommendation (Rating: 3) and encourage the authors to incorporate the new evidence and appropriately qualify their conclusions.
Dear Reviewer cfSd,
We sincerely thank you for your thoughtful follow-up and insightful suggestions. Your emphasis on closely matched controls and common evaluation points helped us sharpen the evidence for the CGRO formulation and strengthen the feature-support analysis. We have incorporated these comparisons into the revised manuscript. Revised passages are highlighted in red. For subsections revised in full, the subsection headings are highlighted in red.
- R3W1 & R3Q1. Appendix A.13, Table 26, compares CGRO with a direct class-wise objective using the same frozen-reference rewards and matched training and tuning budgets. CGRO achieves 78.6% mIoU, compared with 78.2% for the direct alternative.
- R3W2 & R3Q2. Appendix A.10, Table 21, compares feature support on three common point sets. PointCRO achieves the largest same-class support increase across all three sets. We have also revised Table 9 and its accompanying discussion in the main text to evaluate all methods on the same set of points corrected by CGRO.
We greatly appreciate your engagement throughout the discussion. Your feedback has helped us make the controlled comparisons more informative and the conclusions more precise. We would welcome your assessment of these revisions and any remaining concerns.
Best regards,
The Authors
Response to Reviewer cfSd
R3W1&R3Q1: What evidence distinguishes CGRO from a direct class-wise optimization objective using the same frozen-reference rewards and matched tuning budget?
R3A1: Thank you for this insightful suggestion. To isolate the contribution of the relative optimization formulation, we conducted a direct comparison against the closest alternative class-level objective (adv_logprob) under a matched training and tuning budget. This alternative retains the exact same frozen-reference reward construction, detached class-wise advantage computation, reference policy synchronization protocol, and expectation weighting as CGRO, while replacing the probability ratio and clipping surrogate with a direct objective based on signed advantage-weighted class log probabilities. All other configurations, including RFKL, initialization, random seeds, loss coefficients, batch size, and evaluation protocols, remain strictly identical.
Under the evaluated setting, the simplified direct objective achieves 78.2% mIoU, leaving a substantial performance gap of 0.4 percentage points below the 78.6% mIoU attained by CGRO. Unlike direct log-probability optimization, which applies unbounded updates proportional to advantage magnitudes and risks over-penalizing or over-reinforcing ambiguous boundary points, the probability ratio and clipping operations in CGRO anchor policy updates to the frozen reference distribution. This bounded relative optimization prevents destructive gradient steps on noisy 3D point predictions, thereby translating identical reference-derived competition signals into superior segmentation accuracy. We will incorporate this controlled comparison, the formal objective definition, and experimental details into the revised manuscript and supplementary material.
R3W2&R3Q2: Does the feature-support advantage persist on a common point set rather than each method's separately selected corrected points?
R3A2: Thank you for raising this question regarding the impact of point-set selection. To ensure a fair evaluation, we recompute the feature metrics on three fixed populations corresponding to the points successfully corrected by CGRO, CGRO + UFKL, and PointCRO, respectively. Within each fixed population, all three methods are evaluated on the exact same point IDs, with the baseline-selected reference identities and TopWrong classes held constant.As detailed in the table below, PointCRO achieves the largest same-class support increase (ΔSGT) across all three fixed populations, including those corrected by the alternative methods. This consistency demonstrates that the performance advantage persists when evaluated on identical point sets and is not an artifact of selecting PointCRO's own successful corrections. Furthermore, PointCRO maintains positive relative margin changes (ΔMfeat) across all populations, confirming that its increase in ground-truth class support consistently outweighs the increase in TopWrong support. We will include this table and the corresponding evaluation protocol in Appendix.