REVIEW 2 cited by
LHC physics dataset for unsupervised New Physics detection at 40 MHz
Not yet reviewed by Pith; the record is open.
This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.
SPECIMEN: schema-true, not a live event
T0 review · schema-true
One-sentence machine reading of the paper's core claim.
pith:XXXXXXXX · record.json · timestamp
Signed reviews
read the original abstract
In particle detectors at the Large Hadron Collider, tens of terabytes of data are produced every second from proton-proton collisions occurring at a rate of 40 megahertz. This data rate is reduced to a sustainable level by a real-time event filter processing system which decides whether each collision event should be kept for further analysis or be discarded. We introduce a dataset of proton collision events which emulates a typical data stream collected by such a real-time processing system, pre-filtered by requiring the presence of at least one electron or muon. This dataset could be used to develop novel event selection strategies and assess their sensitivity to new phenomena. In particular, by publishing this dataset we intend to stimulate a community-based effort towards the design of novel algorithms for performing unsupervised New Physics detection, customized to fit the bandwidth, latency and computational resource constraints of the real-time event selection system of a typical particle detector.
Forward citations
Cited by 2 Pith papers
-
Generative Amplification with Surrogate Monte Carlo
An amplitude surrogate trained on a few thousand exact LHC amplitude points statistically outperforms the training data, with largest amplification in sparsely populated kinematic tails of Z+g and Z+4g production.
-
Analysis of Hardware Synthesis Strategies for Machine Learning in Collider Trigger and Data Acquisition
For small-to-medium fully connected VAE trigger encoders on an Alveo U200 FPGA, hls4ml achieves lower latency and SNL achieves lower LUT and FF usage at matched latency.
Discussion (0). Continue with ORCID to comment.