REVIEW 2 cited by
Status of CMSSM in light of current LHC Run-2 and LUX data
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
Motivated by the latest results of the LHC Run-2 and LUX experiments, we examine the status of the constrained minimal supersymmetric standard model (CMSSM) by performing a global fit. We construct a likelihood function including the electroweak precision observables, $B$-physics measurements, LHC Run-1 and -2 data of SUSY direct searches, Planck observation of the dark matter relic density and the combined LUX Run-3 and -4 detection limits. Based on the profile likelihood functions of 1 billion samples, we obtain the following observations: (i) The stau coannihilation region has been mostly excluded by the latest LHC Run-2 data; (ii) The focus point region has been largely covered by the LUX-2016 limits while the $A$-funnel region has been severely restricted by flavor observables like $B_s \to \mu^+\mu^-$. The remaining parts of both regions will be totally covered by the future LZ dark matter experiment; (iii) The masses of the stop, the lightest neutralino and the gluino have been pushed up to 1033 GeV, 449 GeV and 2285 GeV, respectively.
Forward citations
Cited by 2 Pith papers
-
DLScanner: A parameter space scanner package assisted by deep learning methods
A new scanner package combines a similarity-learning neural network with VEGAS adaptive sampling to collect valid points in BSM parameter scans faster than earlier ML-based methods.
-
Revisiting CMSSM with Non-Universal Gaugino Masses under Current Constraints
Current data restrict the g~-SUGRA scenario to tanβ ≳ 5 and M0 ≳ 20 tanβ GeV, with large muon g-2 contributions difficult and future colliders needed to cover the remaining parameter space.
Discussion (0). Continue with ORCID to comment.