Papers › A Background-Agnostic Framework with Adversarial Training for Abnormal Event Detection in Video

A Background-Agnostic Framework with Adversarial Training for Abnormal Event Detection in Video

27 Aug 2020arXiv:2008.12328archive 2025-07-28

Mariana-Iuliana Georgescu, Radu Tudor Ionescu, Fahad Shahbaz Khan, Marius Popescu, Mubarak Shah

Abnormal event detection in video is a complex computer vision problem that has attracted significant attention in recent years. The complexity of the task arises from the commonly-adopted definition of an abnormal event, that is, a rarely occurring event that typically depends on the surrounding context. Following the standard formulation of abnormal event detection as outlier detection, we propose a background-agnostic framework that learns from training videos containing only normal events. Our framework is composed of an object detector, a set of appearance and motion auto-encoders, and a set of classifiers. Since our framework only looks at object detections, it can be applied to different scenes, provided that normal events are defined identically across scenes and that the single main factor of variation is the background. To overcome the lack of abnormal data during training, we propose an adversarial learning strategy for the auto-encoders. We create a scene-agnostic set of out-of-domain pseudo-abnormal examples, which are correctly reconstructed by the auto-encoders before applying gradient ascent on the pseudo-abnormal examples. We further utilize the pseudo-abnormal examples to serve as abnormal examples when training appearance-based and motion-based binary classifiers to discriminate between normal and abnormal latent features and reconstructions. We compare our framework with the state-of-the-art methods on four benchmark data sets, using various evaluation metrics. Compared to existing methods, the empirical results indicate that our approach achieves favorable performance on all data sets. In addition, we provide region-based and track-based annotations for two large-scale abnormal event detection data sets from the literature, namely ShanghaiTech and Subway.

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 3 code samples: 2 from 1 repository linked to this paper, 1 identical to code harvested from another paper's repository. Across all 3: 3 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 1 honoured, 0 violated, 0 with no contract checked; 2 where Syntology's instrument failed) · 0 unverified. Where Syntology's instrument failed: 1 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: 2 samples from 1 repository, 2 ran (1 with no instrument failure; 1 where Syntology's instrument failed); 1 identical to code first harvested elsewhere. 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-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

lilygeorgescu/AED officialmentioned in papermentioned on GitHubSyntology: 2 samples, 2 ran (1 instrument-failed) · 0 unverified report
m-3lab/awesome-visual-sensory-anomaly-detection mentioned on GitHubSyntology: not harvested 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: 3 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 1 honoured, 0 violated, 0 with no contract checked; 2 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 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 · honoured contract
1ran · our draft was wrong
1ran; the contract check could not run

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 lilygeorgescu/AED. 1 sample is listed last, in a group without a repository. “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.

lilygeorgescu/AED official repository 2 samples, 2 ran (1 instrument-failed) · 0 unverified
compute_tbdr evaluation/compute_tbdc_rbdc.py ran · our draft was wrong licence not identified · pointer only · 32f9a43a8db49a6e · report fixture: signature gt_tracks:list/1/Track, num_matched_detections_per_track:list/1/int, alpha:float/0/float · returned float64 · level recorded 2026-09-22
get_matching_gt_indices evaluation/compute_tbdc_rbdc.py ran · honoured contract licence not identified · pointer only · 331b15f4d9630ab7 · report fixture: signature pred_anomaly:Anomaly/0/?, gt_anomalies_per_frame:list/1/Anomaly, beta:float/0/float · returned list · level recorded 2026-09-22
Repository not located 1 sample, 1 ran (1 instrument-failed) · 0 unverified
1 sample is identical to code Syntology harvested from another paper's repository; this paper's own copy was not located, so no repository is named and no licence is recorded.
bb_intersection_over_union in 12 papers repository not located ran; the contract check could not run (RAISES) · metamorphic tier: well formed fingerprinted licence of this copy not recorded · a2c564ef3e28ab1d · report fixture: signature boxA:list/1/int, boxB:list/1/int · returned float · level recorded 2026-09-22

Tasks

Abnormal Event Detection In VideoAnomaly DetectionAnomaly Detection In Surveillance VideosEvent DetectionOutlier Detection

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Abnormal Event Detection In Video UCSD Ped2 Background-Agnostic Framework AUC 98.7% #2 of 4 Archive leaderboard report
Anomaly Detection CUHK Avenue Background-Agnostic Framework AUC 92.3% #11 of 35 Archive leaderboard report
Anomaly Detection CUHK Avenue Background-Agnostic Framework FPS 25 #11 of 35 Archive leaderboard report
Anomaly Detection CUHK Avenue Background-Agnostic Framework RBDC 65.05 #11 of 35 Archive leaderboard report
Anomaly Detection CUHK Avenue Background-Agnostic Framework TBDC 66.85 #11 of 35 Archive leaderboard report
Anomaly Detection ShanghaiTech Background-Agnostic Framework AUC 82.7% #15 of 31 Archive leaderboard report
Anomaly Detection UBnormal Background-Agnostic Framework AUC 61.3% #12 of 14 Archive leaderboard report
Anomaly Detection UBnormal Background-Agnostic Framework RBDC 25.43 #12 of 14 Archive leaderboard report
Anomaly Detection UBnormal Background-Agnostic Framework TBDC 56.27 #12 of 14 Archive leaderboard report
Anomaly Detection UCSD Ped2 Background-Agnostic AUC 98.7% #4 of 14 Archive leaderboard report
Anomaly Detection UCSD Ped2 Background-Agnostic FPS 24 #4 of 14 Archive leaderboard report
Anomaly Detection UCSD Peds2 Background-Agnostic Framework AUC 98.7 #1 of 3 Archive leaderboard report
Anomaly Detection In Surveillance Videos UCSD Peds2 Background-Agnostic Framework AUC 98.7 #1 of 6 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