Methods › Computer Vision › Image Scaling Strategies › FixRes › Papers where code ran, page 1
FixRes
Papers archive 2025-07-28
archive papers tagged: 10 · with a code link: 10 · 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 10 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.
-
Three things everyone should know about Vision Transformers 18 Mar 2022 · 8 repositories · arXiv:2203.09795Syntology community repositories only · 1 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 1 violated, 0 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified (of 1 harvested sample)
-
Training data-efficient image transformers & distillation through attention 23 Dec 2020 · 40 repositories · arXiv:2012.12877Syntology community repositories only · 12 ran (of which 1 constructed an object rather than computing a result; 9 with no instrument failure: 1 honoured, 0 violated, 8 with no contract checked; 3 where Syntology's instrument failed) · 7 unverified (of 19 harvested samples) · 3 pointer-only (licence)
-
An Image is Worth 16x16 Words: Transformers for Image Recognition at Scale 22 Oct 2020 · 158 repositories · arXiv:2010.11929Syntology official: harvested, nothing ran · 307 ran (of which 165 constructed an object rather than computing a result; 286 with no instrument failure: 8 honoured, 2 violated, 276 with no contract checked; 21 where Syntology's instrument failed) · 112 unverified (of 419 harvested samples) · 154 pointer-only (licence)
-
Big Transfer (BiT): General Visual Representation Learning 24 Dec 2019 · 9 repositories · arXiv:1912.11370Syntology community repositories only · 9 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 1 violated, 6 with no contract checked; 2 where Syntology's instrument failed) · 1 unverified (of 10 harvested samples)
-
Self-training with Noisy Student improves ImageNet classification 11 Nov 2019 · 13 repositories · arXiv:1911.04252Syntology official (archive's flag): 6 ran · 13 ran (of which 0 constructed an object rather than computing a result; 10 with no instrument failure: 2 honoured, 0 violated, 8 with no contract checked; 3 where Syntology's instrument failed) · 11 unverified (of 24 harvested samples) · 2 pointer-only (licence)