Abstract
The current LHCb trigger system consists of a hardware level, which reduces the LHC bunch-crossing rate of 40 MHz to 1.1 MHz, a rate at which the entire detector is read out. A second level, implemented in a farm of around 20k parallel processing CPUs, the event rate is reduced to around 12.5 kHz. The LHCb experiment plans a major upgrade of the detector and DAQ system in the LHC long shutdown II (2018-2019). In this upgrade, a purely software based trigger system is being developed and it will have to process the full 30 MHz of bunch crossings with inelastic collisions. LHCb will also receive a factor of 5 increase in the instantaneous luminosity, which further contributes to the challenge of reconstructing and selecting events in real time with the CPU farm. We discuss the plans and progress towards achieving efficient reconstruction and selection with a 30 MHz throughput. Another challenge is to exploit the increased signal rate that results from removing the 1.1 MHz readout bottleneck, combined with the higher instantaneous luminosity. Many charm hadron signals can be recorded at up to 50 times higher rate. LHCb is implementing a new paradigm in the form of real time data analysis, in which abundant signals are recorded in a reduced event format that can be fed directly to the physics analyses. These data do not need any further offline event reconstruction, which allows a larger fraction of the grid computing resources to be devoted to Monte Carlo productions. We discuss how this real-time analysis model is absolutely critical to the LHCb upgrade, and how it will evolve during Run-II.
Highlights
LHCb UpgradeNeed to remove hardware trigger (L0), i.e., move from the full detector readout done @1 MHz to 40 MHz one The upgraded LHCb must cope with up to five times higher inst
Luminosity relative to Run II (L = 2 ∙ 1033 cm−2s−1) Triggerless readout with the full software trigger that requires real-time calibration and alignment Offline-like reconstruction run in real time Use Run II trigger system as a testbed for new techniques for Run III
Since we aim at the HLT reconstruction to be of the offline quality – create a dedicated data stream that persists only the HLT candidates – Turbo stream Much smaller event size 70 kB/event vs. 5 kB/event (Turbo) No offline re-processing – ready for physics analysis immediately All Turbo trigger lines amount to ~ 2.5 kHz (~ 10 kHz for the full stream)
Summary
Need to remove hardware trigger (L0), i.e., move from the full detector readout done @1 MHz to 40 MHz one The upgraded LHCb must cope with up to five times higher inst.
Published Version (Free)
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have