The Upgrade I of LHCb VELO -- towards an intelligent monitoring platform
P. Kopciewicz, T. Szumlak, M. Majewski, K. Akiba, O. Augusto, J. Back,, D. S. Bobulska, G. Bogdanova, S. Borghi, T. Bowcock, J. Buytaert, E. Lemos, Cid, V. Coco, P. Collins, E. Dall'Occo, K. de Bruyn, S. de Capua, F. Dettori,, K. Dreimanis, D. Dutta, L. Eklund, T. Evans

TL;DR
This paper discusses the upgrade of the LHCb VELO detector to handle increased data rates and luminosity, incorporating advanced technologies for improved performance and monitoring.
Contribution
It introduces an intelligent monitoring platform for the upgraded VELO detector, integrating state-of-the-art detector technologies and data handling capabilities.
Findings
Design of a high-rate, radiation-hard VELO detector with 52 modules.
Expected data output rate of 1.6 Tbit/s for the upgraded detector.
First detector to read out at the full LHC rate of 40 MHz.
Abstract
The Large Hadron Collider beauty (LHCb) detector is designed to detect decays of b- and c- hadrons for the study of CP violation and rare decays. At the end of the LHC Run 2, many of the LHCb measurements remained statistically dominated. In order to increase the trigger yield for purely hadronic channels, the hardware trigger will be removed, and the detector will be read out at 40 MHz. This, in combination with the five-fold increase in luminosity, requires radical changes to LHCb's electronics, and, in some cases, the replacement of entire sub-detectors with state-of-the-art detector technologies. The Vertex Locator (VELO) surrounding the interaction region is used to reconstruct the collision points (primary vertices) and decay vertices of long-lived particles (secondary vertices). The upgraded VELO will be composed of 52 modules placed along the beam axis divided into two…
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
