Abstract
The design and performance of the ATLAS Inner Detector (ID) trigger algorithms running online on the High Level Trigger (HLT) computing cluster with the early LHC Run 2 data are discussed. During the LHC shutdown from 2013 to 2015, the HLT farm was redesigned to run in a single HLT stage, rather than in two stages (Level 2 and Event Filter) as was used in Run 1. This allowed for a redesign of the HLT ID tracking algorithm, which aims to satisfy the challenging demands of the higher collision energy of the LHC in Run 2 and is essential for tracking of different charged particles in the ATLAS detector. The detailed performance of the tracking algorithms with the initial Run 2 data is discussed for electrons, muons and other charged particles. Comparison with the Run 1 strategy is made and demonstrates the superior performance of the strategy adopted for Run 2.
Highlights
The ATLAS detector is one of the general-‐purpose detectors located at the Large Hadron Collider (LHC) [1,2]
The Inner Detector (ID), as one of the major components of the ATLAS detector, provides vital information for the tracking and identification of charged particles. It is composed of three sub-‐detectors: two silicon detectors, which are the Pixel and the Semiconductor Tracker (SCT), and a Transition Radiation Tracker (TRT)
High Level Trigger (HLT) in Run 2 has been merged into a single stage, allowing for a redesigned ID tracking algorithm
Summary
The ATLAS detector is one of the general-‐purpose detectors located at the Large Hadron Collider (LHC) [1,2]. The ID, as one of the major components of the ATLAS detector, provides vital information for the tracking and identification of charged particles. It is composed of three sub-‐detectors: two silicon detectors, which are the Pixel and the Semiconductor Tracker (SCT), and a Transition Radiation Tracker (TRT). A significantly higher luminosity is foreseen, which primarily comes from the reduced colliding proton bunch interval and the increased additional proton-‐proton interactions per bunch crossing, , referred to as pile-‐up. This produces a more complex tracking environment. Run 2 with a faster decision-‐making and reasonable tracking performance
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
