Papers › Variational Autoencoders for Anomalous Jet Tagging

Variational Autoencoders for Anomalous Jet Tagging

3 Jul 2020arXiv:2007.01850archive 2025-07-28

Taoli Cheng, Jean-François Arguin, Julien Leissner-Martin, Jacinthe Pilette, Tobias Golling

We present a detailed study on Variational Autoencoders (VAEs) for anomalous jet tagging at the Large Hadron Collider. By taking in low-level jet constituents' information, and training with background QCD jets in an unsupervised manner, the VAE is able to encode important information for reconstructing jets, while learning an expressive posterior distribution in the latent space. When using the VAE as an anomaly detector, we present different approaches to detect anomalies: directly comparing in the input space or, instead, working in the latent space. In order to facilitate general search approaches such as bump-hunt, mass-decorrelated VAEs based on distance correlation regularization are also studied. We find that the naive mass-decorrelated VAEs fail at maintaining proper detection performance, by assigning higher probabilities to some anomalous samples. To build a performant mass-decorrelated anomalous jet tagger, we propose the Outlier Exposed VAE (OE-VAE), for which some outlier samples are introduced in the training process to guide the learned information. OE-VAEs are employed to achieve two goals at the same time: increasing sensitivity of outlier detection and decorrelating jet mass from the anomaly score. We succeed in reaching excellent results from both aspects. Code implementation of this work can be found at https://github.com/taolicheng/VAE-Jet

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; 8 with no instrument failure: 0 honoured, 1 violated, 7 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 9 samples from 1 repository, 8 ran (8 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.

Levels written on 2026-09-25 (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.

taolicheng/VAE-Jet officialmentioned in papermentioned on GitHubtfMITSyntology: 9 samples, 8 ran (0 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; 8 with no instrument failure: 0 honoured, 1 violated, 7 with no contract checked; 0 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 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 · violated contract
7ran
1unverified

Licence: 1 of the 9 samples is pointer only, meaning Syntology does not serve that copy's text. For that sample, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from taolicheng/VAE-Jet. “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.

taolicheng/VAE-Jet official repository 9 samples, 8 ran (0 instrument-failed) · 1 unverified
annealing_fn tf2/train_disco.py ran fingerprinted MIT (permissive) · 9c9155005989a5a6 · report fixture: signature epoch:int/0/int, weight:float/0/float · returned float · level recorded 2026-09-25
annealing_fn tf2/train_oe_resample.py ran fingerprinted MIT (permissive) · d361c031d072ede4 · report fixture: signature epoch:int/0/int, weight:float/0/float · returned float · level recorded 2026-09-25
annealing_fn_2steps tf2/train_disco.py ran fingerprinted MIT (permissive) · ec98a116d9f61d78 · report fixture: signature epoch:int/0/int, weight:float/0/float · returned float · level recorded 2026-09-25
annealing_fn_v2 tf2/train_oe_resample.py ran fingerprinted MIT (permissive) · 6a6ad31f7157364e · report fixture: signature epoch:int/0/int, weight:float/0/float · returned float · level recorded 2026-09-25
distance_corr tf2/disco.py ran MIT (permissive) · 824ab9ee98133ee2 · report fixture: signature var_1:EagerTensor/1/float, var_2:EagerTensor/1/float, normedweight:EagerTensor/1/float, power:int/0/int · returned SymbolicTensor · level recorded 2026-09-25
jet_mass tf1/utils.py ran · violated contract fingerprinted MIT (permissive) here; the stored copy is pointer only · 55fa93b1134abf90 · report fixture: signature jet:ndarray/2/float · returned float64 · level recorded, date not recorded
jet_pt tf1/utils.py ran MIT (permissive) · e28433fdc4f312cc · report fixture: signature jet:ndarray/2/float · returned float32 · level recorded 2026-09-25
load_scaler tf1/utils.py ran MIT (permissive) · 5c254e62e9e1ba97 · report fixture: signature filename:str/0/str, key:str/0/str, len_input:int/0/int, pt_scaling:bool/0/bool · returned RobustScaler · level recorded 2026-09-25
load_test tf2/utils.py unverified MIT (permissive) · aac9738b35e2457f · report

Tasks

Jet TaggingOutlier Detection

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

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