Cargando…
The Software Architecture of the LHCb High Level Trigger
<!--HTML-->The LHCb experiment is a spectrometer dedicated to the study of heavy flavor at the LHC. The rate of proton-proton collisions at the LHC is 15 MHz, but disk space limitations mean that only 3 kHz can be written to tape for offline processing. For this reason the LHCb data acquisitio...
Autor principal: | |
---|---|
Lenguaje: | eng |
Publicado: |
2012
|
Materias: | |
Acceso en línea: | http://cds.cern.ch/record/1460606 |
_version_ | 1780925244084584448 |
---|---|
author | Witek, Mariusz |
author_facet | Witek, Mariusz |
author_sort | Witek, Mariusz |
collection | CERN |
description | <!--HTML-->The LHCb experiment is a spectrometer dedicated to the study of heavy flavor at the LHC. The rate of proton-proton collisions at the LHC is 15 MHz, but disk space limitations mean that only 3 kHz can be written to tape for offline processing. For this reason the LHCb data acquisition system -- trigger -- plays a key role in selecting signal events and rejecting background. In contrast to previous experiments at hadron colliders like for example CDF or D0, the bulk of the LHCb trigger is implemented in software and deployed on a farm of 20k parallel processing nodes. This system, called the High Level Trigger (HLT) is responsible for reducing the rate from the maximum at which the detector can be read out, 1.1 MHz, to the 3 kHz which can be processed offline,and has 20 ms in which to process and accept/reject each event. In order to minimize systematic uncertainties, the HLT was designed from the outset to reuse the offline reconstruction and selection code, and is based around multiple independent and redundant, selection algorithms, which make it possible to trigger efficiently even in the case that one of the detector subsystems fails. Because of specific LHC running conditions, the HLT had to cope with three times higher event multiplicities than it was designed for in 2010 and 2011. This contribution describes the software architecture of the HLT, focusing on the code optimization and commissioning effort which took place during 2010 and 2011 in order to enable LHCb to trigger efficiently in these unexpected running conditions, and the flexibility and robustness of the LHCb software framework which allowed this reoptimization to be performed in a timely manner. We demonstrate that the software architecture of the HLT, in particular the concepts of algorithm redundancy and independence, were crucial to enable LHCb to deliver its nominal trigger signal efficiency and background rejection rate in these unexpected conditions, and outline lessons for future trigger design in particle physics experiments. |
id | cern-1460606 |
institution | Organización Europea para la Investigación Nuclear |
language | eng |
publishDate | 2012 |
record_format | invenio |
spelling | cern-14606062022-11-02T22:23:44Zhttp://cds.cern.ch/record/1460606engWitek, MariuszThe Software Architecture of the LHCb High Level TriggerComputing in High Energy and Nuclear Physics (CHEP) 2012Conferences<!--HTML-->The LHCb experiment is a spectrometer dedicated to the study of heavy flavor at the LHC. The rate of proton-proton collisions at the LHC is 15 MHz, but disk space limitations mean that only 3 kHz can be written to tape for offline processing. For this reason the LHCb data acquisition system -- trigger -- plays a key role in selecting signal events and rejecting background. In contrast to previous experiments at hadron colliders like for example CDF or D0, the bulk of the LHCb trigger is implemented in software and deployed on a farm of 20k parallel processing nodes. This system, called the High Level Trigger (HLT) is responsible for reducing the rate from the maximum at which the detector can be read out, 1.1 MHz, to the 3 kHz which can be processed offline,and has 20 ms in which to process and accept/reject each event. In order to minimize systematic uncertainties, the HLT was designed from the outset to reuse the offline reconstruction and selection code, and is based around multiple independent and redundant, selection algorithms, which make it possible to trigger efficiently even in the case that one of the detector subsystems fails. Because of specific LHC running conditions, the HLT had to cope with three times higher event multiplicities than it was designed for in 2010 and 2011. This contribution describes the software architecture of the HLT, focusing on the code optimization and commissioning effort which took place during 2010 and 2011 in order to enable LHCb to trigger efficiently in these unexpected running conditions, and the flexibility and robustness of the LHCb software framework which allowed this reoptimization to be performed in a timely manner. We demonstrate that the software architecture of the HLT, in particular the concepts of algorithm redundancy and independence, were crucial to enable LHCb to deliver its nominal trigger signal efficiency and background rejection rate in these unexpected conditions, and outline lessons for future trigger design in particle physics experiments.oai:cds.cern.ch:14606062012 |
spellingShingle | Conferences Witek, Mariusz The Software Architecture of the LHCb High Level Trigger |
title | The Software Architecture of the LHCb High Level Trigger |
title_full | The Software Architecture of the LHCb High Level Trigger |
title_fullStr | The Software Architecture of the LHCb High Level Trigger |
title_full_unstemmed | The Software Architecture of the LHCb High Level Trigger |
title_short | The Software Architecture of the LHCb High Level Trigger |
title_sort | software architecture of the lhcb high level trigger |
topic | Conferences |
url | http://cds.cern.ch/record/1460606 |
work_keys_str_mv | AT witekmariusz thesoftwarearchitectureofthelhcbhighleveltrigger AT witekmariusz computinginhighenergyandnuclearphysicschep2012 AT witekmariusz softwarearchitectureofthelhcbhighleveltrigger |