- Rating
- 3(+1)
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
SpecHyper-Track adds a training-free module to an online tracker (TrackTrack) that refines appearance features with two hypergraphs (1) A cooperative hyperedges over motion-consistent groups, smoothed by a low-pass residual, and competitive hyperedges over nearby look-alike targets, sharpened by a high-pass residual. (2) A framelet decomposition then gives high-frequency features to established tracks and fused features to new tracks. Experiments cover MOT16, MOT17 and DanceTrack (Tables 4–6), with ablations on MOT17 validation (Tables 1–3).
Critical strengths
(1) SpecHyper-Track reduces identity switches from 1487 to 1101, on MOT17 (Table 2). With the same detector, ReID model, and tracking settings as their reproduced TrackTrack baseline, HOTA also improves modestly from 65.6 to 66.9 on MOT17 and from 62.4 to 64.2 on DanceTrack (Tables 5–6), without additional training
(2) Table 1 shows why the residual design matters. Keeping the original features and applying a bounded residual update achieves 71.1 IDF1, compared with 48.7 Table 1.
Critical weaknesses
(1) The benefit of using high-frequency features for established tracks and fused features for new tracks is unclear. In Table 2, the residual update adds 2.9 HOTA points, while the framelet split and routing add another 0.4 and reduce identity switches from 1376 to 1189. These results do not isolate the effect of assigning different features to the two stages. Since this is a main contribution, the authors should compare against using the same features in both stages and swapping the assignments.
(2) The reimplemented baseline is weaker than the published one. The authors' re-run of TrackTrack gets 65.6 HOTA on MOT17 and 62.4 on DanceTrack (Tables 5–6), but the published results are 67.1 and 66.5 (Shim et al., CVPR 2025, Tables 1 and 3), both above SpecHyper-Track (66.9 and 64.2). The gap is not explained, so it is unclear whether the module helps a well-tuned tracker. It also means the MOT17 claim in Sec. 3.2, of beating the strongest competitor, does not hold.
Questions for authors
Requested clarification+evidence:
(1) Please asses or elaborate contribution of routing properly. Why use high-frequency features for established tracks and fused features for new tracks? Please compare this assignment with using high-frequency features in both stages, fused features in both stages, and swapping the assignments. These comparisons would help isolate and better understand contribution of each component.
(2) Please clarify the difference in official TrackTrack (Shim et al., CVPR 2025) and its reimplementation, what causes the gap to the published results? Also does the method still works i.e. gives similar gains against release and config, at least on MOT17 or DanceTrack validation?
5 comments
The difference appears marginal, is it even consistent across multiple seeds?
Thank you for the follow-up. Both trackers use the same fixed detections generated by a publicly released detector and the same ReID features. With these inputs fixed, the tracking stage, including our enhancement module, has no seed-dependent steps, so the reported results do not depend on the choice of random seed under this evaluation setup.
To complement the HOTA results in Table R4, we report IDF1 and AssA gains over our TrackTrack reproduction under the same evaluation protocol.
| Test set | IDF1 gain (points) | AssA gain (points) |
|---|---|---|
| MOT17 | +0.8 | +1.2 |
| DanceTrack | +1.3 | +2.1 |
| On MOT20, where dense crowds and frequent occlusions make identity association challenging, SpecHyper-Track improves all reported metrics over our TrackTrack reproduction. With the same enhancement parameters across datasets, it also improves HOTA on all three test sets. |
Q1. Motivation and Benefits of Track-State-Aware Feature Routing
Established tracks have accumulated appearance observations, so we use high-frequency-enhanced features (Xh) to distinguish easily confused candidates. For unconfirmed tracks with shorter appearance histories, we use fused features (Xf), which retain these discriminative cues and add within-group context. To isolate the effect of routing, we varied only the feature assignment, keeping feature construction, conditional activation, and post-processing fixed.
Table R1. Routing ablation on the MOT17 ablation split
The proposed routing improves IDF1 by 0.5-0.8 points and AssA by 0.3-0.7 points across the three alternatives.
Q2. Published TrackTrack results and matched-protocol comparison
We reproduced TrackTrack using the authors' released code and configuration parameters. Within each dataset, we ran our TrackTrack reproduction and SpecHyper-Track on the same machine using identical detection inputs, ReID features, and evaluation settings.
Table R2. HOTA comparison of published TrackTrack, reproduced TrackTrack, and SpecHyper-Track on the MOT17 and DanceTrack test sets.
Using the same relation construction and frequency enhancement parameters on both test sets, SpecHyper-Track improves HOTA over our matched-protocol TrackTrack reproduction on both MOT17 and DanceTrack and achieves a HOTA score close to the published TrackTrack result on MOT17. It also improves IDF1 and AssA by 0.8 and 1.2 points on MOT17 and by 1.3 and 2.1 points on DanceTrack, respectively. We will revise Sec. 3.2 to report the published, reproduced, and augmented results side by side.