Papers › Dual PatchNorm

Dual PatchNorm

2 Feb 2023arXiv:2302.01327archive 2025-07-28

Manoj Kumar, Mostafa Dehghani, Neil Houlsby

We propose Dual PatchNorm: two Layer Normalization layers (LayerNorms), before and after the patch embedding layer in Vision Transformers. We demonstrate that Dual PatchNorm outperforms the result of exhaustive search for alternative LayerNorm placement strategies in the Transformer block itself. In our experiments, incorporating this trivial modification, often leads to improved accuracy over well-tuned Vision Transformers and never hurts.

PaperPDFCodeCode 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

No sample from the archive's official repository (google-research/big_vision) is linked to this paper; the 9 samples below come from 2 community repositories. Syntology harvested code from google-research/big_vision for 7 other papers.

google-research/big_vision: Syntology's graph links these samples to How to train your ViT? Data, Augmentation, and Regularization in Vision Transformers (arXiv:2106.10270; that paper's own run record: 2 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 1 honoured, 0 violated, 0 with no contract checked; 1 where Syntology's instrument failed) · 0 unverified), UViM: A Unified Modeling Approach for Vision with Learned Guiding Codes (arXiv:2205.10337; that paper's own run record: 2 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; 1 where Syntology's instrument failed) · 1 unverified), PaLI: A Jointly-Scaled Multilingual Language-Image Model (arXiv:2209.06794; that paper's own run record: 2 ran (of which 1 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 1 violated, 1 with no contract checked; 0 where Syntology's instrument failed) · 2 unverified) and 4 more (every one in this page's JSON twin); nothing checks that they implement this paper's method.

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

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

Levels written between 2026-09-22 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 2 of the 7 samples that ran have no recorded date.

google-research/big_vision officialmentioned in papermentioned on GitHubjaxSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to How to train your ViT? Data, Augmentation, and Regularization in Vision Transformers (arXiv:2106.10270; that paper's own run record: 2 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 1 honoured, 0 violated, 0 with no contract checked; 1 where Syntology's instrument failed) · 0 unverified), UViM: A Unified Modeling Approach for Vision with Learned Guiding Codes (arXiv:2205.10337; that paper's own run record: 2 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; 1 where Syntology's instrument failed) · 1 unverified), PaLI: A Jointly-Scaled Multilingual Language-Image Model (arXiv:2209.06794; that paper's own run record: 2 ran (of which 1 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 1 violated, 1 with no contract checked; 0 where Syntology's instrument failed) · 2 unverified) and 4 more (every one in this page's JSON twin); nothing checks that they implement this paper's method. report
lucidrains/MEGABYTE-pytorch mentioned on GitHubpytorchMITSyntology: 4 samples, 3 ran (1 instrument-failed) · 1 unverified report
lucidrains/denoising-diffusion-pytorch mentioned on GitHubpytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Denoising Diffusion Probabilistic Models (arXiv:2006.11239; that paper's own run record: 186 ran (of which 81 constructed an object rather than computing a result; 142 with no instrument failure: 20 honoured, 8 violated, 114 with no contract checked; 44 where Syntology's instrument failed) · 67 unverified), Building Normalizing Flows with Stochastic Interpolants (arXiv:2209.15571; that paper's own run record: 5 ran (of which 3 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 0 violated, 3 with no contract checked; 2 where Syntology's instrument failed) · 2 unverified) and Can denoising diffusion probabilistic models generate realistic astrophysical fields? (arXiv:2211.12444; that paper's own run record: 3 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 1 honoured, 2 violated, 0 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified); nothing checks that they implement this paper's method. report
lucidrains/musiclm-pytorch mentioned on GitHubpytorchMITSyntology: 5 samples, 4 ran (0 instrument-failed) · 1 unverified report
lucidrains/phenaki-pytorch mentioned on GitHubpytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to MaskGIT: Masked Generative Image Transformer (arXiv:2202.04200; that paper's own run record: 14 ran (of which 9 constructed an object rather than computing a result; 10 with no instrument failure: 0 honoured, 0 violated, 10 with no contract checked; 4 where Syntology's instrument failed) · 7 unverified), Improved Masked Image Generation with Token-Critic (arXiv:2209.04439; that paper's own run record: 6 ran (of which 2 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 0 violated, 3 with no contract checked; 3 where Syntology's instrument failed) · 4 unverified) and Phenaki: Variable Length Video Generation From Open Domain Textual Description (arXiv:2210.02399; that paper's own run record: 3 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 1 honoured, 2 violated, 0 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified); nothing checks that they implement this paper's method. report
lucidrains/recurrent-interface-network-pytorch mentioned on GitHubpytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Scalable Adaptive Computation for Iterative Generation (arXiv:2212.11972; that paper's own run record: 21 ran (of which 9 constructed an object rather than computing a result; 18 with no instrument failure: 8 honoured, 0 violated, 10 with no contract checked; 3 where Syntology's instrument failed) · 8 unverified); nothing checks that they implement this paper's method. report
osier0524/lottery-ticket-to-ddpm mentioned on GitHubpytorchSyntology: not harvested 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

9 samples harvested: 7 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 1 honoured, 4 violated, 1 with no contract checked; 1 where Syntology's instrument failed) · 2 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.

1ran · honoured contract
4ran · violated contract
1ran · our draft was wrong
1ran
2unverified

Licence: 2 of the 9 samples are pointer only, meaning Syntology does not serve that copy's text. For 2 of them, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. 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. 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.

lucidrains/MEGABYTE-pytorch community (archive-listed) 4 samples, 3 ran (1 instrument-failed) · 1 unverified
default in 430 papers MEGABYTE_pytorch/megabyte.py ran · violated contract fingerprinted MIT (permissive) here; the stored copy is pointer only · 60fff7c3c400d7ff · report fixture: signature val:int/0/int, d:int/0/int · returned int · level recorded, date not recorded
exists in 528 papers
census: 5 implementations from 103 papers, 1 distinct output on one shared input this sample: bucket 1 of 1, arg 1: rank 1, kind int, dtype int64
MEGABYTE_pytorch/attend.py ran · violated contract MIT (permissive) here; the stored copy is pointer only · aa5486a3650902d8 · report fixture: signature val:Tensor/1/int · returned bool · level recorded, date not recorded
once in 16 papers MEGABYTE_pytorch/attend.py ran · our draft was wrong MIT (permissive) · 52e10a7d6b0fa036 · report fixture: signature fn:callable/0/? · returned function · level recorded 2026-09-22
pack_one in 14 papers MEGABYTE_pytorch/megabyte.py unverified MIT (permissive) · 6182326691dd827b · report
lucidrains/musiclm-pytorch community (archive-listed) 5 samples, 4 ran (0 instrument-failed) · 1 unverified
all_gather_same_dim musiclm_pytorch/distributed.py ran MIT (permissive) · 444ef2a4a08a512e · report fixture: signature t:Tensor/2/float · returned list · level recorded 2026-09-25
cast_tuple in 58 papers musiclm_pytorch/trainer.py ran · honoured contract fingerprinted MIT (permissive) · 5cfcc1d3230706ff · report fixture: signature t:int/0/int · returned tuple · level recorded 2026-09-22
first in 17 papers musiclm_pytorch/musiclm_pytorch.py ran · violated contract fingerprinted MIT (permissive) · 0ff658860f6a6e4f · report fixture: signature it:list/1/int · returned int · level recorded 2026-09-22
yes_or_no in 10 papers musiclm_pytorch/trainer.py ran · violated contract MIT (permissive) · d95562c398a6b25e · report fixture: signature question:str/0/str · returned bool · level recorded 2026-09-22
all_gather_variable_dim musiclm_pytorch/distributed.py unverified MIT (permissive) · 68fd08f2f8ed9157 · report

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

Absolute Position EncodingsAdamAttentionBPEDense ConnectionsDropoutLabel SmoothingLayer NormalizationLinear LayerMulti-Head AttentionPosition-Wise Feed-Forward LayerResidual ConnectionSoftmaxTransformer

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