Cluster reconstruction in the HGCAL at the Level 1 trigger

The CMS collaboration has chosen a novel High Granularity Calorimeter for the endcap regions as part of its planned upgrade for the High Luminosity LHC. The calorimeter will have fine segmentation in both the transverse and longitudinal directions, and its data will be part of the Level 1 trigger of...

Ausführliche Beschreibung

Gespeichert in:
Bibliographische Detailangaben
1. Verfasser: Alves, Bruno
Format: Tagungsbericht
Sprache:eng
Schlagworte:
Online-Zugang:Volltext
Tags: Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
Beschreibung
Zusammenfassung:The CMS collaboration has chosen a novel High Granularity Calorimeter for the endcap regions as part of its planned upgrade for the High Luminosity LHC. The calorimeter will have fine segmentation in both the transverse and longitudinal directions, and its data will be part of the Level 1 trigger of the CMS experiment. The trigger has tight constraints on latency and rate, and will need to be implemented in hardware. The high granularity results in around six million readout channels in total, reduced to one million that are used at 40 MHz as part of the Level 1 trigger, presenting a significant challenge in terms of data manipulation and processing; the trigger data volumes will be an order of magnitude above those currently handled at CMS. In addition, the high luminosity will result in an average of 140 (or more) interactions per bunch crossing. This leads to a huge rate by background processes which must be efficiently rejected by the trigger algorithms. Furthermore, reconstruction of the particle clusters to be used for particle flow in events with high hit rates is also a complex computational problem for the trigger. The status of the cluster reconstruction algorithms developed to tackle these major challenges, as well as the associated trigger architecture, is presented. Methods developed to mitigate the known issue of cluster splitting are described, incuding an iterative algorithm which has no impact on firmware resources.
ISSN:2100-014X
2101-6275
2100-014X
DOI:10.1051/epjconf/202429502006