Methods › General › Normalization › Batch Normalization

Batch Normalization

6,287 papers tagged archive 2025-07-28

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

Batch Normalization aims to reduce internal covariate shift, and in doing so aims to accelerate the training of deep neural nets. It accomplishes this via a normalization step that fixes the means and variances of layer inputs. Batch Normalization also has a beneficial effect on the gradient flow through the network, by reducing the dependence of gradients on the scale of the parameters or of their initial values. This allows for use of much higher learning rates without the risk of divergence. Furthermore, batch normalization regularizes the model and reduces the need for Dropout.

We apply a batch normalization layer as follows for a minibatch ℬ:

μ_ℬ = 1/m∑ᵐᵢ₌₁xᵢ

σ²_ℬ = 1/m∑ᵐᵢ₌₁(xᵢ-μ_ℬ)²

x̂ᵢ = (xᵢ - μ_ℬ)/(√(σ²_ℬ+ϵ))

yᵢ = γx̂ᵢ + β= BN_(γ, β)(xᵢ)

Where γ and β are learnable parameters.

Source: Batch Normalization: Accelerating Deep Network Training...See Code · google/jax

In Syntology repository known, no verified implementation (declared_code; repositories: 5 listed of 66 in the graph, strongest link: mentioned on GitHub). The archive credits no paper with an arXiv id for this method, so whether this answer (about arXiv:1502.03167) is about this method is not checked.

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:1502.03167 (its page on this site · its page on Syntology): Syntology's run record for its harvested code, 19 ran (of which 5 constructed an object rather than computing a result; 14 with no instrument failure: 0 honoured, 0 violated, 14 with no contract checked; 5 where Syntology's instrument failed) · 2 unverified (of 21 harvested samples) · 5 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: 6,287 · with a code link: 2,771 · where Syntology ran a sample: 742 (621 with a run with no instrument failure, 121 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran (742 of 6,287 tagged: 621 with a run with no instrument failure, 121 where every run was a failure of Syntology's instrument)

Page 1 of 63: papers 1 to 100 of 6,287, 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 1,316 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
Image Classification702
Object Detection608
Semantic Segmentation598
object-detection548
image-classification536
Segmentation408
Transfer Learning344
General Classification320
Classification300
Data Augmentation268
Object257
Deep Learning220
Reinforcement Learning (RL)209
Self-Supervised Learning207
reinforcement-learning197
Image Generation190
Representation Learning189
Contrastive Learning187
Reinforcement Learning182
Quantization180

Usage over time archive 2025-07-28

Papers per year tagged with Batch Normalization: 2015 to 2025, peak 1,107 1,107 0 2015: 14 papers 2015 2016: 72 papers 2016 2017: 194 papers 2017 2018: 439 papers 2018 2019: 729 papers 2019 2020: 1039 papers 2020 2021: 1107 papers 2021 2022: 942 papers 2022 2023: 879 papers 2023 2024: 655 papers 2024 2025: 217 papers 2025
Papers per year the archive tags with this method, by the paper's archive date (6,287 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