Papers › GMAN: A Graph Multi-Attention Network for Traffic Prediction

GMAN: A Graph Multi-Attention Network for Traffic Prediction

11 Nov 2019arXiv:1911.08415archive 2025-07-28

Chuanpan Zheng, Xiaoliang Fan, Cheng Wang, Jianzhong Qi

Long-term traffic prediction is highly challenging due to the complexity of traffic systems and the constantly changing nature of many impacting factors. In this paper, we focus on the spatio-temporal factors, and propose a graph multi-attention network (GMAN) to predict traffic conditions for time steps ahead at different locations on a road network graph. GMAN adapts an encoder-decoder architecture, where both the encoder and the decoder consist of multiple spatio-temporal attention blocks to model the impact of the spatio-temporal factors on traffic conditions. The encoder encodes the input traffic features and the decoder predicts the output sequence. Between the encoder and the decoder, a transform attention layer is applied to convert the encoded traffic features to generate the sequence representations of future time steps as the input of the decoder. The transform attention mechanism models the direct relationships between historical and future time steps that helps to alleviate the error propagation problem among prediction time steps. Experimental results on two real-world traffic prediction tasks (i.e., traffic volume prediction and traffic speed prediction) demonstrate the superiority of GMAN. In particular, in the 1 hour ahead prediction, GMAN outperforms state-of-the-art methods by up to 4% improvement in MAE measure. The source code is available at https://github.com/zhengchuanpan/GMAN.

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 10 code samples harvested from 1 repository linked to this paper: 4 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; 0 where Syntology's instrument failed) · 6 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 10 samples from 1 repository, 4 ran (4 with no instrument failure; 0 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 2 of its repositories that Syntology harvested for other papers:

Levels written on 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

zhengchuanpan/GMAN officialmentioned in papermentioned on GitHubpytorchApache-2.0Syntology: 10 samples, 4 ran (0 instrument-failed) · 6 unverified report
SmallNana/GMAN_pytorch mentioned on GitHubpytorchSyntology: not harvested report
VincLee8188/GMAN-PyTorch mentioned on GitHubpytorchSyntology: not harvested report
VincLee8188/Gman_Ptorch_version mentioned on GitHubpytorchSyntology: not harvested report
benedekrozemberczki/pytorch_geometric_temporal mentioned on GitHubpytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Diffusion Convolutional Recurrent Neural Network: Data-Driven Traffic Forecasting (arXiv:1707.01926; that paper's own run record: 17 ran (of which 7 constructed an object rather than computing a result; 9 with no instrument failure: 1 honoured, 0 violated, 8 with no contract checked; 8 where Syntology's instrument failed) · 18 unverified), Predicting Path Failure In Time-Evolving Graphs (arXiv:1905.03994; that paper's own run record: 3 ran (of which 1 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 2 where Syntology's instrument failed) · 1 unverified) and Adaptive Graph Convolutional Recurrent Network for Traffic Forecasting (arXiv:2007.02842; that paper's own run record: 5 ran (of which 5 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 0 where Syntology's instrument failed) · 2 unverified; every one of the 5 samples that ran constructed an object rather than computing a result); nothing checks that they implement this paper's method. report
tijsmaas/TrafficPrediction mentioned on GitHubtfSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Diffusion Convolutional Recurrent Neural Network: Data-Driven Traffic Forecasting (arXiv:1707.01926; that paper's own run record: 17 ran (of which 7 constructed an object rather than computing a result; 9 with no instrument failure: 1 honoured, 0 violated, 8 with no contract checked; 8 where Syntology's instrument failed) · 18 unverified); 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: 4 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; 0 where Syntology's instrument failed) · 6 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.

4ran
6unverified

Licence: 0 of the 10 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 zhengchuanpan/GMAN. “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.

zhengchuanpan/GMAN official repository 10 samples, 4 ran (0 instrument-failed) · 6 unverified
alias_draw in 6 papers METR/node2vec/node2vec.py ran Apache-2.0 (permissive) · c71ec4f39a2bea7a · report fixture: signature J:list/1/int, q:ndarray/1/float · returned int · level recorded 2026-09-25
dropout in 34 papers METR/tf_utils.py ran Apache-2.0 (permissive) · e4716e5fdd0a9483 · report fixture: signature x:EagerTensor/2/float, drop:float/0/float, is_training:EagerTensor/0/bool · returned EagerTensor · level recorded 2026-09-25
metric in 14 papers METR/utils.py ran Apache-2.0 (permissive) · 1ba47a23adf07065 · report fixture: signature pred:ndarray/1/float, label:ndarray/1/float · returned tuple · level recorded 2026-09-25
seq2instance METR/utils.py ran fingerprinted Apache-2.0 (permissive) · 3fc58cdee460bc5d · report fixture: signature data:ndarray/2/float, P:int/0/int, Q:int/0/int · returned tuple · level recorded 2026-09-25
alias_setup in 6 papers METR/node2vec/node2vec.py unverified Apache-2.0 (permissive) · 0ddb0dd1cf3b67dd · report
batch_norm in 46 papers METR/tf_utils.py unverified Apache-2.0 (permissive) · 8e2329b6f957b2ce · report
conv2d in 119 papers METR/tf_utils.py unverified Apache-2.0 (permissive) · 6122f2f19a4027d8 · report
loadData in 8 papers METR/utils.py unverified Apache-2.0 (permissive) · 78c234f574a9d6a2 · report
placeholder in 7 papers METR/model.py unverified Apache-2.0 (permissive) · 87a81a456578efcc · report
placeholder in 7 papers PeMS/model.py unverified Apache-2.0 (permissive) · c11afb5b81b2e8bd · report

Tasks

DecoderImage DehazingPredictionTraffic Prediction

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Image Dehazing KITTI GMAN PSNR 24.64 #2 of 3 Archive leaderboard report
Traffic Prediction NE-BJ GMAN 12 steps MAE 4.80 #3 of 6 Archive leaderboard report
Traffic Prediction PEMS-BAY GMAN MAE @ 12 step 1.92 #12 of 16 Archive leaderboard report
Traffic Prediction PEMS-BAY GMAN RMSE 4.49 #12 of 16 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

Multi-Attention NetworkSPEED

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