Abstract
LHCb is one of the 4 LHC experiments and continues to revolutionise data acquisition and analysis techniques. Already two years ago the concepts of “online” and “offline” analysis were unified: the calibration and alignment processes take place automatically in real time and are used in the triggering process such that Online data are immediately available offline for physics analysis (Turbo analysis), the computing capacity of the HLT farm has been used simultaneously for different workflows : synchronous first level trigger, asynchronous second level trigger, and Monte-Carlo simulation. Thanks to the same software environment, LHCb can switch seamlessly and fast from Online to Offline workflows, run them simultaneously and thus maximize the usage of the HLT farm computing resources.
Highlights
LHCb [1] is one of the 4 LHC experiment at CERN and which has been active for 10 years
3.2 High Level Trigger 2 The High Level Trigger 2 (HLT2) is run asynchronously on the High Level Trigger 1 (HLT1) output which has been buffered on the local disk of the HLT farm worker nodes and reduces the rate to 12 kHz
The simulation software is installed on CernVM File System (CVMFS) and the environment is set in the same way as the HLT2 software
Summary
LHCb [1] is one of the 4 LHC experiment at CERN and which has been active for 10 years. The data taken by the detector are processed by a set of computers in real time to decrease the amount of information that will be stored on tape for analysis purpose afterwards by physics community. The computing capacity is quite important and LHCb has decided to use this capacity during idle cycle to process some Monte Carlo generations. We will describe the environment of the High Level Trigger (HLT) farm, the various workflows that we use and how we are able to have this concept of “online” and “offline” analysis unified
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.