Papers › Spatial-Temporal-Decoupled Masked Pre-training for Spatiotemporal Forecasting

Spatial-Temporal-Decoupled Masked Pre-training for Spatiotemporal Forecasting

1 Dec 2023arXiv:2312.00516archive 2025-07-28

Haotian Gao, Renhe Jiang, Zheng Dong, Jinliang Deng, Yuxin Ma, Xuan Song

Spatiotemporal forecasting techniques are significant for various domains such as transportation, energy, and weather. Accurate prediction of spatiotemporal series remains challenging due to the complex spatiotemporal heterogeneity. In particular, current end-to-end models are limited by input length and thus often fall into spatiotemporal mirage, i.e., similar input time series followed by dissimilar future values and vice versa. To address these problems, we propose a novel self-supervised pre-training framework Spatial-Temporal-Decoupled Masked Pre-training (STD-MAE) that employs two decoupled masked autoencoders to reconstruct spatiotemporal series along the spatial and temporal dimensions. Rich-context representations learned through such reconstruction could be seamlessly integrated by downstream predictors with arbitrary architectures to augment their performances. A series of quantitative and qualitative evaluations on six widely used benchmarks (PEMS03, PEMS04, PEMS07, PEMS08, METR-LA, and PEMS-BAY) are conducted to validate the state-of-the-art performance of STD-MAE. Codes are available at https://github.com/Jimmy-7664/STD-MAE.

PaperPDFCodeCode Syntology ran

In Syntology Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, Syntology's MCP tool lists every function and class Syntology harvested from this paper and whether it ran (how to connect): get_harvested_code_for_paper(arxiv_id="2312.00516")

Code

Syntology Ran 2 of 3 code samples harvested from 1 repository linked to this paper; 1 has no recorded run. Of those that ran: 2 ran with no contract checked.

By repository: official repository: 3 samples from 1 repository, 2 ran. The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

jimmy-7664/std-mae officialmentioned in papermentioned on GitHubpytorch 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

3 samples harvested; 2 ran; 0 honoured the contract we drafted; 1 has no recorded run. Read from Syntology's graph 2026-09-24; that is when this build read the record, not when the samples ran.

2ran
1unverified

Licence: 3 of the 3 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 jimmy-7664/std-mae. “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. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “fixture could not drive it” are failures of Syntology's instrument, not of the code.

Each sample ends with its code_sha256, Syntology's identity for that exact code. An agent fetches the stored sample with Syntology's MCP tool get_code(code_sha256="…") (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 from a repository marked official are listed first. 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 four 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; or the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar). 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.

l1_loss jimmy-7664/std-mae/basicts/losses/losses.py official repository ran fingerprinted no licence file found · pointer only · 48469f10c13c505c · report
masked_mae jimmy-7664/std-mae/basicts/metrics/mae.py official repository ran fingerprinted no licence file found · pointer only · 3492570f7c53230f · report
l2_loss jimmy-7664/std-mae/basicts/losses/losses.py official repository unverified no licence file found · pointer only · e97291c1cbf62cfd · report

Tasks

Time SeriesTraffic Prediction

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Traffic Prediction EXPY-TKY STD-MAE 1 step MAE 5.73 #1 of 8 Archive leaderboard report
Traffic Prediction EXPY-TKY STD-MAE 3 step MAE 6.41 #1 of 8 Archive leaderboard report
Traffic Prediction EXPY-TKY STD-MAE 6 step MAE 6.75 #1 of 8 Archive leaderboard report
Traffic Prediction METR-LA STD-MAE 12 steps MAE 3.40 #10 of 20 Archive leaderboard report
Traffic Prediction METR-LA STD-MAE 12 steps MAPE 9.59 #10 of 20 Archive leaderboard report
Traffic Prediction METR-LA STD-MAE 12 steps RMSE 7.07 #10 of 20 Archive leaderboard report
Traffic Prediction METR-LA STD-MAE MAE @ 12 step 3.40 #10 of 20 Archive leaderboard report
Traffic Prediction METR-LA STD-MAE MAE @ 3 step 2.62 #10 of 20 Archive leaderboard report
Traffic Prediction PEMS-BAY STD-MAE MAE @ 12 step 1.77 #3 of 16 Archive leaderboard report
Traffic Prediction PEMS-BAY STD-MAE RMSE 4.20 #3 of 16 Archive leaderboard report
Traffic Prediction PeMS04 STD-MAE 12 Steps MAE 17.80 #1 of 12 Archive leaderboard report
Traffic Prediction PeMS07 STD-MAE MAE@1h 18.31 #1 of 17 Archive leaderboard report
Traffic Prediction PeMSD3 STD-MAE 12 steps MAE 13.80 #1 of 6 Archive leaderboard report
Traffic Prediction PeMSD3 STD-MAE 12 steps MAPE 13.96 #1 of 6 Archive leaderboard report
Traffic Prediction PeMSD3 STD-MAE 12 steps RMSE 24.43 #1 of 6 Archive leaderboard report
Traffic Prediction PeMSD4 STD-MAE 12 steps MAE 17.80 #2 of 13 Archive leaderboard report
Traffic Prediction PeMSD7 STD-MAE 12 steps MAE 18.31 #1 of 8 Archive leaderboard report
Traffic Prediction PeMSD7 STD-MAE 12 steps MAPE 7.72 #1 of 8 Archive leaderboard report
Traffic Prediction PeMSD7 STD-MAE 12 steps RMSE 31.07 #1 of 8 Archive leaderboard report
Traffic Prediction PeMSD7(L) STD-MAE 12 steps MAE 2.64 #1 of 6 Archive leaderboard report
Traffic Prediction PeMSD7(L) STD-MAE 12 steps MAPE 6.65 #1 of 6 Archive leaderboard report
Traffic Prediction PeMSD7(L) STD-MAE 12 steps RMSE 5.50 #1 of 6 Archive leaderboard report
Traffic Prediction PeMSD7(M) STD-MAE 12 steps MAE 2.52 #1 of 7 Archive leaderboard report
Traffic Prediction PeMSD7(M) STD-MAE 12 steps MAPE 6.35 #1 of 7 Archive leaderboard report
Traffic Prediction PeMSD7(M) STD-MAE 12 steps RMSE 5.20 #1 of 7 Archive leaderboard report
Traffic Prediction PeMSD8 STD-MAE 12 steps MAE 13.44 #5 of 13 Archive leaderboard report
Traffic Prediction PeMSD8 STD-MAE 12 steps MAPE 8.76 #5 of 13 Archive leaderboard report
Traffic Prediction PeMSD8 STD-MAE 12 steps RMSE 22.47 #5 of 13 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.

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