Methods › General › Normalization › Layer Normalization

Layer Normalization

24,980 papers tagged archive 2025-07-28

Introduced by Jimmy Lei Ba et al. in Layer Normalization

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

Unlike batch normalization, Layer Normalization directly estimates the normalization statistics from the summed inputs to the neurons within a hidden layer so the normalization does not introduce any new dependencies between training cases. It works well for RNNs and improves both the training time and the generalization performance of several existing RNN models. More recently, it has been used with Transformer models.

We compute the layer normalization statistics over all the hidden units in the same layer as follows:

μˡ = 1/H∑ᴴᵢ₌₁aᵢˡ

σˡ = √(1/H∑ᴴᵢ₌₁(aᵢˡ-μˡ)²)

where H denotes the number of hidden units in a layer. Under layer normalization, all the hidden units in a layer share the same normalization terms μ and σ, but different training cases have different normalization terms. Unlike batch normalization, layer normalization does not impose any constraint on the size of the mini-batch and it can be used in the pure online regime with batch size 1.

PaperSourceSee Code · CyberZHG/torch-layer-normalization

In Syntology repository known, no verified implementation (declared_code; repositories: 5 listed of 34 in the graph, strongest link: mentioned on GitHub). This answer is about arXiv:1607.06450, the paper the archive credits with this method.

Code Syntology holds under other names, as the lookup lists them (code_nearby); not a complete list, and none of them is this method.

Origin paper of this answer, arXiv:1607.06450 (its page on this site · its page on Syntology): Syntology's run record for its harvested code, 7 ran (of which 5 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 0 violated, 7 with no contract checked; 0 where Syntology's instrument failed) · 10 unverified (of 17 harvested samples) · 8 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: 24,980 · with a code link: 11,273 · where Syntology ran a sample: 3,471 (2,817 with a run with no instrument failure, 654 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran (3,471 of 24,980 tagged: 2,817 with a run with no instrument failure, 654 where every run was a failure of Syntology's instrument)

Page 1 of 250: papers 1 to 100 of 24,980, 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 2,597 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
Language Modelling3,010
Language Modeling2,355
Retrieval1,818
Question Answering1,490
Decoder1,393
RAG1,355
Sentence1,334
Retrieval-augmented Generation1,176
Translation1,035
Machine Translation925
Semantic Segmentation862
Large Language Model841
Text Generation763
Image Classification720
Transfer Learning715
Object Detection668
Representation Learning622
Sentiment Analysis608
Classification597
object-detection597

Usage over time archive 2025-07-28

Papers per year tagged with Layer Normalization: 2016 to 2025, peak 6,979 6,979 0 2016: 2 papers 2016 2017: 26 papers 2017 2018: 130 papers 2018 2019: 1074 papers 2019 2020: 2146 papers 2020 2021: 3163 papers 2021 2022: 3357 papers 2022 2023: 5282 papers 2023 2024: 6979 papers 2024 2025: 2821 papers 2025
Papers per year the archive tags with this method, by the paper's archive date (24,980 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