A comprehensive real-time analysis model at the LHCb experiment

Information

LHCb-DP-2019-002
arXiv:1903.01360 [PDF]

(Submitted on 04 Mar 2019)
JINST 14 (2019) P04006
Inspire 1723258

Tools

Abstract

An evolved real-time data processing strategy is proposed for high-energy physics experiments, and its implementation at the LHCb experiment is presented. The reduced event model allows not only the signal candidate firing the trigger to be persisted, as previously available, but also an arbitrary set of other reconstructed or raw objects from the event. This allows for higher trigger rates for a given output data bandwidth, when compared to the traditional model of saving the full raw detector data for each trigger, whilst accommodating inclusive triggers and preserving data mining capabilities. The gains in physics reach and savings in computing resources already made possible by the model are discussed, along with the prospects of employing it more widely for Run 3 of the Large Hadron Collider.

Figures and captions

An overview of the LHCb trigger scheme in Run 2 [9]. The green boxes represent trigger stages, the blue ellipses represent storage units, and arrows between elements represent data flow, labelled with approximate flow rates. Events that reach a terminal storage unit are kept for offline analysis.	Figure1.pdf [36 KiB] HiDef png [273 KiB] Thumbnail [190 KiB]
Data flow in saving and restoring trigger objects from online (left) to offline (right) [2].	Figure2.pdf [36 KiB] HiDef png [277 KiB] Thumbnail [219 KiB]
A cartoon of the same reconstructed event with varying levels of object persistence: Turbo (top); selective persistence (middle); and complete reconstruction persistence (bottom). Solid objects are those persisted in each case. A trigger selection may also ask for one or more sub-detector raw banks to also be stored, shown as solid rectangles.	Figure3.pdf [59 KiB] HiDef png [342 KiB] Thumbnail [423 KiB]
Algorithm flow to decide whether a given raw bank is persisted for the current event. The resulting list of banks persisted for a given event is the superset of those required by the individual lines.	Figure4.pdf [16 KiB] HiDef png [180 KiB] Thumbnail [134 KiB]
Animated gif made out of all figures.	DP-2019-002.gif Thumbnail