Abstract
Processing and scientific analysis of the data taken by the ATLAS experiment requires reliable information describing the event data recorded by the detector or generated in software. ATLAS event processing applications store such descriptive metadata information in the output data files along with the event information. To better leverage the available computing resources during LHC Run3 the ATLAS experiment has migrated its data processing and analysis software to a multi-threaded framework: AthenaMT. Therefore in-file metadata must support concurrent event processing, especially around input file boundaries. The in-file metadata handling software was originally designed for serial event processing. It grew into a rather complex system over the many years of ATLAS operation. To migrate this system to the multi-threaded environment it was necessary to adopt several pragmatic solutions, mainly because of the shortage of available person-power to work on this project in early phases of the AthenaMT development. In order to simplify the migration, first the redundant parts of the code were cleaned up wherever possible. Next the infrastructure was improved by removing reliance on constructs that are problematic during multi-threaded processing. Finally, the remaining software infrastructure was redesigned for thread safety.
Highlights
Modern particle physics experiments produce a variety of data required to perform physical measurements
As the effort of the ATLAS collaboration to produce thread safe production software, AthenaMT [3, 4], resulted in mature code it became clear that the in-file metadata infrastructure required improvement
During the review of the ATLAS metadata handling software components, it was determined that the current implementation of the Luminosity Block metadata handling mechanism can be considered AthenaMT-compatible
Summary
Modern particle physics experiments produce a variety of data required to perform physical measurements. The elementary measurement of the ATLAS detector [1] is an event: the detector response to a collision at its center. The event may be the physical response of the detector to a collision delivered by the Large Hadron Collider or the simulated detector
Sign-in/Register to view highlights & summary 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.
