- Rating
- 2(+1)
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
The paper proposes EdgeGaze, an end-to-end multi-person gaze target detector built on the EdgeCrafter set-based detector. Each of N = 20 queries predicts a head box, a confidence score and a gaze distribution. Two additions are proposed: Scene Prior Guidance, where saliency, object and head maps supervise the shared encoder features during training to form a "Prior-Guided Scene Representation" (PGSR) fused with the person queries, and a Unified Gaze Distribution (UGD), a single softmax over the 64×64 gaze grid plus one out-of-frame bin. The paper reports good results on GazeFollow and VideoAttentionTarget, zero-shot transfer to GOO-Real and ChildPlay, and 3.1–4.9 ms latency with less parameters than Gaze-LLE.
Critical strengths
- Efficiency is re-measured under a single protocol for all methods, including frozen backbones and the head detector required by two-stage methods.
- The paper is transparent and honest about annotation incompleteness, wrong experiment estting and reports the strict detection mAP.
- A compact end-to-end model is a useful practical direction, and the dataset statistic in Fig. 2 is a nice motivation.
Critical weaknesses
-
The evaluation protocol uses test-set information, and the reported numbers are not valid test results. This avoid the normal usage of test set in machine learning. All previous methods like Gaze-LLE would never do that.
- Checkpoints are selected on the test split: "For each training run, we select the checkpoint with the highest mAP on the corresponding test split and report all metrics from that checkpoint" (L830-831). This applies to the main results and to every ablation.
- The effect is visible in the paper itself. Table A5 evaluates the full model "at the final epoch" and gives VAT mAP 0.8211, L2 0.0569, AUC 0.9763, whereas Table 1 (test-selected checkpoint) reports 0.824, 0.056, 0.977. This gap is as large as most of the component ablation effects (Tables 3-4).
- Predictions are assigned to annotations with Hungarian matching whose evaluation cost includes the gaze term with weight 100 and the out-of-frame term (Table A1, L787), and this single assignment is shared across AUC, L2, out-of-frame AP and mAP (L824-827). If the gaze cost is computed against the annotated gaze point, as Table A1 implies, the evaluation selects among 20 queries the one whose gaze is closest to the ground truth, using a weight 20× larger than the box term. This is an oracle selection, not a detection result. It would also explain why the VAT Out. AP is 0.999-1.000 for all variants, far above two-stage methods (≤0.951).
- It is not stated whether the confidence threshold (L753-754) is applied before matching, nor how annotated people with no matching detection are counted in AUC/L2. If missed or unmatched people are excluded, the hardest cases are removed from the evaluation.
-
The comparison between end-to-end and two-stage methods is not like-for-like, and the SOTA claims (L38-39, L102-103, L377, L482) do not hold.
- Two-stage methods produce one prediction per GT head; end-to-end methods are scored after the matching above. The pattern in Table 1 reflects this: all end-to-end methods have lower AUC than recent two-stage methods but much lower L2 (e.g. Tonini et al. 0.922 AUC / 0.072 L2 vs. ViTGaze 0.949 / 0.105). These distances are not on the same scale.
- Even with this protocol, EdgeGaze is not SOTA on GazeFollow: PAGE reports 0.966 AUC vs 0.960 (L283), and the L2 advantage depends on the protocol issue above.
- L412-413 claims the zero-shot setting is "stricter" than two-stage methods that receive GT heads. With gaze-based matching, it is not. A 26.7M model trained only on GazeFollow halving the in-domain ChildPlay L2 of Gaze-LLE ViT-L (0.053 vs 0.101, Table 2) needs to be verified under a protocol where matching uses head boxes only.
- A fair comparison is easy to run, since the head detector is already used for the latency measurements: evaluate two-stage methods on detected heads, and evaluate EdgeGaze with box-only matching, thresholded predictions, and missed heads counted as errors.
-
The proposed components do not explain the results.
- Without any scene prior (Table 3a, first row), the model already obtains 0.9592 AUC / 0.0584 L2 / 0.7857 mAP, i.e. above every baseline in Table 1. The full Scene Prior Guidance adds +0.0008 AUC and −0.0021 L2.
- On VAT (Table A5), the no-prior model has higher AUC than the full model (0.9764 vs 0.9763) and the same Out. AP (0.9997). On GazeFollow, Lsal+Lobj without Lhead has the best AUC (0.9601).
- UGD vs separate prediction (Table 4) changes AUC by 0.0015 and Out. AP from 0.9982 to 0.9997, and worsens VAT L2 (0.0545 → 0.0561). Out. AP is saturated and cannot discriminate between the two.
- All differences come from single runs with checkpoints selected on test mAP. Notably, the full model stands out mainly in mAP (the selection criterion), while the other metrics are nearly flat. Multiple seeds and variance are needed.
- The gains therefore appear to come mainly from the pretrained EdgeCrafter detector (COCO + Objects365, App. A.1) and the evaluation protocol, not from PGSR or UGD.
-
The "edge" and "independent of crowding" claims are not supported.
- All latencies are measured on a desktop RTX 2080 Ti with TensorRT FP16 (L369). No embedded device (e.g. Jetson, mobile NPU/CPU), memory footprint or power measurement is reported, despite the title and L45 "well suited for edge deployment".
- Computation is "nearly independent of scene crowding" (L31-32, L74-75, L101) because the model has a fixed cap of N = 20 queries (L303). It cannot output more than 20 people, yet Fig. A2 plots it up to K = 32 heads. Performance as a function of the number of people (and beyond 20) should be reported.
-
Limited novelty. The set-prediction formulation is HGTTR applied to the EdgeCrafter detector. Saliency/object/head auxiliary supervision follows prior work on joint gaze-saliency modeling (Chong et al., 2018) and object-aware gaze detection (Tonini et al., 2023; GaTector). UGD is a softmax with one additional "out" bin. Combined with the small ablation effects, the technical contribution is thin for top conferences (ICLR/NeurIPS/CVPR) but it's fine with flagship conferences or application centric conferences like ECCV, WACV, IEEE FG or BMVC.
Some minor issues:
-
Several numbers and statements are inconsistent across the main text and the appendix:
- Table 4 (UGD row) and Table A5 (all three priors) describe the same full EdgeGaze-M configuration, yet report different VAT results: AUC 0.9771 vs 0.9763, L2 0.0561 vs 0.0569, mAP 0.8240 vs 0.8211. The paper should state which number is the actual result (see the checkpoint-selection comment above).
- L317 "10 epochs of fine-tuning on VideoAttentionTarget" → Table A1 reports that only 20% of the training batches are used per epoch, i.e. about 2 full epochs.
- L742 "EdgeGaze achieves the reported GazeFollow performance with just 10 training epochs" → per L830-831, the reported checkpoint is the one with the best test mAP, which is not necessarily the epoch-10 checkpoint.
-
Incorrect or inconsistent citations:
- L364 states that Gaze-LLE uses DINOv3. Gaze-LLE uses a frozen DINOv2 encoder, while PAGE and GazeAnywhere are based on DINOv3. Please check which model was used for the parameter and latency measurements of Gaze-LLE.
- TextGaze's parameter count is said to include "Qwen2.5-VL (Bai et al., 2025)" (L326), but Bai et al. (2025) is the Qwen3-VL technical report (L542-544).
- Zong et al. 2023a and 2023b are the same paper (L661-666).
-
Missing comparisons: GazeDETR (L154) and GaTector+ (L190) are end-to-end / head-free methods discussed in the related work, and both appear in Fig. A1, but neither is compared in Tables 1-2. Head detection quality (AP or recall on annotated heads) is also never reported, although it is a core output of an end-to-end detector.
-
Several analyses and figures are presented selectively:
- Fig. 1 plots Pareto fronts using Avg. Dist., the metric most affected by the matching protocol, and omits PAGE, which is in Table 1. With AUC as the accuracy axis and PAGE included, the margin over Gaze-LLE/GazeMoE shrinks to ≤0.002 AUC and PAGE is more accurate (0.966), which does not support "a substantially better accuracy–efficiency trade-off" (L109-110).
- App. F.1 (L1024-1025) reports that all three priors give the best mAP and L2 after fine-tuning, but omits that the same model ranks 5th of 8 in VAT AUC (0.9763 vs 0.9773, Table A5).
- Fig. A3 is selected by construction: the six cases are those where "only the full model places its gaze estimate within 0.06 of the annotation" (L1029-1030). It cannot serve as evidence for PGSR.
- UGD is claimed to contribute to zero-shot transfer (L124-127), but it is not ablated on GOO-Real or ChildPlay, and no out-of-frame metric is reported on ChildPlay even though it provides out-of-frame labels.
-
The GazeHTA-style mAP excludes unmatched predictions, so it has no false positives and is closer to a matched-instance accuracy than an AP. The strict mAP (0.474, L910) should be reported in Table 1, with the same protocol applied to the baselines.
-
GOO-Real: the evaluated copy has ten images fewer than the standard split (L808-809), and AUC uses a 5×5 one-hot grid (L817). Please confirm the baseline numbers in Table 2 were obtained under the same definition.
-
Fig. 2 / App. C.2: L86 states that gaze falls "on another head", but C.2 (L851-852) counts gaze points "inside the head boxes". Please clarify whether the gazer's own head box is excluded.
-
The authors should tone down the language:
- L109-110 "consistently lies on the Pareto frontier, offering a substantially better accuracy–efficiency trade-off" → see the comment on Fig. 1 above.
- L415-416 "the learned scene and gaze representations generalize beyond the training distribution rather than overfitting to a particular benchmark" → two zero-shot datasets evaluated under a different protocol from the baselines do not support this.
- L470-471 "provides a cleaner and more effective prediction space" → UGD changes GazeFollow AUC by 0.0015 and worsens VAT L2.
- L485 "making end-to-end gaze understanding practical for edge deployment" → no edge device is evaluated.
- L743 "indicating faster optimization" → the comparison is uncontrolled, as acknowledged in L744-746.
Questions for authors
- The topic is interesting and important but the experiment design is not rigorous and has many fake claims. Each main argument above is followed by supporting evidence. Please address each main argument and the evidence behind it.
- Please re-report Tables 1-4 with checkpoints selected on a held-out validation split (or the final epoch), with matching based on head boxes only, confidence thresholding before matching, and missed annotated people counted as errors. Please also report the number of matched vs. total annotated people.
- Please evaluate at least Gaze-LLE and Sharingan on detected heads under the same end-to-end protocol, and report latency/memory on an actual edge device.
- If there is no space in rebuttal windows, all minor issues can be skipped.
17 comments
# Response (1/14) to Reviewer XbqF
Hungarian matching. GazeFollow and VAT provide gaze annotations for only a subset of the people in a scene (Appendices B.2 and D.1). To score the annotated head–gaze pairs, we use one Hungarian assignment per image between the queries and the available annotations. The assignment minimizes the joint cost in Table A1, which uses the annotated gaze and in/out labels. Under the matched-instance mAP protocol, correct predictions for unannotated people do not incur false-positive penalties from missing labels. GazeHTA [4] likewise calls its matcher in the evaluator (lines 95–113) and solves a Hungarian assignment (lines 156–161) during test scoring (lines 119–130). The unofficial HGTTR implementation also matches predictions to test annotations for gaze AUC and L2, with a ground-truth gaze heatmap cost.
Confidence threshold and AUC/L2. We agree that Appendix A.2 should clarify where the confidence threshold is applied. It filters inference outputs. For Table 1, Hungarian matching uses all 20 final decoder predictions and assigns one to each eligible ground-truth instance in the evaluated GazeFollow and VAT splits. A valid in-frame annotation contributes to AUC and L2 even if its assigned head prediction has low confidence or poor localization. We report head recall under head-only matching in Response (2/14).
[1] Ryan, F., et al. "Gaze-LLE: Gaze Target Estimation via Large-Scale Learned Encoders." CVPR, 2025. Paper.
[2] Ye, Z., et al. "PAGE: Towards Practical Human-level Gaze Target Estimation." arXiv:2607.04860, 2026.
[3] Tonini, F., et al. "Object-aware Gaze Target Detection." ICCV, 2023.
[4] Lin, Z.-Y., et al. "GazeHTA: End-to-end Gaze Target Detection with Head-Target Association." ICRA, 2025.
# Response (2/14) to Reviewer XbqF
Question: The comparison between end-to-end and two-stage methods is not like-for-like, and the SOTA claims (L38-39, L102-103, L377, L482) do not hold.
- Two-stage methods produce one prediction per GT head; end-to-end methods are scored after the matching above. The pattern in Table 1 reflects this: all end-to-end methods have lower AUC than recent two-stage methods but much lower L2 (e.g. Tonini et al. 0.922 AUC / 0.072 L2 vs. ViTGaze 0.949 / 0.105). These distances are not on the same scale.
- Even with this protocol, EdgeGaze is not SOTA on GazeFollow: PAGE reports 0.966 AUC vs 0.960 (L283), and the L2 advantage depends on the protocol issue above.
- L412-413 claims the zero-shot setting is "stricter" than two-stage methods that receive GT heads. With gaze-based matching, it is not. A 26.7M model trained only on GazeFollow halving the in-domain ChildPlay L2 of Gaze-LLE ViT-L (0.053 vs 0.101, Table 2) needs to be verified under a protocol where matching uses head boxes only.
- A fair comparison is easy to run, since the head detector is already used for the latency measurements: evaluate two-stage methods on detected heads, and evaluate EdgeGaze with box-only matching, thresholded predictions, and missed heads counted as errors.
Response: Comparison protocol. We agree that Table 1 compares different evaluation settings. Two-stage gaze predictors are conditioned on supplied head boxes. EdgeGaze must localize heads and is scored after ground-truth-assisted Hungarian matching (Appendix B.2). Localization and association introduce additional sources of error, and gaze-assisted assignment affects AUC and L2. We report both settings side by side, following HGTTR (Table 1) [1] and GazeHTA (Table I) [2].
GazeFollow comparison. We supplied the released Gaze-LLE model with head boxes predicted by a dedicated YOLOv5m detector, which achieved 99.10% head recall. Both methods use the same confidence floor and head-only matching at IoU ≥ 0.5. AUC/L2 use matched heads. The mAP denominator includes all annotated heads, so misses count as failures.
| Method | Matched/GT heads | Head recall ↑ | AUC ↑ | mAP (head-only) ↑ | Avg. L2 ↓ | Min. L2 ↓ |
|---|---|---|---|---|---|---|
| EdgeGaze-M (validation-selected) | 4695/4782 | 98.18% | 0.9320 | 0.7022 | 0.1298 | 0.0680 |
| YOLOv5m + Gaze-LLE [3] | 4739/4782 | 99.10% | 0.9584 | 0.7836 | 0.0988 | 0.0413 |
Table 1 and PAGE. The submitted RTX 2080 Ti timings include the external head detector for two-stage methods (Section 4). Table 1 marks PAGE's 0.966 GF AUC as the best result. PAGE has 1,718.5 M parameters and takes 107.2 ms on that GPU, compared with 26.7 M and 4.9 ms for EdgeGaze-M.
ChildPlay zero-shot evaluation. In Table 2, ground-truth head boxes give the two-stage baselines a localization and association advantage. EdgeGaze must detect the heads, and its gaze scores can reflect errors in both detection and association. We computed the submitted L2 of 0.053 after ground-truth-assisted Hungarian matching, following GazeHTA's gaze-assisted association convention (matcher lines 129–134) [2]. We also evaluated the GazeFollow-validation-selected model with confidence filtering and head-only association.
| Model | Matched/GT heads | Head recall ↑ | AUC ↑ | L2 ↓ |
|---|---|---|---|---|
| EdgeGaze-M (zero-shot) | 24322/24935 | 97.54% | 0.9401 | 0.1160 |
Head recall covers all annotated heads in the evaluated frames. AUC/L2 use matched in-frame annotations. The common-protocol Gaze-LLE comparison above is on GazeFollow.
[1] Tu, D., et al. "End-to-End Human-Gaze-Target Detection With Transformers." CVPR, 2022. Section 4.3 and Table 1.
[2] Lin, Z.-Y., et al. "GazeHTA: End-to-end Gaze Target Detection with Head-Target Association." ICRA, 2025. Section IV-E and Table I.
[3] Ryan, F., et al. "Gaze-LLE: Gaze Target Estimation via Large-Scale Learned Encoders." CVPR, 2025. Paper.
# Response (1/14) to Reviewer XbqF
Thank you for your feedback. Due to the limited time remaining and the numerous questions, these are our final responses for the discussion period.
Question: The evaluation protocol uses test-set information, and the reported numbers are not valid test results. This avoid the normal usage of test set in machine learning. All previous methods like Gaze-LLE would never do that.
Response: Checkpoint selection. Gaze-LLE's official GazeFollow script loads the test split (lines 44–47) and tracks the best epoch by Min. L2 (lines 107–111) [1]. PAGE likewise loads the GazeFollow test split (lines 94–102) and tracks the best Min. L2 epoch (lines 231–233) [2]. Object-aware GTD uses the GazeFollow test annotations for validation (lines 67–73) and saves checkpoints by validation AUC (lines 8–13) [3].
We could not locate a public implementation released by the original HGTTR authors. The public third-party reproduction (README line 3) uses the GazeFollow and VAT test annotations for validation and selects checkpoints by that split's AUC.
Our submission selected checkpoints by test mAP. We retrained EdgeGaze-M with held-out validation splits and selected checkpoints on validation. Both settings use the original scoring protocol on the test splits. The comparison also reflects the change in training data.