Papers › Filter Response Normalization Layer: Eliminating Batch Dependence in the Training of...

Filter Response Normalization Layer: Eliminating Batch Dependence in the Training of Deep Neural Networks

21 Nov 2019CVPR 2020 6arXiv:1911.09737archive 2025-07-28

Saurabh Singh, Shankar Krishnan

Batch Normalization (BN) uses mini-batch statistics to normalize the activations during training, introducing dependence between mini-batch elements. This dependency can hurt the performance if the mini-batch size is too small, or if the elements are correlated. Several alternatives, such as Batch Renormalization and Group Normalization (GN), have been proposed to address this issue. However, they either do not match the performance of BN for large batches, or still exhibit degradation in performance for smaller batches, or introduce artificial constraints on the model architecture. In this paper we propose the Filter Response Normalization (FRN) layer, a novel combination of a normalization and an activation function, that can be used as a replacement for other normalizations and activations. Our method operates on each activation channel of each batch element independently, eliminating the dependency on other batch elements. Our method outperforms BN and other alternatives in a variety of settings for all batch sizes. FRN layer performs ≈0.7-1.0% better than BN on top-1 validation accuracy with large mini-batch sizes for Imagenet classification using InceptionV3 and ResnetV2-50 architectures. Further, it performs >1% better than GN on the same problem in the small mini-batch size regime. For object detection problem on COCO dataset, FRN layer outperforms all other methods by at least 0.3-0.5% in all batch size regimes.

PaperPDFConference PDFCodeCode Syntology ran

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):

Code

Syntology 2 code samples harvested from 2 repositories linked to this paper: 2 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 2 where Syntology's instrument failed) · 0 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; 1 where the contract check could not run; failures of Syntology's instrument, not of the code. Every run on this page is a failure of Syntology's instrument, not of the code.

By repository: community (archive-listed): 2 samples from 2 repositories, 2 ran (0 with no instrument failure; 2 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 3 of its repositories that Syntology harvested for other papers:

Levels written on 2026-09-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

16 repositories listed; official and paper-mentioned ones first.

CarloLepelaars/filter_response_normalization_keras mentioned on GitHubMITSyntology: not harvested report
EmptySamurai/pytorch-reconet mentioned on GitHubpytorchMITSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Analyzing and Improving the Image Quality of StyleGAN (arXiv:1912.04958; that paper's own run record: 68 ran (of which 0 constructed an object rather than computing a result; 48 with no instrument failure: 4 honoured, 6 violated, 38 with no contract checked; 20 where Syntology's instrument failed) · 24 unverified); nothing checks that they implement this paper's method. report
SdahlSean/FilterResponseNormalizationTensorflow mentioned on GitHubtfSyntology: not harvested report
amirbar/FilterResponseNormalization mentioned on GitHubtfSyntology: not harvested report
gakkiri/Filter-Response-Normalization mentioned on GitHubpytorchMITSyntology: not harvested report
gupta-abhay/pytorch-frn mentioned on GitHubpytorchMITSyntology: not harvested report
kobiso/FilterResponseNorm-MXNet mentioned on GitHubmxnetMITSyntology: not harvested report
philipperemy/keras-frn mentioned on GitHubtfSyntology: 1 sample, 1 ran (1 instrument-failed) · 0 unverified report
ppwwyyxx/FRN-on-common-ImageNet-baseline mentioned on GitHubtfSyntology: not harvested report
tattaka/Filter-Response-Normalization-PyTorch mentioned on GitHubpytorchSyntology: 1 sample, 1 ran (1 instrument-failed) · 0 unverified report
2023-MindSpore-1/ms-code-216 mindsporeSyntology: not harvested report
2023-MindSpore-4/Code11 mindsporeSyntology: not harvested report
2023-MindSpore-4/Code14 mindsporeSyntology: not harvested report
MindSpore-paper-code-3/code5 mindsporeSyntology: not harvested report
ensta-u2is/torch-uncertainty pytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Training independent subnetworks for robust prediction (arXiv:2010.06610; that paper's own run record: 4 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 3 honoured, 0 violated, 1 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified), On the Pitfalls of Heteroscedastic Uncertainty Estimation with Probabilistic Neural Networks (arXiv:2203.09168; that paper's own run record: 2 ran (of which 0 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) and Tailoring Mixup to Data for Calibration (arXiv:2311.01434; that paper's own run record: 6 ran (of which 2 constructed an object rather than computing a result; 6 with no instrument failure: 3 honoured, 1 violated, 2 with no contract checked; 0 where Syntology's instrument failed) · 3 unverified); nothing checks that they implement this paper's method. report
mindspore-ai/models mindsporeSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to AdaBin: Improving Binary Neural Networks with Adaptive Binary Sets (arXiv:2208.08084; that paper's own run record: 4 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified); nothing checks that they implement this paper's method. report

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

2 samples harvested: 2 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 2 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Every run on this page is a failure 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.

1ran · our draft was wrong
1ran; the contract check could not run

Licence: 0 of the 2 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 2 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”. “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.

philipperemy/keras-frn community (archive-listed) 1 sample, 1 ran (1 instrument-failed) · 0 unverified
frn_layer_paper frn/frn.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant fingerprinted MIT (permissive) · d799bca8504332a9 · report fixture: signature x:EagerTensor/4/float, tau:EagerTensor/0/float, beta:EagerTensor/0/float, gamma:EagerTensor/0/float, epsilon:float/0/float · returned EagerTensor · level recorded 2026-09-22
tattaka/Filter-Response-Normalization-PyTorch community (archive-listed) 1 sample, 1 ran (1 instrument-failed) · 0 unverified
convert_model in 14 papers filter_response_normalization/filter_response_normalize.py ran · our draft was wrong MIT (permissive) · c9a5f3feedf35dc9 · report fixture: signature module:callable/0/? · returned SimpleModel · level recorded 2026-09-22

Tasks

Image ClassificationObject Detectionobject-detection

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Image Classification ImageNet InceptionV3 (FRN layer) Top 1 Accuracy 78.95% #796 of 1060 Archive leaderboard report
Image Classification ImageNet ResnetV2 50 (FRN layer) Top 1 Accuracy 77.21% #878 of 1060 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

Methods

Introduced by this paper: Filter Response Normalization

1x1 ConvolutionAuxiliary ClassifierAverage PoolingBatch NormalizationBottleneck Residual BlockConvolutionDense ConnectionsDropoutFPNFilter Response NormalizationFocal LossGlobal Average PoolingInception-v3Inception-v3 ModuleKaiming InitializationLabel SmoothingLinear Warmup With Cosine AnnealingMax PoolingRMSPropReLUResidual BlockResidual ConnectionRetinaNetSoftmax

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