Abstract
ATLAS is embarking on a project to multithread its reconstruction software in time for use in Run 3 of the LHC. One component that must be migrated is the histogramming infrastructure used for data quality monitoring of the reconstructed data. This poses unique challenges due to its large memory footprint which forms a bottleneck for parallelization and the need to accommodate relatively inexperienced developers. We discuss plans for the upgraded framework.
Highlights
The ATLAS experiment [1] at the Large Hadron Collider (LHC) utilizes multiple layers of monitoring to verify the condition of the detector and the quality of collected data
One core component, AthenaMonitoring, is code that runs in the ATLAS data processing framework Athena [2] to produce histograms as part of the standard reconstruction of the data
One example identified early on was a plot of the mean number of channels reporting a signal in each module of a detector; the final histogram has one entry per detector module, and the value plotted is the mean occupancy accumulated over many events
Summary
The ATLAS experiment [1] at the Large Hadron Collider (LHC) utilizes multiple layers of monitoring to verify the condition of the detector and the quality of collected data. One core component, AthenaMonitoring, is code that runs in the ATLAS data processing framework Athena [2] (based on Gaudi [3]) to produce histograms as part of the standard reconstruction of the data. In preparation for Run 3 of the LHC, the Athena framework is being updated to support a multithreaded execution mode. This will require many changes to the Athena user code base, including AthenaMonitoring. This presents an opportunity to rectify some flaws in the current monitoring framework implementation
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
