Abstract
In 2010 ATLAS has seen the first proton-proton collisions at 7 TeV. This year a collision rate of nearly 10 MHz has been achieved. Events of potential interest for physics analysis are selected by a three-level trigger system, with a final recording rate of about 200 Hz. The first level (LI) is implemented in customized hardware, the two levels of the high level trigger (HLT) are software triggers. The selection is described by the Trigger Configuration in the form of menus, each of which contains about 400 signatures. Each signature corresponds to a chain of algorithms which reconstruct and refine specific event features. The HLT Steering receives information from the Configuration system, dynamically creates chains and controls the execution of algorithms and flow of information during event processing. The Steering tests each signature on LI-accepted events, and those satisfying one or more test are recorded for later analysis. To save execution time, the Steering has a facility to cache results, avoiding later recalculation. To control rate, prescale factors can be applied to LI or HLT signatures. Where needed for later analysis, the Steering has a test-after-accept functionality to provide the results of the tests for prescaled signatures. In order to maintain a high selection efficiency it is essential that the trigger can be dynamically re-configured in response to changes in the detector or machine conditions, such as the status of detector readout elements, instantaneous LHC luminosity and beam-spot position. This relies on techniques that allow configuration changes, such as LI and HLT prescale updates, to be made during a run without disrupting data taking, while ensuring a consistent and reproducible configuration across the entire HLT farm. We present the performance of the trigger system during collisions, showing the evolution with LHC luminosity and briefly describe the expectations for the next phase of LHC exploitation.
Highlights
– Prescale at HLT applied before chain execution
● Check whether to start the chain based on decision of previous level ● Apply prescale factor before execution ● Execute algorithms of each chain
● Event processing in L2/Event Filter (EF) not ordered by Luminosity Block (LB) ● Possible restart of HLT aplication during a run ● A single HLT application may not process events from a given Lumi Block
Summary
● Check whether to start the chain based on decision of previous level ● Apply prescale factor before execution ● Execute algorithms of each chain. – Selection based on dedicated algorithms – Reconstruction in Regions-Of-Interest (ROI) ● Minimize data transfer and CPU usage – Selection based on offline algorithms – Full event information available – Primarily ROI-based reconstruction Calo Muon MinBias 40MHz L1 Accept ~75kHz
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Disclaimer: 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.