Journal article
Search for long-lived charged particles using large specific ionisation loss and time of flight in 140 fb − 1 of pp collisions at s = 13 TeV with the ATLAS detector
- Abstract:
- This paper presents a search for massive, charged, long-lived particles with the ATLAS detector at the Large Hadron Collider using an integrated luminosity of 140 fb−1 of proton-proton collisions at s = 13 TeV. These particles are expected to move significantly slower than the speed of light. In this paper, two signal regions provide complementary sensitivity. In one region, events are selected with at least one charged-particle track with high transverse momentum, large specific ionisation measured in the pixel detector, and time of flight to the hadronic calorimeter inconsistent with the speed of light. In the other region, events are selected with at least two tracks of opposite charge which both have a high transverse momentum and an anomalously large specific ionisation. The search is sensitive to particles with lifetimes greater than about 3 ns with masses ranging from 200 GeV to 3 TeV. The results are interpreted to set constraints on the supersymmetric pair production of long-lived R-hadrons, charginos and staus, with mass limits extending beyond those from previous searches in broad ranges of lifetime.
- Publication status:
- Published
- Peer review status:
- Peer reviewed
Actions
Access Document
- Files:
-
-
(Preview, Version of record, pdf, 2.5MB, Terms of use)
-
- Publisher copy:
- 10.1007/jhep07(2025)140
Authors
- Publisher:
- Springer
- Journal:
- Journal of High Energy Physics More from this journal
- Volume:
- 2025
- Issue:
- 7
- Article number:
- 140
- Publication date:
- 2025-07-11
- Acceptance date:
- 2025-06-17
- DOI:
- EISSN:
-
1029-8479
- ISSN:
-
1126-6708
- Language:
-
English
- Keywords:
- Source identifiers:
-
3118153
- Deposit date:
-
2025-07-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