Papers › Portraying Double Higgs at the Large Hadron Collider II

Portraying Double Higgs at the Large Hadron Collider II

22 Mar 2022arXiv:2203.11951links table onlyarchive 2025-07-28

Li Huang, Su-beom Kang, Jeong Han Kim, Kyoungchul Kong, Jun Seung Pi

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.

The Higgs potential is vital to understand the electroweak symmetry breaking mechanism, and probing the Higgs self-interaction is arguably one of the most important physics targets at current and upcoming collider experiments. In particular, the triple Higgs coupling may be accessible at the HL-LHC by combining results in multiple channels, which motivates to study all possible decay modes for the double Higgs production. In this paper, we revisit the double Higgs production at the HL-LHC in the final state with two b-tagged jets, two leptons and missing transverse momentum. We focus on the performance of various neural network architectures with different input features: low-level (four momenta), high-level (kinematic variables) and image-based. We find it possible to bring a modest increase in the signal sensitivity over existing results via careful optimization of machine learning algorithms making a full use of novel kinematic variables.

PaperPDFCode

Code

junseungpi/dihiggs officialmentioned in papermentioned on GitHubpytorch 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

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