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 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="2008.12328")

Code

Syntology Ran 3 of 3 code samples harvested from 1 repository linked to this paper; 0 have no recorded run. Of those that ran: 1 ran · honoured contract; 1 ran · our draft was wrong; 1 ran · fixture could not drive it.

By repository: official repository: 2 samples from 1 repository, 2 ran; 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.

lilygeorgescu/AED officialmentioned in papermentioned on GitHub 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; 1 honoured the contract we drafted; 0 have no recorded run. Read from Syntology's graph 2026-09-24; that is when this build read the record, not when the samples ran.

1ran · honoured contract
1ran · our draft was wrong
1ran · fixture could not drive it

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. Some samples are identical code Syntology first harvested from another repository; for those, this paper's copy is not located and its licence is not recorded. “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.

compute_tbdr lilygeorgescu/AED/evaluation/compute_tbdc_rbdc.py official repository ran · our draft was wrong licence not identified · pointer only · 32f9a43a8db49a6e · report
get_matching_gt_indices lilygeorgescu/AED/evaluation/compute_tbdc_rbdc.py official repository ran · honoured contract licence not identified · pointer only · 331b15f4d9630ab7 · report
bb_intersection_over_union identical code first harvested elsewhere ran · fixture could not drive it fingerprinted licence of this copy not recorded · a2c564ef3e28ab1d · report

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