Difference: Trigger (1 vs. 3)
Revision 331 Aug 2010 - SimonGeorge
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
| Added: | ||||||||
| > > | The ATLAS Trigger | |||||||
| Changed: | ||||||||
| < < | High Level Trigger Software for ATLAS | |||||||
| > > | Students and staff from RHUL are involved in a wide range of work on the ATLAS Trigger, from developing software to select electrons in a few milliseconds, to day-to day online operation of the trigger.
The ATLAS trigger has to sift through the debris of LHC proton bunch collisions that occur at up to 40 million times per second, and select only a few hundred per second of these 'events' to save for further analysis. The rest are lost for ever. So, no pressure then! | |||||||
| Added: | ||||||||
| > > | ATLAS has designed a three-level trigger system to perform this challenging task. It was designed, built and commissioning by a community of over 500 people from universities and labs all over the world, including RHUL. The first level is realised in custom-built electronics (FPGA and ASIC in case you're an interested electronics expert). The higher level trigger (HLT) is implemented as software running on a network of around 2300 computers. We've been developing several parts of this software, including the framework and some of the algorithms. | |||||||
| Added: | ||||||||
| > > | ||||||||
| Changed: | ||||||||
| < < | We are involved in the management of the Atlas Trigger, with leadership in the areas of software coordination and trigger algorithms. We have also represented the interests of several key physics groups in the menu coordination group. | |||||||
| > > |  | |||||||
| RHUL staff and students regularly play their part in operating the trigger, with expert roles and shifts in the Atlas Control Room. | ||||||||
| Added: | ||||||||
| > > | Special training is given so you can sit at the trigger desk all night and know what to do when the trigger rate goes up - or down - unexpectedly. | |||||||
| Changed: | ||||||||
| < < | The trigger software project has about ... lines of code, ... developers and we build ... releases per year. Trigger algorithms are produced though collaboration between trigger experts, reconstruction developers and physics analysis groups to give the optimum balance between technical performance (memory, cpu and network usage), the best rejection and least biased selection. This performance has to be validated before use and monitored once it is on-line. Students and staff from RHUL have been involved in all parts of this process, including recent work in electron/photon triggers. | |||||||
| > > | RHUL staff have a long standing involvement in the management of the Atlas Trigger, with leadership in the areas of software coordination and trigger algorithms. We have also represented the interests of several key physics groups in the trigger menu coordination group, where the high-level strategies for the trigger are decided. | |||||||
| Added: | ||||||||
| > > | The trigger software project has about a million lines of C++/Python code, ~50 active developers and we build about 20 releases per year. In a typical week we have ~100 open bugs and 50 opened/closed. RHUL staff coordinate this work and develop many of the tools and procedures for managing and validating all this the software. | |||||||
| Changed: | ||||||||
| < < | ||||||||
| > > |
<-- stats based on http://indico.cern.ch/getFile.py/access?contribId=3&sessionId=0&resId=0&materialId=slides&confId=50977 | |||||||
| ||||||||
| Line: 29 to 37 | ||||||||
| ||||||||
| Added: | ||||||||
| > > | ||||||||
| ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| ||||||||
| Added: | ||||||||
| > > |
| |||||||
Revision 231 Aug 2010 - SimonGeorge
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
| Deleted: | ||||||||
| < < | ||||||||
High Level Trigger Software for ATLAS | ||||||||
| Line: 6 to 5 | ||||||||
| ||||||||
| Added: | ||||||||
| > > | We are involved in the management of the Atlas Trigger, with leadership in the areas of software coordination and trigger algorithms. We have also represented the interests of several key physics groups in the menu coordination group. RHUL staff and students regularly play their part in operating the trigger, with expert roles and shifts in the Atlas Control Room. The trigger software project has about ... lines of code, ... developers and we build ... releases per year. Trigger algorithms are produced though collaboration between trigger experts, reconstruction developers and physics analysis groups to give the optimum balance between technical performance (memory, cpu and network usage), the best rejection and least biased selection. This performance has to be validated before use and monitored once it is on-line. Students and staff from RHUL have been involved in all parts of this process, including recent work in electron/photon triggers. | |||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| ||||||||
| Changed: | ||||||||
| < < |
| |||||||
| > > |
| |||||||
| Added: | ||||||||
| > > |
| |||||||
| Added: | ||||||||
| > > |
| |||||||
| ||||||||
| Added: | ||||||||
| > > |
| |||||||
Revision 103 Apr 2008 - VeroniqueBoisvert
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
| Added: | ||||||||
| > > |
High Level Trigger Software for ATLAS
We lead the ATLAS High Level Trigger project for the development of the software suite for the physics event selection. Activity in this area has concentrated on the development of a control framework for the development and testing of trigger algorithms. We have been major contributors to the development of a new stand-alone software package ("PESASim") to emulate the trigger response and allow the fast and realistic determination of trigger efficiencies and background rates for the optimization of trigger event selections.
Current projects focus on release integration of HLT source code as well as development of analysis tools.
| |||||||
View topic | History: r3 < r2 < r1 | More topic actions...
Copyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Ideas, requests, problems regarding RHUL Physics Department TWiki? Send feedback