Papers › Online Test-Time Adaptation of Spatial-Temporal Traffic Flow Forecasting

Online Test-Time Adaptation of Spatial-Temporal Traffic Flow Forecasting

8 Jan 2024arXiv:2401.04148archive 2025-07-28

Pengxin Guo, Pengrong Jin, Ziyue Li, Lei Bai, Yu Zhang

Accurate spatial-temporal traffic flow forecasting is crucial in aiding traffic managers in implementing control measures and assisting drivers in selecting optimal travel routes. Traditional deep-learning based methods for traffic flow forecasting typically rely on historical data to train their models, which are then used to make predictions on future data. However, the performance of the trained model usually degrades due to the temporal drift between the historical and future data. To make the model trained on historical data better adapt to future data in a fully online manner, this paper conducts the first study of the online test-time adaptation techniques for spatial-temporal traffic flow forecasting problems. To this end, we propose an Adaptive Double Correction by Series Decomposition (ADCSD) method, which first decomposes the output of the trained model into seasonal and trend-cyclical parts and then corrects them by two separate modules during the testing phase using the latest observed data entry by entry. In the proposed ADCSD method, instead of fine-tuning the whole trained model during the testing phase, a lite network is attached after the trained model, and only the lite network is fine-tuned in the testing process each time a data entry is observed. Moreover, to satisfy that different time series variables may have different levels of temporal drift, two adaptive vectors are adopted to provide different weights for different time series variables. Extensive experiments on four real-world traffic flow forecasting datasets demonstrate the effectiveness of the proposed ADCSD method. The code is available at https://github.com/Pengxin-Guo/ADCSD.

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

Syntology 9 code samples harvested from 1 repository linked to this paper: 8 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 3 where Syntology's instrument failed) · 1 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; 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, 8 ran (5 with no instrument failure; 3 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 on 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

pengxin-guo/adcsd officialmentioned in paperpytorchSyntology: 9 samples, 8 ran (3 instrument-failed) · 1 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: 8 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 3 where Syntology's instrument failed) · 1 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 · our draft was wrong
1ran; the contract check could not run
5ran
1unverified

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 pengxin-guo/adcsd. “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.

pengxin-guo/adcsd official repository 9 samples, 8 ran (3 instrument-failed) · 1 unverified
log_cosh_loss libcity/model/loss.py ran · our draft was wrong fingerprinted no licence file found · pointer only · 8b1fe12a843654ca · report fixture: signature preds:Tensor/2/float, labels:Tensor/2/float · returned Tensor · level recorded 2026-09-24
mae in 41 papers
census: 4 implementations from 6 papers, 3 distinct outputs across 3 buckets, one shared input per bucket
libcity/evaluator/eval_funcs.py ran fingerprinted no licence file found · pointer only · adfbb8bc32262202 · report fixture: signature loc_pred:ndarray/2/float, loc_true:ndarray/2/float · returned float64 · level recorded 2026-09-24
masked_mae_loss in 7 papers libcity/model/loss.py ran · our draft was wrong fingerprinted no licence file found · pointer only · 2a82a90d91ced4b6 · report fixture: signature y_pred:Tensor/2/float, y_true:Tensor/2/float · returned Tensor · level recorded 2026-09-24
masked_mae_torch libcity/model/loss.py ran no licence file found · pointer only · addcdb338a54bba0 · report fixture: signature preds:Tensor/2/float, labels:Tensor/2/float, null_val:float/0/float, mask_val:float/0/float · returned Tensor · level recorded 2026-09-24
mse in 78 papers
census: 5 implementations from 6 papers, 4 distinct outputs across 3 buckets, one shared input per bucket
libcity/evaluator/eval_funcs.py ran fingerprinted no licence file found · pointer only · a57096075ed5bfb9 · report fixture: signature loc_pred:ndarray/2/float, loc_true:ndarray/2/float · returned float64 · level recorded 2026-09-24
rmse in 44 papers libcity/evaluator/eval_funcs.py ran fingerprinted no licence file found · pointer only · d43c793b0819b516 · report fixture: signature loc_pred:ndarray/2/float, loc_true:ndarray/2/float · returned float64 · level recorded 2026-09-24
sort_confidence_ids libcity/evaluator/utils.py ran; the contract check could not run (RAISES) fingerprinted no licence file found · pointer only · 1fca944cc6ee41b8 · report fixture: signature confidence_list:list/1/float, threshold:int/0/int · returned list · level recorded 2026-09-24
transfer_data libcity/evaluator/utils.py ran no licence file found · pointer only · 57277243f9a05725 · report fixture: signature data:dict/0/?, model:str/0/str, maxk:int/0/int · returned dict · level recorded 2026-09-24
evaluate_model in 54 papers libcity/evaluator/utils.py unverified no licence file found · pointer only · 9b199ea651c27032 · report

Tasks

Test-time AdaptationTraffic Prediction

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Traffic Prediction NYCTaxi ADCSD MAE @ in 16.987 #5 of 5 Archive leaderboard report
Traffic Prediction NYCTaxi ADCSD MAE @ out 14.595 #5 of 5 Archive leaderboard report
Traffic Prediction PeMS07 ADCSD MAE@1h 19.62 #8 of 17 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