Methods › General › Pruning › Spectral-Normalized Identity Priors
Spectral-Normalized Identity Priors
archive 2025-07-28 Description, source and code snippet are the archive's method entry.
Spectral-Normalized Identity Priors, or SNIP, is a structured pruning approach that penalizes an entire residual module in a Transformer model toward an identity mapping. It is applicable to any structured module, including a single attention head, an entire attention block, or a feed-forward subnetwork. The method identifies and discards unimportant non-linear mappings in the residual connections by applying a thresholding operator on the function norm. Furthermore, spectral normalization to stabilize the distribution of the post-activation values of the Transformer layers, further improving the pruning effectiveness of the proposed methodology.
In Syntology name not resolved (unknown_name). The lookup matched no method, paper or venue by this name; that asserts nothing about whether code exists.
Near matches the lookup lists, each a different name: Spectral-Normalized Identity Prior (SNIP); spectrally-normalized robust generalization bound; Spectral-normalized Neural Gaussian Process (SNGP); Spectral Theory of Normalized Corrected GNN Propagation; SpecTraL; SPECTRAL; SSC-Priors; Task Priors.
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: 1 · with a code link: 1 · 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 1 tagged papers has a Syntology run on record
Page 1 of 1: paper 1 of 1, 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.
-
Pruning Redundant Mappings in Transformer Models via Spectral-Normalized Identity Prior 5 Oct 2020 · 1 repository · arXiv:2010.01791
Tasks archive 2025-07-28
The archive attaches no task to a paper tagged with this method.
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