2024 Articles
A search for top-squark pair production, in final states containing a top quark, a charm quark and missing transverse momentum, using the 139 fbβ»ΒΉ of ππ collision data collected by the ATLAS detector
This paper presents a search for top-squark pair production in final states with a top quark, a charm quark and missing transverse momentum. The data were collected with the ATLAS detector during LHC Run 2 and correspond to an integrated luminosity of 139 fbβ»ΒΉ search for top-squark pair production, in final states containing a top quark of proton-proton collisions at a centre-of-mass energy of βs = 13 TeV. The analysis is motivated by an extended Minimal Supersymmetric Standard Model featuring a non-minimal flavour violation in the second- and third-generation squark sector.
The top squark in this model has two possible decay modes, either π‘Μβ β πΟΜββ° or π‘Μβ β π‘ΟΜββ°, where the ΟΜββ° is undetected. The analysis is optimised assuming that both of the decay modes are equally probable, leading to the most likely final state of π‘π + πΈ_π ^miss. Good agreement is found between the Standard Model expectation and the data in the search regions. Exclusion limits at 95% CL are obtained in the π(π‘Μβ ) vs. π(ΟΜββ°) plane and, in addition, limits on the branching ratio of the π‘Μβ β π‘ΟΜββ° decay as a function of π(π‘Μβ ) are also produced. Top-squark masses of up to 800 GeV are excluded for scenarios with light neutralinos, and top-squark masses up to 600 GeV are excluded in scenarios where the neutralino and the top squark are almost mass degenerate.
Subjects
Files
-
13130_2024_Article_24087.pdf application/pdf 2.21 MB Download File
Also Published In
- Title
- Journal of High Energy Physics
- DOI
- https://doi.org/10.1007/JHEP07(2024)250
More About This Work
- Academic Units
- Physics
- Published Here
- October 9, 2024
Notes
Beyond Standard Model, Hadron-Hadron Scattering , Supersymmetry
SWORD deposit contains more than 40 names, only first 40 processed. See mets.xml for full list. Large number of Name fields will generate error in Hyacinth. See JIRA ticket SWORD-86.