Methods › General › Initialization › T-Fixup
T-Fixup
Introduced by Xiao Shi Huang et al. in Improving Transformer Optimization Through Better Initialization
archive 2025-07-28 Description, source and code snippet are the archive's method entry.
T-Fixup is an initialization method for Transformers that aims to remove the need for layer normalization and warmup. The initialization procedure is as follows:
- Apply Xavier initialization for all parameters excluding input embeddings. Use Gaussian initialization 𝒩(0, d^(-1/2)) for input embeddings where d is the embedding dimension.
- Scale v_d and w_d matrices in each decoder attention block, weight matrices in each decoder MLP block and input embeddings x and y in encoder and decoder by (9 N)^(-1/4)
- Scale vₑ and wₑ matrices in each encoder attention block and weight matrices in each encoder MLP block by 0.67 N^(-1/4)
In Syntology name not resolved (unknown_name). The lookup matched no method, paper or venue by this name; that asserts nothing about whether code exists.
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.
Papers archive 2025-07-28
archive papers tagged: 2 · with a code link: 2 · where Syntology ran a sample: 0 (0 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument) Syntology
Show: all tagged papersonly where code ran: none of the 2 tagged papers has a Syntology run on record
Page 1 of 1: papers 1 to 2 of 2, 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.
-
Optimizing Deeper Transformers on Small Datasets 30 Dec 2020 · 1 repository · arXiv:2012.15355
-
Improving Transformer Optimization Through Better Initialization 1 Jan 2020 · 1 repository
Tasks archive 2025-07-28
10 tasks the archive attaches to papers tagged with this method, by distinct papers. A task without a page in the catalog is plain text.
| Task | Papers |
|---|---|
| Decoder | 1 |
| Language Modeling | 1 |
| Language Modelling | 1 |
| Machine Translation | 1 |
| Reading Comprehension | 1 |
| SQL Parsing | 1 |
| Semantic Parsing | 1 |
| Text to SQL | 1 |
| Text-To-SQL | 1 |
| Translation | 1 |
Usage over time archive 2025-07-28
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
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