Methods › General › Prioritized Sampling › ATSS › Papers where code ran, page 1
Adaptive Training Sample Selection
ATSS
Papers archive 2025-07-28
archive papers tagged: 16 · with a code link: 13 · where Syntology ran a sample: 5 (5 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument) Syntology
Show: all tagged papersonly where code ran (5 of 16 tagged: 5 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument)
Syntology We ran code from the paper's repository; we did not isolate this method inside it.
Page 1 of 1: papers 1 to 5 of the 5 tagged papers where Syntology ran at least one harvested sample (5 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument), newest first by the archive's date (ties by arXiv id). This is a filter on Syntology's record ordered by date only, not a ranking; a run is not a correctness claim. A paper missing from this list is not a recorded non-run: it may have no arXiv id, no harvested code, or only samples that have not run yet.
Repository counts are the archive's code-links table. A Syntology line states what Syntology ran from that paper's harvested code, as “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the instrument figure counts failures of Syntology's instrument, not of the code. It is per sample and not a correctness claim. When the archive marks a repository official for the paper, the line starts with that repository's state (the archive's flag, not a verdict on who wrote the code; “community repositories only” when every sample that ran came from a community repository, “official: no sample here; runs from other or unrecorded repositories” when some came from a repository the paper names or has in its text, or from none recorded); hover it for the repositories the samples that ran came from.
-
DETRs with Collaborative Hybrid Assignments Training 22 Nov 2022 · 6 repositories · arXiv:2211.12860Syntology 4 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified (of 5 harvested samples)
-
TOOD: Task-aligned One-stage Object Detection 17 Aug 2021 · 6 repositories · arXiv:2108.07755Syntology official (archive's flag): 1 ran · 2 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 1 where Syntology's instrument failed) · 2 unverified (of 4 harvested samples) · 3 pointer-only (licence)
-
RelationNet++: Bridging Visual Representations for Object Detection via Transformer Decoder 29 Oct 2020 · 4 repositories · arXiv:2010.15831Syntology official (archive's flag): 4 ran · 4 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified (of 5 harvested samples)
-
Generalized Focal Loss: Learning Qualified and Distributed Bounding Boxes for Dense Object Detection 8 Jun 2020 · 7 repositories · arXiv:2006.04388Syntology community repositories only · 22 ran (of which 0 constructed an object rather than computing a result; 22 with no instrument failure: 0 honoured, 0 violated, 22 with no contract checked; 0 where Syntology's instrument failed) · 2 unverified (of 24 harvested samples) · 2 pointer-only (licence)
-
Bridging the Gap Between Anchor-based and Anchor-free Detection via Adaptive Training Sample Selection 5 Dec 2019 · 13 repositories · arXiv:1912.02424Syntology community repositories only · 4 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified (of 4 harvested samples)