Methods › General › Normalization › Weight Normalization

Weight Normalization

88 papers tagged archive 2025-07-28

Introduced by Tim Salimans et al. in Weight Normalization: A Simple Reparameterization to Accelerate Training of Deep Neural Networks

archive 2025-07-28 Description, source and code snippet are the archive's method entry.

Weight Normalization is a normalization method for training neural networks. It is inspired by batch normalization, but it is a deterministic method that does not share batch normalization's property of adding noise to the gradients. It reparameterizes each k-dimentional weight vector w in terms of a parameter vector v and a scalar parameter g and to perform stochastic gradient descent with respect to those parameters instead. Weight vectors are expressed in terms of the new parameters using:

w = g/(‖ textbfv‖)v

where v is a k-dimensional vector, g is a scalar, and ‖v‖ denotes the Euclidean norm of v. This reparameterization has the effect of fixing the Euclidean norm of the weight vector w: we now have ‖w‖= g, independent of the parameters v.

PaperSourceSee Code · pytorch/pytorch

In Syntology harvested code stored, below machine verification (unverified_code; harvested), served level V1; retrieve with get_harvested_code_for_paper(arxiv_id='1602.07868'). Repositories: 9 listed of 9 in the graph, strongest link: official. The lookup matched a paper by its title, arXiv:1602.07868, not a method entry. This answer is about arXiv:1602.07868, the paper the archive credits with this method.

Origin paper of this answer, arXiv:1602.07868 (its page on this site · its page on Syntology): Syntology's run record for its harvested code, 10 ran (of which 0 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 0 violated, 9 with no contract checked; 1 where Syntology's instrument failed) · 6 unverified (of 16 harvested samples) · 1 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.

What each level means, quoted from Syntology's server card: V0 “imports”; V1 “executes against a synthesized fixture and returns a value of the recorded type”; V2 “two implementations GENERATED from the paper's signature and spec agree numerically (1e-6) on fixture inputs” “neither of the two ever read the authors' own code, so V2 measures how unambiguously the paper specifies the method, not fidelity to the authors' implementation (measured 2026-09-11, commit 75eaa77: cross_checked_by is a second LLM on 2,628 of 2,831 served samples)”; V3 “paper-derived property tests pass on both of those same two generations.” The card adds: “No rung on this ladder compares the served code against the authors' implementation, so treat every level as evidence about runnability and internal agreement, not about matching the paper's results.” A level quoted in two parts is one definition the card writes as two clauses joined by a double hyphen, each clause quoted on its own (how these levels are quoted).

Papers archive 2025-07-28

archive papers tagged: 88 · with a code link: 45 · where Syntology ran a sample: 22 (18 with a run with no instrument failure, 4 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran (22 of 88 tagged: 18 with a run with no instrument failure, 4 where every run was a failure of Syntology's instrument)

Page 1 of 1: papers 1 to 88 of 88, 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.

Tasks archive 2025-07-28

20 shown of 101 tasks the archive attaches to papers tagged with this method, by distinct papers. A task without a page in the catalog is plain text.

TaskPapers
Speech Synthesis12
GPU7
Image Classification7
CPU6
Image Generation6
Quantization6
Text to Speech6
text-to-speech6
Decoder5
image-classification5
General Classification4
BIG-bench Machine Learning3
Machine Translation3
Model Compression3
Representation Learning3
Translation3
Audio Synthesis2
Classification2
Density Estimation2
Domain Adaptation2

Usage over time archive 2025-07-28

Papers per year tagged with Weight Normalization: 2016 to 2025, peak 19 19 0 2016: 4 papers 2016 2017: 7 papers 2017 2018: 5 papers 2018 2019: 14 papers 2019 2020: 19 papers 2020 2021: 13 papers 2021 2022: 9 papers 2022 2023: 5 papers 2023 2024: 10 papers 2024 2025: 2 papers 2025
Papers per year the archive tags with this method, by the paper's archive date (88 dated). Bars are counts, not a trend claim.

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

Normalization

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