Methods › General › Activation Functions › E-swish
E-swish
Introduced by Eric Alcaide in E-swish: Adjusting Activations to Different Network Depths
archive 2025-07-28 Description, source and code snippet are the archive's method entry.
The archive carries no description for this method.
In Syntology for a different name, 'Swish', about another paper, arXiv:1710.05941: repository known, no verified implementation (declared_code; repositories: 5 listed of 22 in the graph, strongest link: mentioned on GitHub). The lookup matched a different name in Syntology's graph, 'Swish' (resolution: token_match); this answer is about that name. About another paper: this answer is about arXiv:1710.05941, while the archive credits arXiv:1801.07145.
Origin paper of this answer, arXiv:1710.05941 (its page on this site · its page on Syntology): Syntology's run record for its harvested code, 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). The instrument figure counts failures of Syntology's instrument, not of the code. Ran means executed on a synthesized input, not that the code is correct.
Syntology's have check for this name (free, it answers coverage only), read 2026-10-05; ask it again live. A level is the served verification level of that one answer; nothing here is summed across methods.
Papers archive 2025-07-28
archive papers tagged: 2 · with a code link: 2 · where Syntology ran a sample: 0 (0 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: none of the 2 tagged papers has a Syntology run on record
Page 1 of 1: papers 1 to 2 of 2, newest first by the archive's date (ties by slug), in archive order.
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.
-
EfficientPose: Scalable single-person pose estimation 25 Apr 2020 · 1 repository · arXiv:2004.12186
-
E-swish: Adjusting Activations to Different Network Depths 22 Jan 2018 · 1 repository · arXiv:1801.07145
Tasks archive 2025-07-28
3 tasks the archive attaches to papers tagged with this method, by distinct papers. A task without a page in the catalog is plain text.
| Task | Papers |
|---|---|
| 2D Human Pose Estimation | 1 |
| Computational Efficiency | 1 |
| Pose Estimation | 1 |
Usage over time archive 2025-07-28
Components: the archive holds no method-to-method composition, so PwC's Components table cannot be rebuilt; the Papers list carries no Results column for the same reason (the archive does not join its leaderboard rows to method tags).
Categories archive 2025-07-28
Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections