Abstract

The ATLAS (A Toroidal LHC ApparatuS) trigger system is designed to keep high effiency for interesting events while achieving a rejection of low transverse momentum ( p T ) physics of about 10 7 , thus reaching the ∼200 Hz data storage capability of the Data Aquisition system. A three levels structure has been implemented for this purpose, as described in this work for the case of the muon trigger system. After describing the implementation, some performance results are presented in terms of final trigger rates, resolutions, efficiencies, background rejection and algorithm latency.

Highlights

  • 12 April 2007The ATLAS (A Toroidal Large Hadron Collider (LHC) ApparatuS) trigger system is designed to keep high effiency for interesting events while achieving a rejection of low transverse momentum (pT ) physics of about 107, reaching the ∼200 Hz data storage capability of the Data Aquisition system

  • High pT muons are important for many known processes, that can be used for monitoring and calibration (Z → μμ), and for several new phenomena (Higgs, SUSY), predicted at the energy of the Large Hadron Collider (LHC)

  • ∗sergio.grancagnolo@le.infn.it, I.N.F.N. fellow, Dipartimento di Fisica, via Arnesano, 73100 Lecce, Italy. It consists of resistive plate and thin gap trigger chambers (RPC and TGC) and precision detectors consisting of monitored drift tubes (MDT) and cathode strip chambers (CSC)

Read more

Summary

12 April 2007

The ATLAS (A Toroidal LHC ApparatuS) trigger system is designed to keep high effiency for interesting events while achieving a rejection of low transverse momentum (pT ) physics of about 107, reaching the ∼200 Hz data storage capability of the Data Aquisition system. A three levels structure has been implemented for this purpose, as described in this work for the case of the muon trigger system. Some performance results are presented in terms of final trigger rates, resolutions, efficiencies, background rejection and algorithm latency

Introduction
Level 1 trigger
Level 2 trigger
Event Filter
A trigger chain example Trigger software works with objects called
Conclusions
Full Text
Paper version not known

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 call

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.