Papers › Multivariate Time-series Anomaly Detection via Graph Attention Network

Multivariate Time-series Anomaly Detection via Graph Attention Network

4 Sep 2020arXiv:2009.02040archive 2025-07-28

Hang Zhao, Yujing Wang, Juanyong Duan, Congrui Huang, Defu Cao, Yunhai Tong, Bixiong Xu, Jing Bai, Jie Tong, Qi Zhang

Anomaly detection on multivariate time-series is of great importance in both data mining research and industrial applications. Recent approaches have achieved significant progress in this topic, but there is remaining limitations. One major limitation is that they do not capture the relationships between different time-series explicitly, resulting in inevitable false alarms. In this paper, we propose a novel self-supervised framework for multivariate time-series anomaly detection to address this issue. Our framework considers each univariate time-series as an individual feature and includes two graph attention layers in parallel to learn the complex dependencies of multivariate time-series in both temporal and feature dimensions. In addition, our approach jointly optimizes a forecasting-based model and are construction-based model, obtaining better time-series representations through a combination of single-timestamp prediction and reconstruction of the entire time-series. We demonstrate the efficacy of our model through extensive experiments. The proposed method outperforms other state-of-the-art models on three real-world datasets. Further analysis shows that our method has good interpretability and is useful for anomaly diagnosis.

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

By repository: community (archive-listed): 8 samples from 2 repositories, 8 ran (7 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. 1 of the 8 samples that ran has no recorded date.

ML4ITS/mtad-gat-pytorch mentioned on GitHubpytorchMITSyntology: 7 samples, 7 ran (1 instrument-failed) · 0 unverified report
mangushev/mtad-gat mentioned on GitHubtfSyntology: 1 sample, 1 ran (0 instrument-failed) · 0 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

8 samples harvested: 8 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 2 violated, 5 with no contract checked; 1 where Syntology's instrument failed) · 0 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 · violated contract
1ran · our draft was wrong
5ran

Licence: 0 of the 8 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 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.

ML4ITS/mtad-gat-pytorch community (archive-listed) 7 samples, 7 ran (1 instrument-failed) · 0 unverified
adjust_predicts eval_methods.py ran MIT (permissive) · 6e0ef50ddcbd9946 · report fixture: signature score:ndarray/1/float, label:ndarray/1/float, threshold:float/0/float, pred:NoneType/0/?, calc_latency:bool/0/bool · returned ndarray · level recorded 2026-09-24
backMean spot.py ran · our draft was wrong fingerprinted MIT (permissive) · e4c7d8229585523b · report fixture: signature X:ndarray/1/float, d:int/0/int · returned ndarray · level recorded 2026-09-24
calc_point2point eval_methods.py ran fingerprinted MIT (permissive) · 5730860df6f005e7 · report fixture: signature predict:ndarray/1/int, actual:ndarray/1/int · returned tuple · level recorded 2026-09-24
get_data_dim in 6 papers utils.py ran MIT (permissive) · 8ba79dc49855a077 · report fixture: signature dataset:str/0/str · returned int · level recorded 2026-09-24
get_target_dims utils.py ran MIT (permissive) · b2029bff46e49e3a · report fixture: signature dataset:str/0/str · returned list · level recorded 2026-09-24
normalize_data in 32 papers
census: 7 implementations from 7 papers, 7 distinct outputs across 3 buckets, one shared input per bucket
utils.py ran MIT (permissive) · 9725dabb7ae0f789 · report fixture: signature data:ndarray/2/float, scaler:NoneType/0/? · returned tuple · level recorded 2026-09-24
str2bool in 533 papers args.py ran · violated contract MIT (permissive) · 7c508037b40522af · report fixture: signature v:str/0/str · returned bool · level recorded, date not recorded
mangushev/mtad-gat community (archive-listed) 1 sample, 1 ran (0 instrument-failed) · 0 unverified
scale01 training.py ran · violated contract fingerprinted MIT (permissive) · 681a2fdae1dd8b51 · report fixture: signature data:ndarray/1/float · returned ndarray · level recorded 2026-09-22

Tasks

Anomaly DetectionGraph AttentionSpatio-Temporal ForecastingTime SeriesTime Series AnalysisTime Series Anomaly DetectionUnsupervised Anomaly Detection

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Unsupervised Anomaly Detection SMAP MTAD-GAT AUC 98.44 #4 of 9 Archive leaderboard report
Unsupervised Anomaly Detection SMAP MTAD-GAT F1 88.80 #4 of 9 Archive leaderboard report
Unsupervised Anomaly Detection SMAP MTAD-GAT Precision 79.91 #4 of 9 Archive leaderboard report
Unsupervised Anomaly Detection SMAP MTAD-GAT Recall 99.91 #4 of 9 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

GATGraph Self-AttentionInterpretability

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