Methods › General › Parameter Sharing › Weight Tying › Papers where code ran, page 1
Weight Tying
Papers archive 2025-07-28
archive papers tagged: 63 · with a code link: 30 · where Syntology ran a sample: 5 (3 with a run with no instrument failure, 2 where every run was a failure of Syntology's instrument) Syntology
Show: all tagged papersonly where code ran (5 of 63 tagged: 3 with a run with no instrument failure, 2 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 (3 with a run with no instrument failure, 2 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.
-
Approximately Equivariant Networks for Imperfectly Symmetric Dynamics 28 Jan 2022 · 1 repository · arXiv:2201.11969Syntology official (archive's flag): 2 ran · 2 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 2 where Syntology's instrument failed) · 0 unverified (of 2 harvested samples) · 2 pointer-only (licence)
-
Trellis Networks for Sequence Modeling 15 Oct 2018 · 1 repository · arXiv:1810.06682Syntology official (archive's flag): 7 ran · 7 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 2 honoured, 0 violated, 5 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified (of 8 harvested samples) · 2 pointer-only (licence)
-
Universal Language Model Fine-tuning for Text Classification 18 Jan 2018 · 66 repositories · arXiv:1801.06146Syntology community repositories only · 2 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 2 where Syntology's instrument failed) · 3 unverified (of 5 harvested samples) · 3 pointer-only (licence)
-
Breaking the Softmax Bottleneck: A High-Rank RNN Language Model 10 Nov 2017 · 9 repositories · arXiv:1711.03953Syntology official (archive's flag): 2 ran · 12 ran (of which 0 constructed an object rather than computing a result; 11 with no instrument failure: 0 honoured, 0 violated, 11 with no contract checked; 1 where Syntology's instrument failed) · 11 unverified (of 23 harvested samples) · 1 pointer-only (licence)
-
Regularizing and Optimizing LSTM Language Models 7 Aug 2017 · 45 repositories · arXiv:1708.02182Syntology community repositories only · 6 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 2 honoured, 0 violated, 0 with no contract checked; 4 where Syntology's instrument failed) · 1 unverified (of 7 harvested samples) · 7 pointer-only (licence)