Journal article
Search for leptoquark pair production decaying into t e - t ¯ e + or t μ - t ¯ μ + in multi-lepton final states in pp collisions at s = 13 TeV with the ATLAS detector
- Abstract:
- A search for leptoquark pair production decaying into te-t¯e+ or tμ-t¯μ+ in final states with multiple leptons is presented. The search is based on a dataset of pp collisions at s=13TeV recorded with the ATLAS detector during Run 2 of the Large Hadron Collider, corresponding to an integrated luminosity of 139 fb-1. Four signal regions, with the requirement of at least three light leptons (electron or muon) and at least two jets out of which at least one jet is identified as coming from a b-hadron, are considered based on the number of leptons of a given flavour. The main background processes are estimated using dedicated control regions in a simultaneous fit with the signal regions to data. No excess above the Standard Model background prediction is observed and 95% confidence level limits on the production cross section times branching ratio are derived as a function of the leptoquark mass. Under the assumption of exclusive decays into te- (tμ-), the corresponding lower limit on the scalar mixed-generation leptoquark mass mLQmixd is at 1.58 (1.59) TeV and on the vector leptoquark mass mU~1 at 1.67 (1.67) TeV in the minimal coupling scenario and at 1.95 (1.95) TeV in the Yang–Mills scenario.
- Publication status:
- Published
- Peer review status:
- Peer reviewed
Actions
Access Document
- Files:
-
-
(Preview, Version of record, pdf, 5.4MB, Terms of use)
-
- Publisher copy:
- 10.1140/epjc/s10052-024-12975-4
Authors
- Publisher:
- SpringerOpen
- Journal:
- The European Physical Journal C More from this journal
- Volume:
- 84
- Issue:
- 8
- Article number:
- 818
- Publication date:
- 2024-08-14
- Acceptance date:
- 2024-06-02
- DOI:
- EISSN:
-
1434-6052
- Language:
-
English
- Source identifiers:
-
2191084
- Deposit date:
-
2024-08-15
This ORA record was generated from metadata provided by an external service. It has not been edited by the ORA Team.
If you are the owner of this record, you can report an update to it here: Report update to this record