ATLAS

Abstract:

The processing of ATLAS event data requires access to conditions data which are stored in database systems. This data includes, for example alignment, calibration, and configuration information which may be characterized by large volumes, diverse content, and/or information which evolves over time as refinements are made in those conditions. Additional layers of complexity are added by the need to provide this information across the worldwide ATLAS computing grid and the sheer number of simultaneously executing processes on the grid, each demanding a unique set of conditions to proceed. Distributing this data to all the processes that require it in an efficient manner has proven to be an increasing challenge with the growing needs and numbers of event-wise tasks. In this presentation, we briefly describe the systems in which we have collected information about the database content and the use of conditions in event data processing. We then proceed to explain how this information has been used not only to refine reconstruction software and job configuration but also to guide modifications of underlying conditions data configuration and in some cases, rewrites of the data in the database into a more harmonious form for offline usage in the processing of both real and simulated data..

Abstract:

Processing ATLAS event data requires a wide variety of auxiliary information from geometry, trigger, and conditions database systems. This information is used to dictate the course of processing and refine the measurement of particle trajectories and energies to construct a complete and accurate picture of the remnants of particle collisions. Such processing occurs on a worldwide computing grid, necessitating wide-area access to this information. Event processing tasks may deploy thousands of jobs. Each job calls for a unique set of information from the databases via SQL queries to dedicated squids in the ATLAS Frontier system, a system designed to pass queries to the database only if that result has not already been cached from another request. Many queries passing through Frontier are logged in an Elastic Search cluster along with pointers to the associated tasks and jobs, various metrics, and states at the time of execution. PanDA, which deploys the jobs, stores various configuration files as well as many log files after each job completes. Information is stored at each stage, but no system contains all information needed to draw a complete picture. This presentation describes the challenges of mining information from these sources to compile a view of database usage by jobs and tasks as well as assemble a global picture of the coherence and competition of tasks in resource usage to identify inefficiencies and bottlenecks within the overall system.

Abstract:

Narrow resonances decaying into W W, W Z or ZZ boson pairs are searched for in 139 fb−1 of proton-proton collision data at a centre-of-mass energy of s = 13 TeV recorded with the ATLAS detector at the Large Hadron Collider from 2015 to 2018. The diboson system is reconstructed using pairs of high transverse momentum, large-radius jets. These jets are built from a combination of calorimeter- and tracker-inputs compatible with the hadronic decay of a boosted W or Z boson, using jet mass and substructure properties. The search is performed for diboson resonances with masses greater than 1.3 TeV. No significant deviations from the background expectations are observed. Exclusion limits at the 95% confidence level are set on the production cross-section times branching ratio into dibosons for resonances in a range of theories beyond the Standard Model, with the highest excluded mass of a new gauge boson at 3.8 TeV in the context of mass-degenerate resonances that couple predominantly to gauge bosons.