Papers › IMTS is Worth Time × Channel Patches: Visual Masked Autoencoders for Irregular...

IMTS is Worth Time × Channel Patches: Visual Masked Autoencoders for Irregular Multivariate Time Series Prediction

28 May 2025arXiv:2505.22815archive 2025-07-28

Zhangyi Hu, Jiemin Wu, Hua Xu, Mingqian Liao, Ninghui Feng, Bo Gao, Songning Lai, Yutao Yue

Irregular Multivariate Time Series (IMTS) forecasting is challenging due to the unaligned nature of multi-channel signals and the prevalence of extensive missing data. Existing methods struggle to capture reliable temporal patterns from such data due to significant missing values. While pre-trained foundation models show potential for addressing these challenges, they are typically designed for Regularly Sampled Time Series (RTS). Motivated by the visual Mask AutoEncoder's (MAE) powerful capability for modeling sparse multi-channel information and its success in RTS forecasting, we propose VIMTS, a framework adapting Visual MAE for IMTS forecasting. To mitigate the effect of missing values, VIMTS first processes IMTS along the timeline into feature patches at equal intervals. These patches are then complemented using learned cross-channel dependencies. Then it leverages visual MAE's capability in handling sparse multichannel data for patch reconstruction, followed by a coarse-to-fine technique to generate precise predictions from focused contexts. In addition, we integrate self-supervised learning for improved IMTS modeling by adapting the visual MAE to IMTS data. Extensive experiments demonstrate VIMTS's superior performance and few-shot capability, advancing the application of visual foundation models in more general time series tasks. Our code is available at https://github.com/WHU-HZY/VIMTS.

PaperPDFCodeCode Syntology ranMethod as code

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 9 code samples harvested from 1 repository linked to this paper: 5 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; 1 where Syntology's instrument failed) · 4 unverified. Where Syntology's instrument failed: 1 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 9 samples from 1 repository, 5 ran (4 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.

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.

whu-hzy/vimts officialmentioned in papermentioned on GitHubpytorchSyntology: 9 samples, 5 ran (1 instrument-failed) · 4 unverified 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.

Code Syntology ran Syntology

9 samples harvested: 5 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; 1 where Syntology's instrument failed) · 4 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; the contract check could not run
4ran
4unverified

Licence: 9 of the 9 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 whu-hzy/vimts. “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.

whu-hzy/vimts official repository 9 samples, 5 ran (1 instrument-failed) · 4 unverified
IMTS_PatchEmbed IMTS/lib/models/visionts/models_mae.py ran no licence file found · pointer only · 4943729c88110c21 · report fixture: signature x:Tensor/3/float · returned Tensor · level recorded 2026-09-24
Linear in 127 papers IMTS/lib/models/visionts/models_mae.py ran · metamorphic tier: invariant no licence file found · pointer only · 134faf93427daea3 · report fixture: signature x:Tensor/2/float · returned Tensor · level recorded 2026-09-22
Mlp in 102 papers IMTS/lib/models/visionts/models_mae.py ran no licence file found · pointer only · 7e045c902914c785 · report fixture: signature x:Tensor/2/float · returned Tensor · level recorded 2026-09-24
get_2d_sincos_pos_embed_for_seq IMTS/lib/models/visionts/models_mae.py ran; the contract check could not run (RAISES) no licence file found · pointer only · be2cd94cfe0ee2f0 · report fixture: signature embed_dim:int/0/int, grid_size:list/1/int, cls_token:bool/0/bool · returned ndarray · level recorded 2026-09-22
nconv in 5 papers IMTS/lib/models/visionts/models_mae.py ran · metamorphic tier: invariant no licence file found · pointer only · d47294d8704c58f9 · report fixture: signature x:Tensor/4/float, A:Tensor/4/float · returned Tensor · level recorded 2026-09-22
MaskedAutoencoderViT in 14 papers IMTS/lib/models/visionts/models_mae.py unverified no licence file found · pointer only · 0c4169c946e2736d · report
gcn in 7 papers IMTS/lib/models/visionts/models_mae.py unverified no licence file found · pointer only · 319f1727947e81b0 · report

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it.

1 assembly on this paper: 1 harvested, 0 generated.

harvested Assembly for VIMTS (graph method: VIMTS). 14 bricks; individually on a fixture: 9 ran (of which 3 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 0 violated, 7 with no contract checked; 2 where Syntology's instrument failed) · 5 unverified. The assembly has not been run end-to-end.

  1. MaskedAutoencoderViT entry · level 0 · unverified · 0c4169c946e2736d
  2. Block helper · level 0 · unverified · f4ee7167fad69080
  3. IMTS_PatchEmbed helper · level 1 · ran · 4943729c88110c21
  4. gcn helper · level 0 · unverified · 319f1727947e81b0
  5. get_2d_sincos_pos_embed_for_seq helper · level 1 · ran; the contract check could not run (RAISES) · be2cd94cfe0ee2f0
  6. Attention helper · level 0 · unverified · 2698a4c6a1a414f9
  7. LayerScale helper · level 1 · ran · 701e39ed251d5829
  8. Mlp helper · level 1 · ran · 7e045c902914c785
  9. linear helper · level 1 · ran · f1cab21ec84db199
  10. nconv helper · level 1 · ran · d47294d8704c58f9
  11. get_2d_sincos_pos_embed_from_grid helper · level 0 · unverified · 2884deadbb637c3e
  12. Linear helper · level 1 · ran · 134faf93427daea3
  13. get_1d_sincos_pos_embed_from_grid helper · level 1 · ran; the contract check could not run · 5c8ea92d43ead77d
  14. LoRALayer helper · level 1 · ran · 562c6b943203b573

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2505.22815") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

Missing ValuesSelf-Supervised LearningTime SeriesTime Series Prediction

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

MAE

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