Papers › iTransformer: Inverted Transformers Are Effective for Time Series Forecasting

iTransformer: Inverted Transformers Are Effective for Time Series Forecasting

10 Oct 2023arXiv:2310.06625archive 2025-07-28

Yong liu, Tengge Hu, Haoran Zhang, Haixu Wu, Shiyu Wang, Lintao Ma, Mingsheng Long

The recent boom of linear forecasting models questions the ongoing passion for architectural modifications of Transformer-based forecasters. These forecasters leverage Transformers to model the global dependencies over temporal tokens of time series, with each token formed by multiple variates of the same timestamp. However, Transformers are challenged in forecasting series with larger lookback windows due to performance degradation and computation explosion. Besides, the embedding for each temporal token fuses multiple variates that represent potential delayed events and distinct physical measurements, which may fail in learning variate-centric representations and result in meaningless attention maps. In this work, we reflect on the competent duties of Transformer components and repurpose the Transformer architecture without any modification to the basic components. We propose iTransformer that simply applies the attention and feed-forward network on the inverted dimensions. Specifically, the time points of individual series are embedded into variate tokens which are utilized by the attention mechanism to capture multivariate correlations; meanwhile, the feed-forward network is applied for each variate token to learn nonlinear representations. The iTransformer model achieves state-of-the-art on challenging real-world datasets, which further empowers the Transformer family with promoted performance, generalization ability across different variates, and better utilization of arbitrary lookback windows, making it a nice alternative as the fundamental backbone of time series forecasting. Code is available at this repository: https://github.com/thuml/iTransformer.

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 (thuml/iTransformer) is linked to this paper; the 10 samples below come from 2 community repositories. Syntology harvested code from thuml/iTransformer for another paper.

thuml/iTransformer: Syntology's graph links these samples to A Time Series is Worth 64 Words: Long-term Forecasting with Transformers (arXiv:2211.14730; that paper's own run record: 17 ran (of which 2 constructed an object rather than computing a result; 16 with no instrument failure: 0 honoured, 0 violated, 16 with no contract checked; 1 where Syntology's instrument failed) · 13 unverified); nothing checks that they implement this paper's method.

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

By repository: community (archive-listed): 10 samples from 2 repositories, 8 ran (6 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 8 of its repositories that Syntology harvested for other papers:

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

thuml/iTransformer officialmentioned in papermentioned on GitHubpytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to A Time Series is Worth 64 Words: Long-term Forecasting with Transformers (arXiv:2211.14730; that paper's own run record: 17 ran (of which 2 constructed an object rather than computing a result; 16 with no instrument failure: 0 honoured, 0 violated, 16 with no contract checked; 1 where Syntology's instrument failed) · 13 unverified); nothing checks that they implement this paper's method. report
Hannibal046/GridTST mentioned on GitHubpytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Are Transformers Effective for Time Series Forecasting? (arXiv:2205.13504; that paper's own run record: 13 ran (of which 4 constructed an object rather than computing a result; 13 with no instrument failure: 0 honoured, 0 violated, 13 with no contract checked; 0 where Syntology's instrument failed) · 6 unverified); nothing checks that they implement this paper's method. report
hughxx/tsf-new-paper-taste mentioned on GitHubpytorchSyntology: not harvested report
kwuking/TimeMixer mentioned on GitHubpytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Time-LLM: Time Series Forecasting by Reprogramming Large Language Models (arXiv:2310.01728; that paper's own run record: 7 ran (of which 7 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) · 2 unverified; every one of the 7 samples that ran constructed an object rather than computing a result); nothing checks that they implement this paper's method. report
lss-1138/SegRNN mentioned on GitHubpytorchApache-2.0Syntology: 3 samples, 2 ran (1 instrument-failed) · 1 unverified report
lucidrains/iTransformer mentioned on GitHubpytorchMITSyntology: 7 samples, 6 ran (1 instrument-failed) · 1 unverified report
master-plc/fredf mentioned on GitHubpytorchMITSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Are Transformers Effective for Time Series Forecasting? (arXiv:2205.13504; that paper's own run record: 13 ran (of which 4 constructed an object rather than computing a result; 13 with no instrument failure: 0 honoured, 0 violated, 13 with no contract checked; 0 where Syntology's instrument failed) · 6 unverified) and FreDF: Learning to Forecast in the Frequency Domain (arXiv:2402.02399; that paper's own run record: 7 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; 6 where Syntology's instrument failed) · 1 unverified); nothing checks that they implement this paper's method. report
sanjaylopa22/QCAAPatchTF mentioned on GitHubpytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to ETSformer: Exponential Smoothing Transformers for Time-series Forecasting (arXiv:2202.01381; that paper's own run record: 3 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 1 honoured, 1 violated, 0 with no contract checked; 1 where Syntology's instrument failed) · 2 unverified); nothing checks that they implement this paper's method. report
taohan10200/weather-5k mentioned on GitHubpytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Are Transformers Effective for Time Series Forecasting? (arXiv:2205.13504; that paper's own run record: 13 ran (of which 4 constructed an object rather than computing a result; 13 with no instrument failure: 0 honoured, 0 violated, 13 with no contract checked; 0 where Syntology's instrument failed) · 6 unverified) and How far are today's time-series models from real-world weather forecasting applications? (arXiv:2406.14399; that paper's own run record: 16 ran (of which 15 constructed an object rather than computing a result; 16 with no instrument failure: 0 honoured, 0 violated, 16 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified); nothing checks that they implement this paper's method. report
thuml/Time-Series-Library mentioned on GitHubpytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to UniTS: A Unified Multi-Task Time Series Model (arXiv:2403.00131; that paper's own run record: 19 ran (of which 9 constructed an object rather than computing a result; 19 with no instrument failure: 0 honoured, 0 violated, 19 with no contract checked; 0 where Syntology's instrument failed) · 9 unverified), XLinear: A Lightweight and Accurate MLP-Based Model for Long-Term Time Series... (arXiv:2601.09237; that paper's own run record: 7 ran (of which 7 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) · 2 unverified; every one of the 7 samples that ran constructed an object rather than computing a result) and To See Far, Look Close: Evolutionary Forecasting for Long-term Time Series (arXiv:2601.23114; that paper's own run record: 3 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; 0 where Syntology's instrument failed) · 3 unverified; every one of the 3 samples that ran constructed an object rather than computing a result); nothing checks that they implement this paper's method. report
WenjieDu/PyPOTS pytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Attention Is All You Need (arXiv:1706.03762; that paper's own run record: 610 ran (of which 293 constructed an object rather than computing a result; 529 with no instrument failure: 45 honoured, 15 violated, 469 with no contract checked; 81 where Syntology's instrument failed) · 336 unverified), Informer: Beyond Efficient Transformer for Long Sequence Time-Series Forecasting (arXiv:2012.07436; that paper's own run record: 62 ran (of which 53 constructed an object rather than computing a result; 62 with no instrument failure: 0 honoured, 1 violated, 61 with no contract checked; 0 where Syntology's instrument failed) · 14 unverified), Multi-Time Attention Networks for Irregularly Sampled Time Series (arXiv:2101.10318; 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, 0 violated, 2 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified) and 5 more (every one in this page's JSON twin); 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

10 samples harvested: 8 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 2 honoured, 4 violated, 0 with no contract checked; 2 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 last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

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

Licence: 4 of the 10 samples are pointer only, meaning Syntology does not serve that copy's text. For 4 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.

lss-1138/SegRNN community (archive-listed) 3 samples, 2 ran (1 instrument-failed) · 1 unverified
PositionalEncoding in 126 papers
census: 13 implementations from 9 papers, 9 distinct outputs across 5 buckets, one shared input per bucket
layers/PatchTST_layers.py ran · honoured contract Apache-2.0 (permissive) · 16b9b78d429636b7 · report fixture: signature q_len:int/0/int, d_model:int/0/int, normalize:bool/0/bool · returned Tensor · level recorded 2026-09-22
get_activation_fn in 67 papers layers/PatchTST_layers.py ran · our draft was wrong Apache-2.0 (permissive) here; the stored copy is pointer only · 72b9272542f279c6 · report fixture: signature activation:str/0/str · returned ReLU · level recorded 2026-09-24
Coord2dPosEncoding in 17 papers layers/PatchTST_layers.py unverified Apache-2.0 (permissive) here; the stored copy is pointer only · c3fc6992d1e467f3 · report
lucidrains/iTransformer community (archive-listed) 7 samples, 6 ran (1 instrument-failed) · 1 unverified
identity in 174 papers
census: 11 implementations from 39 papers, 3 distinct outputs across 2 buckets, one shared input per bucket this sample: bucket 1 of 2, arg 1: rank 2, kind float, dtype float32
iTransformer/iTransformer.py ran · honoured contract MIT (permissive) · 7f1040f5e3991d5e · report fixture: signature t:Tensor/2/float, args:tuple/1/Tensor, kwargs:dict/0/? · returned Tensor · level recorded, date not recorded
default in 430 papers iTransformer/attend.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
default in 430 papers iTransformer/iTransformer.py ran · violated contract fingerprinted MIT (permissive) · 99b3563ebc6734ad · report fixture: signature v: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
iTransformer/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
exists in 528 papers
census: 5 implementations from 103 papers, 1 distinct output on one shared input
iTransformer/iTransformer.py ran · violated contract fingerprinted MIT (permissive) · b7c3487f192e31b7 · report fixture: signature v:int/0/int · returned bool · level recorded, date not recorded
once in 16 papers iTransformer/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 iTransformer/iTransformer2D.py unverified MIT (permissive) · 6182326691dd827b · report

Tasks

Time SeriesTime Series Forecasting

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Time Series Forecasting ETTh1 (336) Multivariate iTransformer MAE 0.458 #59 of 72 Archive leaderboard report
Time Series Forecasting ETTh1 (336) Multivariate iTransformer MSE 0.487 #59 of 72 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

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