Methods › General › Activation Functions › SiLU › Papers where code ran, page 1
Sigmoid Linear Unit
SiLU
Papers archive 2025-07-28
archive papers tagged: 30 · with a code link: 16 · where Syntology ran a sample: 5 (4 with a run with no instrument failure, 1 where every run was a failure of Syntology's instrument) Syntology
Show: all tagged papersonly where code ran (5 of 30 tagged: 4 with a run with no instrument failure, 1 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 (4 with a run with no instrument failure, 1 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.
-
Sparsing Law: Towards Large Language Models with Greater Activation Sparsity 4 Nov 2024 · 1 repository · arXiv:2411.02335Syntology official (archive's flag): 5 ran · 5 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; 1 where Syntology's instrument failed) · 0 unverified (of 5 harvested samples)
-
Reducing Fine-Tuning Memory Overhead by Approximate and Memory-Sharing Backpropagation 24 Jun 2024 · 1 repository · arXiv:2406.16282Syntology official (archive's flag): 10 ran · 10 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; 0 where Syntology's instrument failed) · 11 unverified (of 21 harvested samples) · 3 pointer-only (licence)
-
Low Curvature Activations Reduce Overfitting in Adversarial Training 15 Feb 2021 · 1 repository · arXiv:2102.07861Syntology official: no sample here; runs from other or unrecorded repositories · 1 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; 1 where Syntology's instrument failed) · 1 unverified (of 2 harvested samples) · 2 pointer-only (licence)
-
Bottleneck Transformers for Visual Recognition 27 Jan 2021 · 13 repositories · arXiv:2101.11605Syntology 26 ran (of which 9 constructed an object rather than computing a result; 19 with no instrument failure: 1 honoured, 0 violated, 18 with no contract checked; 7 where Syntology's instrument failed) · 23 unverified (of 49 harvested samples) · 8 pointer-only (licence)
-
Searching for Activation Functions 16 Oct 2017 · 22 repositories · arXiv:1710.05941Syntology 13 ran (of which 1 constructed an object rather than computing a result; 8 with no instrument failure: 0 honoured, 0 violated, 8 with no contract checked; 5 where Syntology's instrument failed) · 7 unverified (of 20 harvested samples) · 4 pointer-only (licence)