A programmatic view of metadata, metadata services, and metadata flow in ATLAS
Journal of Physics: Conference Series 396:PART 5 (2012)
Abstract:
The volume and diversity of metadata in an experiment of the size and scope of ATLAS are considerable. Even the definition of metadata may seem context-dependent: data that are primary for one purpose may be metadata for another. ATLAS metadata services must integrate and federate information from inhomogeneous sources and repositories, map metadata about logical or physics constructs to deployment and production constructs, provide a means to associate metadata at one level of granularity with processing or decision-making at another, offer a coherent and integrated view to physicists, and support both human use and programmatic access. In this paper we consider ATLAS metadata, metadata services, and metadata flow principally from the illustrative perspective of how disparate metadata are made available to executing jobs and, conversely, how metadata generated by such jobs are returned. We describe how metadata are read, how metadata are cached, and how metadata generated by jobs and the tasks of which they are a part are communicated, associated with data products, and preserved. We also discuss the principles that guide decision-making about metadata storage, replication, and access..ATLAS file and dataset metadata collection and use
Journal of Physics: Conference Series 396:PART 5 (2012)
Abstract:
The ATLAS Metadata Interface ("AMI") was designed as a generic cataloguing system, and as such it has found many uses in the experiment including software release management, tracking of reconstructed event sizes and control of dataset nomenclature. The primary use of AMI is to provide a catalogue of datasets (file collections) which is searchable using physics criteria. In this paper we discuss the various mechanisms used for filling the AMI dataset and file catalogues. By correlating information from different sources we can derive aggregate information which is important for physics analysis; for example the total number of events contained in dataset, and possible reasons for missing events such as a lost file. Finally we will describe some specialized interfaces which were developed for the Data Preparation coordinators. These interfaces manipulate information from both the dataset domain held in AMI, and the run-indexed information held in the ATLAS COMA application (Conditions and Configuration MetadatA)..ATLAS measurements of WW, WZ, and ZZ production
Proceedings of Science 2012-July (2012)
Abstract:
Using data corresponding to 4.6-4.7 fb-1 of integrated luminosity from s = 7 TeV pp collisions at the LHC, the ATLAS Collaboration has measured the production cross section of heavy dibosons (WW, WZ, and ZZ) in the fully leptonic decay channels. A first measurement of ZZ production at s = 8 TeV with data corresponding to 5.8 fb-1 of integrated luminosity has also been performed. Differential cross sections are measured for WZ production, and limits are set on anomalous WWZ and WW? couplings.ATLAS search for a heavy gauge boson decaying to a charged lepton and a neutrino in pp collisions at √s =7 TeV
European Physical Journal C 72:12 (2012)
Abstract:
The ATLAS detector at the LHC is used to search for high-mass states, such as heavy charged gauge bosons (Wʹ), decaying to a charged lepton (electron or muon) and a neutrino. Results are presented based on the analysis of pp collisions at a center-of-mass energy of 7 TeV corresponding to an integrated luminosity of 4.7 fb−1. No excess beyond Standard Model expectations is observed. AWʹ with Sequential Standard Model couplings is excluded at the 95% credibility level for masses up to 2.55 TeV. Excited chiral bosons (W*) with equivalent coupling strength are excluded for masses up to 2.42 TeV.Centrality dependence of dihadron correlations and azimuthal anisotropy harmonics in PbPb collisions at √SNN = 2.76 Tev
European Physical Journal C 72:5 (2012) 1-26