Szczegóły publikacji
Opis bibliograficzny
Readout firmware of the Vertex Locator for LHCb Run 3 and beyond / Karol Hennessy, [et al.], Paweł KOPCIEWICZ, Maciej MAJEWSKI, Agnieszka OBŁĄKOWSKA-MUCHA, Bartłomiej RACHWAŁ, Tomasz SZUMLAK, [et al.] // IEEE Transactions on Nuclear Science ; ISSN 0018-9499. — 2021 — vol. 68 iss. 10, s. 2472–2479. — Bibliogr. s. 2479, Abstr.
Autorzy (70)
- AGHKopciewicz Paweł
- AGHMajewski Maciej W.
- AGHObłąkowska-Mucha Agnieszka
- AGHRachwał Bartłomiej
- AGHSzumlak Tomasz
- Hennessy Karol
- Prieto Antonio Fernández
Słowa kluczowe
Dane bibliometryczne
| ID BaDAP | 137138 |
|---|---|
| Data dodania do BaDAP | 2021-11-04 |
| Tekst źródłowy | URL |
| DOI | 10.1109/TNS.2021.3085018 |
| Rok publikacji | 2021 |
| Typ publikacji | artykuł w czasopiśmie |
| Otwarty dostęp |  |
| Creative Commons | |
| Czasopismo/seria | IEEE Transactions on Nuclear Science |
Abstract
The new LHCb Vertex Locator for LHCb, comprising a new pixel detector and readout electronics will be installed in 2021 for data-taking in Run 3 at the LHC. The electronics centres around the “VeloPix” ASIC at the front-end operating in a trigger-less readout at 40 MHz. A custom serialiser, called GWT (Gigabit Wireline Transmitter) and associated custom protocol have been designed for the VeloPix. The GWT data are sent from the serialisers of the VeloPix at a line rate of 5.12 Gb/s, reaching a total data rate of 2-3 Tb/s for the full VELO detector. Data are sent over 300m optic-fibre links to the control and readout electronics cards for deserialisation and processing in Intel® Arria 10 FPGAs. Due to the VeloPix trigger-less design, latency variances up to 12 μs can occur between adjacent datagrams. It is therefore essential to buffer and synchronise the data in firmware prior to onward propagation or suffer a huge CPU processing penalty. This paper will describe the architecture of the readout firmware in detail with focus given to the resynchronisation mechanism and techniques for clusterisation. Issues found during readout commissioning, and scaling resource utilisation, along with the their solutions, will be illustrated. The latest results of the firmware data processing chain be presented as well as the verification procedures employed in simulation. Challenges for the next generation of the detector will also be presented with ideas for a readout processing solution.