Papers › Layer Normalization
Layer Normalization
Jimmy Lei Ba, Jamie Ryan Kiros, Geoffrey E. Hinton
Training state-of-the-art, deep neural networks is computationally expensive. One way to reduce the training time is to normalize the activities of the neurons. A recently introduced technique called batch normalization uses the distribution of the summed input to a neuron over a mini-batch of training cases to compute a mean and variance which are then used to normalize the summed input to that neuron on each training case. This significantly reduces the training time in feed-forward neural networks. However, the effect of batch normalization is dependent on the mini-batch size and it is not obvious how to apply it to recurrent neural networks. In this paper, we transpose batch normalization into layer normalization by computing the mean and variance used for normalization from all of the summed inputs to the neurons in a layer on a single training case. Like batch normalization, we also give each neuron its own adaptive bias and gain which are applied after the normalization but before the non-linearity. Unlike batch normalization, layer normalization performs exactly the same computation at training and test times. It is also straightforward to apply to recurrent neural networks by computing the normalization statistics separately at each time step. Layer normalization is very effective at stabilizing the hidden state dynamics in recurrent networks. Empirically, we show that layer normalization can substantially reduce the training time compared with previously published techniques.
In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.
Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.
For agents, on Syntology's MCP service (how to connect):
get_harvested_code_for_paper(arxiv_id="1607.06450")get_code(code_sha256="…")with a sample'scode_sha256from the list belowget_citation_path(paper_1="1607.06450", paper_2="…")with another paper's arXiv id or titleget_concepts_for_paper(arxiv_id="1607.06450")
Code
Syntology 17 code samples harvested from 10 repositories linked to this paper: 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. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.
By repository: community (archive-listed): 17 samples from 10 repositories, 7 ran (7 with no instrument failure; 0 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.
No sample is linked to this paper from 14 of its repositories that Syntology harvested for other papers:
- JonasRSV/DDPG, community (archive-listed): harvested for 2 other papers, listed under the repository
- JonasRSV/DQNTensorflow, community (archive-listed): harvested for another paper, listed under the repository
- Waino/hnmt, community (archive-listed): harvested for another paper, listed under the repository
- bzhangGo/rmsnorm, community (archive-listed): harvested for another paper, listed under the repository
- dhesenkamp/attentive-lstm, community (archive-listed): harvested for another paper, listed under the repository
- iejMac/ScriptWriter, community (archive-listed): harvested for another paper, listed under the repository
- jiamings/fast-weights, community (archive-listed): harvested for another paper, listed under the repository
- lmnt-com/haste, community (archive-listed): harvested for another paper, listed under the repository
- MindCode-4/code-7, community (archive-listed): harvested for another paper, listed under the repository
- MindSpore-scientific-2/code-12, community (archive-listed): harvested for another paper, listed under the repository
- labmlai/annotated_deep_learning_paper_implementations, community (archive-listed): harvested for 15 other papers, listed under the repository
- mindspore-ai/contrib, community (archive-listed): harvested for another paper, listed under the repository
- nanzhaogang/contrib, community (archive-listed): harvested for another paper, listed under the repository
- vpj/jax_transformer, community (archive-listed): harvested for 2 other papers, listed under the repository
Levels written between 2026-09-22 and 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.
34 repositories listed; official and paper-mentioned ones first.
Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.
A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.
Code Syntology ran Syntology
17 samples harvested: 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. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.
Licence: 8 of the 17 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.
Harvested from 10 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. For 2 samples that ran, the graph records a signature this page does not show: for a class the fixture built without calling, the harness called the object with inputs it made up itself, so the recorded signature is the harness's probe, not the fixture's arguments. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.
Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.
Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.
A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.
94ce18ebe841264e · report
fixture: returned LayerNorm2D · level recorded 2026-09-22 0050dfbf8ad7677a · report
ea323f4fc8005e6d · report
fixture: returned LayerNormLayer · level recorded 2026-09-22 7d881e4088f29595 · report
fixture: returned GraphNorm · level recorded 2026-09-22 b29f84a895c28c9c · report
fixture: signature hidden_size:int/0/int, init_state_learned:bool/0/bool, device:NoneType/0/? · returned tuple · level recorded 2026-09-26 f1b57d3c5218cd84 · report
fixture: signature length_tensor:Tensor/1/int, max_length:NoneType/0/? · returned Tensor · level recorded 2026-09-26 census: 5 implementations from 5 papers, 5 distinct outputs across 3 buckets, one shared input per bucket LayerNorm.py ran no licence file found · pointer only ·
74c1444feed033d0 · report
fixture: returned LayerNorm · level recorded 2026-09-22 def0b163983628e2 · report
fixture: returned layer_norm · level recorded 2026-09-22 29bb6248ac270983 · report
caa1927febb58775 · report
f61aa475517589c3 · report
56c490283a6d5297 · report
80444e734e109863 · report
Method as code Syntology
What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it. Siblings are assemblies lifted from this paper in the same batch for the same method: alternative readings kept side by side; none replaces or supersedes another.
9 assemblies on this paper: 9 harvested, 0 generated, listed in 1 groups (siblings lifted in one batch form one group).
9 sibling assemblies for Layer Normalization (harvested), lifted in the same batch on 2026-09-09: alternative readings kept side by side; none replaces or supersedes another.
harvested Assembly for Layer Normalization (graph method: Layer Normalization). 1 brick; individually on a fixture: 0 ran · 1 unverified. The assembly has not been run end-to-end.
one of 9 siblings
- LayerNormGRUCell entry · level 0 · unverified ·
4455b0c0adbcbe75
harvested Assembly for Layer Normalization (graph method: Layer Normalization). 2 bricks; individually on a fixture: 2 ran (of which 2 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified; every one of the 2 samples that ran constructed an object rather than computing a result. The assembly has not been run end-to-end.
one of 9 siblings
- LayerNorm entry · level 1 · ran ·
74c1444feed033d0 - layer_norm helper · level 1 · ran ·
def0b163983628e2
harvested Assembly for Layer Normalization (graph method: Layer Normalization). 1 brick; individually on a fixture: 1 ran (of which 1 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified; the one sample that ran constructed an object rather than computing a result. The assembly has not been run end-to-end.
one of 9 siblings
- LayerNormLayer entry · level 1 · ran ·
ea323f4fc8005e6d
harvested Assembly for Layer Normalization (graph method: Layer Normalization). 2 bricks; individually on a fixture: 1 ran (of which 1 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified; the one sample that ran constructed an object rather than computing a result. The assembly has not been run end-to-end.
one of 9 siblings
harvested Assembly for Layer Normalization (graph method: Layer Normalization). 1 brick; individually on a fixture: 0 ran · 1 unverified. The assembly has not been run end-to-end.
one of 9 siblings
- layer_norm entry · level 0 · unverified ·
0050dfbf8ad7677a
harvested Assembly for Layer Normalization (graph method: Layer Normalization). 1 brick; individually on a fixture: 0 ran · 1 unverified. The assembly has not been run end-to-end.
one of 9 siblings
- group_norm entry · level 0 · unverified ·
29bb6248ac270983
harvested Assembly for Layer Normalization (graph method: Layer Normalization). 1 brick; individually on a fixture: 1 ran (of which 1 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified; the one sample that ran constructed an object rather than computing a result. The assembly has not been run end-to-end.
one of 9 siblings
- LayerNorm2D entry · level 1 · ran ·
94ce18ebe841264e
harvested Assembly for Layer Normalization (graph method: Layer Normalization). 1 brick; individually on a fixture: 0 ran · 1 unverified. The assembly has not been run end-to-end.
one of 9 siblings
- LayerNormLayer entry · level 0 · unverified ·
c12ea25352a4dd86
harvested Assembly for Layer Normalization (graph method: Layer Normalization). 4 bricks; individually on a fixture: 0 ran · 4 unverified. The assembly has not been run end-to-end.
one of 9 siblings
- layer_norm entry · level 0 · unverified ·
caa1927febb58775 - layer_norm_compute helper · level 0 · unverified ·
f61aa475517589c3 - layer_norm_compute_python helper · level 0 · unverified ·
80444e734e109863 - layer_norm_compute_grad helper · level 0 · unverified ·
56c490283a6d5297
Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="1607.06450") returns these assemblies with each brick's role and wiring (how to connect).
Results from the paper archive 2025-07-28
No leaderboard rows for this paper in the archive.
Methods
Introduced by this paper: Layer 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