REVIEW 1 cited by
Search for singly and pair-produced leptoquarks coupling to third-generation fermions in proton-proton collisions at $\sqrt{s} =$ 13 TeV
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
A search for leptoquarks produced singly and in pairs in proton-proton collisions is presented. We consider the leptoquark (LQ) to be a scalar particle of charge -1/3$e$ coupling to a top quark plus a tau lepton ($\mathrm{t}\tau$) or a bottom quark plus a neutrino ($\mathrm{b}\nu$), or a vector particle of charge +2/3$e$, coupling to $\mathrm{t}\nu$ or $\mathrm{b}\tau$. These choices are motivated by models that can explain a series of anomalies observed in the measurement of B meson decays. In this analysis the signatures $\mathrm{t}\tau\nu\mathrm{b}$ and $\mathrm{t}\tau\nu$ are probed, using data recorded by the CMS experiment at the CERN LHC at $\sqrt{s} =$ 13 TeV and that correspond to an integrated luminosity of 137 fb$^{-1}$. These signatures have not been previously explored in a dedicated search. The data are found to be in agreement with the standard model prediction. Lower limits at 95% confidence level are set on the LQ mass in the range 0.98-1.73 TeV, depending on the LQ spin and its coupling $\lambda$ to a lepton and a quark, and assuming equal branching fractions for the two LQ decay modes considered. These are the most stringent constraints to date on the existence of leptoquarks in this scenario.
Forward citations
Cited by 1 Pith paper
-
Jet Substructure Probe on Scalar Leptoquark Models via Top Polarization
A simulation study projects up to 5.4 sigma discovery significance for scalar leptoquarks at the HL-LHC and up to 3.2 sigma separation between the S3 and R2 models using a BDT score.
Discussion (0). Continue with ORCID to comment.