- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
PCIA-Track addresses identity confusion in memory-based visual tracking by delaying identity decisions until evidence becomes clearer after a conflict. It preserves the track's memory while continuing to report predictions, then uses backward replay to check whether a competing track reconnects to the target's earlier stable history. The framework augments an existing segmentation-based tracker without additional training. Benchmark comparisons, component ablations, and analyses of individual arbitration outcomes report overall tracking gains while showing that the benefit of retrospective identity correction varies across datasets.
Critical strengths
- The distinction between preserving predictions during a conflict and deciding identity afterward is well motivated and operationally precise (Sections 3.3–3.4). Table 12 supports reporting with duplicate suppression: +0.136 Q-points, with a positive bootstrap interval, relative to withholding all held outputs.
- The paper provides unusually transparent analysis: component removals, evaluator and mask-to-box checks, and explicit failed hand-overs (Appendices A–E). The complete system improves over SAM 3 on all five benchmarks in Table 1 and reaches 0.7352 Q on VOTS2026.
Critical weaknesses
- The central arbitration mechanism has limited demonstrated reliability. Only two of four LVOSv2 hand-overs and one of two DiDi hand-overs are correct; its entire VOTS2026 gain comes from one sequence, and it lowers DiDi Q by 0.37 points (Section 5, Appendix E). Incorrect reference histories also defeat recovery when a correct candidate exists. These results support occasional useful correction more strongly than broadly reliable identity resolution.
- The headline gains compare against plain SAM 3, whereas the implementation inherits SAFEDAM's memory and candidate machinery (Section 3.1). Table 2 removes components individually but does not report the identical base with all three additions disabled; Table 3's published SAFEDAM result does not supply that controlled comparison. Consequently, the combined contribution of the proposed additions is not cleanly separated from the inherited tracker.
Questions for authors
- Clarification: What are the results of the identical implementation with SCF, HaR, and PCIA all disabled, under the same evaluation protocols?