Methods › General › Large Batch Optimization › Adafactor › Papers where code ran, page 2
Adafactor
Papers archive 2025-07-28
archive papers tagged: 733 · with a code link: 363 · where Syntology ran a sample: 103 (89 with a run with no instrument failure, 14 where every run was a failure of Syntology's instrument) Syntology
Show: all tagged papersonly where code ran (103 of 733 tagged: 89 with a run with no instrument failure, 14 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 2 of 2: papers 101 to 103 of the 103 tagged papers where Syntology ran at least one harvested sample (89 with a run with no instrument failure, 14 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.
-
Reformer: The Efficient Transformer 13 Jan 2020 · 10 repositories · arXiv:2001.04451Syntology community repositories only · 6 ran (of which 1 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 5 where Syntology's instrument failed) · 2 unverified (of 8 harvested samples)
-
Exploring the Limits of Transfer Learning with a Unified Text-to-Text Transformer 23 Oct 2019 · 57 repositories · arXiv:1910.10683Syntology 21 ran (of which 0 constructed an object rather than computing a result; 20 with no instrument failure: 1 honoured, 0 violated, 19 with no contract checked; 1 where Syntology's instrument failed) · 10 unverified (of 31 harvested samples)
-
Adafactor: Adaptive Learning Rates with Sublinear Memory Cost 11 Apr 2018 · 5 repositories · arXiv:1804.04235Syntology 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)