REVIEW 2 cited by
Same-Sign Tetralepton Signature at Large Hadron Collider, and future $pp$ Collider
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
abstract
We analyze a novel signature of the type II seesaw model - same-sign tetra-lepton signal arising from the mixing of neutral Higgs bosons and their subsequent decays to singly and doubly charged Higgs bosons. For this, we consider wide ranges of the triplet vacuum expectation value (vev) and Yukawa couplings, that are consistent with the observed neutrino masses and mixing as well as the LHC search limits. We find that a doubly charged Higgs boson with mass around 250 GeV and triplet vev around $10^{-4}-10^{-2}$ GeV can give significantly large number of events through it decay to same-sign $W$ gauge bosons at High-Luminosity LHC with $3000 \text{fb}^{-1}$ of data. We also pursue the analysis for a future hadron collider with the c.m. energy of 100 TeV. Considering a heavy Higgs boson around 900 GeV and an intermediate region of the triplet vev, where both same-sign dilepton and gauge boson decays can occur, we identify a limited range of the parameters where the number of same-sign tetra-lepton events are as large as 1000.
Forward citations
Cited by 2 Pith papers
-
Probing Doubly Charged Higgs Bosons with Three-Body Associated Production at Future $e^+e^-$ Colliders
Doubly charged Higgs bosons in the type-II seesaw 2HDM can be produced via 2-to-3 associated channels at e+e- colliders with cross sections up to ~10^2 fb and good 4-lepton discovery sensitivity.
-
Probing Type II Seesaw Leptogenesis Through Lepton Flavor Violation
A scan over 3σ neutrino parameters yields the most conservative lower bounds on the triplet-Higgs cubic coupling from μ→eγ, μ→3e, and μ-e conversion.
Discussion (0). Continue with ORCID to comment.