- Rating
- 1
- Confidence
- 4
- Informativeness
- 1
- Presentation
- 1
- Soundness
- 1
Read review
Paper summary
The paper proposes EAGLE, which uses shape entropy computed from polygon-annotated samples to quantify an object's intrinsic geometric complexity, and uses this measure to refine bounding-box predictions. The claimed contribution is improved box localization at comparable latency. Validation consists of comparisons against YOLO26 baselines (e.g., n and m variants), reporting AP and latency; the full EAGLE pipeline reports 41.11 AP (n) and 52.94 AP (m).
Critical strengths
- Reasonable motivation. Explicitly quantifying object shape complexity and using it as a prior for bounding-box regression is an intuitive idea, and shape entropy is a sensible, lightweight descriptor for this purpose. This is the main point in the paper's favor. However, it carries limited weight in my assessment, because the paper does not provide convincing evidence that the idea actually works (see Weaknesses).
Critical weaknesses
-
The empirical evidence does not support the claimed improvement. The YOLO26 baselines are incompletely reported. With the official default NMS head and no additional training, YOLO26n achieves 40.9 AP, only ~0.2 below the full EAGLE pipeline (41.11), and YOLO26m achieves 53.1 AP, which exceeds EAGLE (52.94). The remaining differences in AP and latency are small enough to fall within run-to-run noise, and no variance or multi-seed results are reported. Furthermore, there is no ablation isolating the contribution of the shape-entropy conditioning, nor any study of the proportion of polygon-annotated samples. This is consequential because the paper's central claim is an empirical improvement over the baseline; against properly configured baselines, that improvement is marginal or negative, and there is no evidence that the proposed component is responsible for any gain.
-
The technical content and motivation lack rigor. Several equations are incorrect or unjustified: e.g., in C(r) (Line 211) the denominator contains with a dummy index but the summation is missing, and Line 307 defines with unexplained constants and no sensitivity analysis. More seriously, the paper's motivating premise misrepresents prior work: Related Work cites Mask R-CNN as an example of "geometric feature interference," claiming that joint mask training harms box localization, whereas the original paper (He et al., 2017, Table 3) reports that multitask training improves box AP by +0.9. Presentation is also well below the venue standard (a single figure with illegible text at Line 386; a table whose Latency column overflows the page at Line 441). This is consequential because, beyond weak results, the paper's theoretical formulation and its stated motivation cannot be trusted as written.
Questions for authors
All questions below are clarification requests whose answers could change my assessment; I have no suggestions for future work at this stage.
-
Baselines. Why do the reported YOLO26 baselines differ from the official results (40.9 AP for YOLO26n and 53.1 AP for YOLO26m with the default NMS head)? Please report baselines under the official configuration, along with mean ± std over multiple seeds for both EAGLE and the baselines, and specify the latency measurement protocol (hardware, batch size, precision, warm-up, number of runs). If EAGLE shows a statistically significant gain over correctly configured baselines, I would reconsider my assessment.
-
Contribution of shape entropy. What is the performance of the full pipeline with the shape-entropy term removed (or replaced by a constant), and how does performance vary with the proportion of polygon-annotated training samples? Without these results, it is unclear whether the proposed component contributes anything.
-
Mask R-CNN claim. What evidence supports the claim that joint mask training harms box localization, given that the original Mask R-CNN paper reports the opposite (+0.9 AP^bb from multitask training)? If this premise does not hold, how is the method still motivated?
-
Equations and constants. Please correct the C(r) definition (Line 211) and explain how the 0.8/0.2 weights (Line 307) were chosen, including a sensitivity analysis.
-
Authorship process and verification. Taken together, the incorrect equations, unexplained constants, unpolished figures and tables, and the mischaracterization of Mask R-CNN suggest that substantial portions of the paper may have been produced with an automated research pipeline or LLM-based tools without adequate human review. Could the authors clarify which parts of the work, if any, were produced with such tools, and what steps were taken to manually verify the equations, experimental results, and citations?