Papers › Simplified fast detector simulation in MadAnalysis 5
Simplified fast detector simulation in MadAnalysis 5
Jack Y. Araz, Benjamin Fuks, Georgios Polykratis
The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.
We introduce a new simplified fast detector simulator in the MadAnalysis 5 platform. The Python-like interpreter of the programme has been augmented by new commands allowing for a detector parametrisation through smearing and efficiency functions. On run time, an associated C++ code is automatically generated and executed to produce reconstructed-level events. In addition, we have extended the MadAnalysis 5 recasting infrastructure to support our detector emulator, and we provide predefined LHC detector configurations. We have compared predictions obtained with our approach to those resulting from the usage of the Delphes 3 software, both for Standard Model processes and a few new physics signals. Results generally agree to a level of about 10% or better, the largest differences in the predictions stemming from the different strategies that are followed to model specific detector effects. Equipped with these new functionalities, MadAnalysis 5 now offers a new user-friendly way to include detector effects when analysing collider events, the simulation of the detector and the analysis being both handled either through a set of intuitive Python commands or directly within the C++ core of the platform.
Code
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
Not run by Syntology. Nothing on this page verifies that the listed code works.
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