ATLAS

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.

Abstract:

Measurements from the CMS experiment at the LHC of dihadron correlations for charged particles produced in PbPb collisions at a nucleon-nucleon centre-of-mass energy of 2. 76 TeV are presented. The results are reported as a function of the particle transverse momenta (pT) and collision centrality over a broad range in relative pseudorapidity (Δη) and the full range of relative azimuthal angle (Δφ). The observed two-dimensional correlation structure in Δη and Δφ is characterised by a narrow peak at (Δη,Δφ)≈(0,0) from jet-like correlations and a long-range structure that persists up to at least {pipe}Δη{pipe}=4. An enhancement of the magnitude of the short-range jet peak is observed with increasing centrality, especially for particles of pT around 1-2 GeV/c. The long-range azimuthal dihadron correlations are extensively studied using a Fourier decomposition analysis. The extracted Fourier coefficients are found to factorise into a product of single-particle azimuthal anisotropies up to pT≈3-3. 5 GeV/c for at least one particle from each pair, except for the second-order harmonics in the most central PbPb events. Various orders of the single-particle azimuthal anisotropy harmonics are extracted for associated particle pT of 1-3 GeV/c, as a function of the trigger particle pT up to 20 GeV/c and over the full centrality range. © 2012 CERN for the benefit of the CMS collaboration.

Abstract:

A combination of the inclusive diffractive cross section measurements made by the H1 and ZEUS Collaborations at HERA is presented. The analysis uses samples of diffractive deep inelastic ep scattering data at a centre-of-mass energy √s= 318 Gev where leading protons are detected by dedicated spectrometers. Correlations of systematic uncertainties are taken into account, resulting in an improved precision of the cross section measurement which reaches 6 % for the most precise points. The combined data cover the range 2.5 < Q2 < 200 GeV2 in photon virtuality, 0.00035 < xP < 0.09 in proton fractional momentum loss, 0.09 <{pipe}t{pipe}< 0.55 GeV2 in squared four-momentum transfer at the proton vertex and 0.0018 < β <0.816 in β=x/xP, where x is the Bjorken scaling variable. © 2012 The Author(s).

Abstract:

In the ATLAS experiment, a system called COMA (Conditions/Configuration Metadata for ATLAS), has been developed to make globally important run-level metadata more readily accessible. It is based on a relational database storing directly extracted, refined, reduced, and derived information from system-specific database sources as well as information from non-database sources. This information facilitates a variety of unique dynamic interfaces and provides information to enhance the functionality of other systems. This presentation will give an overview of the components of the COMA system, enumerate its diverse data sources, and give examples of some of the interfaces it facilitates. We list important principles behind COMA schema and interface design, and how features of these principles create coherence and eliminate redundancy among the components of the overall system. In addition, we elucidate how interface logging data has been used to refine COMA content and improve the value and performance of end-user reports and browsers..

Abstract:

The ATLAS experiment deployed Frontier technology worldwide during the initial year of LHC collision data taking to enable user analysis jobs running on the Worldwide LHC Computing Grid to access database resident data. Since that time, the deployment model has evolved to optimize resources, improve performance, and streamline maintenance of Frontier and related infrastructure. In this presentation we focus on the specific changes in the deployment and improvements undertaken, such as the optimization of cache and launchpad location, the use of RPMs for more uniform deployment of underlying Frontier related components, improvements in monitoring, optimization of fail-over, and an increasing use of a centrally managed database containing site specific information (for configuration of services and monitoring). In addition, analysis of Frontier logs has allowed us a deeper understanding of problematic queries and understanding of use cases. Use of the system has grown beyond user analysis and subsystem specific tasks such as calibration and alignment, extending into production processing areas, such as initial reconstruction and trigger reprocessing. With a more robust and tuned system, we are better equipped to satisfy the still growing number of diverse clients and the demands of increasingly sophisticated processing and analysis..