REVIEW 1 cited by
The LHC higgsino discovery plane for present and future SUSY searches
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
read the original abstract
Considerations from electroweak naturalness and stringy naturalness imply a little hierarchy in supersymmetric models where the superpotential higgsino mass parameter mu is of order the weak scale whilst the soft SUSY breaking terms may be in the (multi-) TeV range. In such a case, discovery of SUSY at LHC may be most likely in the higgsino pair production channel. Indeed, ATLAS and CMS are performing searches in the higgsino mass discovery plane of m(chi_2^0) vs. \Delta m^0 = m(chi_2^0)-m(chi_1^0). We examine several theoretical aspects of this discovery plane in both the gravity-mediation NUHM2 model and the general mirage-mediation (GMM') models. These include: the associated chargino mass m(chi_1^+), the expected regions of the bottom-up notion of electroweak naturalness \Delta_{EW}, and the expected regions of stringy naturalness. While compatibility with electroweak naturalness allows for mass gaps \Delta m^0~ 4-20 GeV, stringy naturalness exhibits a clear preference for yet smaller mass gaps of 4-10 GeV. For still smaller mass gaps, the plane becomes sharply unnatural since very large gaugino masses are required. This study informs the most promising SUSY search channels and parameter space regions for the upcoming HL-LHC runs and possible HE-LHC option.
Forward citations
Cited by 1 Pith paper
-
The curtain lowers on directly detectable higgsino dark matter
Using LZ2024 limits, the paper derives new lower bounds on gaugino masses and upper bounds on higgsino mass splittings in decoupled-MSSM higgsino dark matter scenarios, plus projections for the neutrino fog.
Discussion (0). Continue with ORCID to comment.