The automated multi-platform software nightly build system is a major component in the ATLAS collaborative software organization, validation and code approval schemes. Code developers from ATLAS ...participating Institutes spread all around the world use about 30 branches of nightly releases for testing new packages, verification of patches to existing software, and migration to new platforms and compilers. The nightly releases lead up to, and are the basis of, stable software releases used for data processing worldwide. The ATLAS nightly builds are managed by the fully automated NICOS framework on the computing farm with 44 powerful multiprocessor nodes. The ATN test tool is embedded within the nightly system and provides results shortly after full compilations complete. Other test frameworks are synchronized with NICOS jobs and run larger scale validation jobs using the nightly releases. NICOS web pages dynamically provide information about the progress and results of the builds. For faster feedback, e-mail notifications about nightly releases problems are automatically distributed to the developers responsible.
A search for scalar particles decaying via narrow resonances into two photons in the mass range 65-600 GeV is performed using 20.3 fb(-1) of √s 8 TeV pp collision data collected with the ATLAS ...detector at the Large Hadron Collider. The recently discovered Higgs boson is treated as a background. No significant evidence for an additional signal is observed. The results are presented as limits at the 95% confidence level on the production cross section of a scalar boson times branching ratio into two photons, in a fiducial volume where the reconstruction efficiency is approximately independent of the event topology. The upper limits set extend over a considerably wider mass range than previous searches.
We update our CHEP06 2 presentation on the ATLAS experiment software infrastructure used to build, validate, distribute, and document the ATLAS offline software. The ATLAS collaboration's ...computational resources and software developers are distributed around the globe in about 35 counties. The ATLAS offline code base is currently over 7 million source lines of code in 10,000+ C++ classes organized into about 2,000 packages. More than 400 developers contribute code each month. Since our last report, we have developed a powerful, flexible system to request code versions to be included in software builds, made changes to our software building tools, increased the number of daily builds used to validate significant code changes, improved the tools for distributing the code to our computational sites around the world, and made many advancements in the tools to document the code.
This is the final report of the ATLAS Simulation Optimization Task Force, establishedin June of 2007. This note justifies the selected Geant4 version, physics list, and range cuts to be used by the ...default ATLAS simulation for initial data taking and beyond. The current status of several projects, including detector description, simulation validation, studies of additional Geant4 parameters, and cavern background, are reported.
Organization and management of ATLAS offline software releases Obreshkov, E.; Albrand, S.; Collot, J. ...
Nuclear instruments & methods in physics research. Section A, Accelerators, spectrometers, detectors and associated equipment,
2008, 2008-1-00, Letnik:
584, Številka:
1
Journal Article
Recenzirano
Odprti dostop
ATLAS is one of the largest collaborations ever undertaken in the physical sciences. This paper explains how the software infrastructure is organized to manage collaborative code development by ...around 300 developers with varying degrees of expertise and situated in 30 different countries. ATLAS offline software currently consists of about 2 million source lines of code contained in 6800 C++ classes, organized in more than 1000 packages. We will describe how releases of the offline ATLAS software are built, validated and subsequently deployed to remote sites. Several software management tools have been used, the majority of which are not ATLAS specific; we will show how they have been integrated.
ATLAS Metadata Task Force ATLAS Collaboration; Costanzo, D.; Cranshaw, J. ...
Physical review letters,
04/2007
Journal Article
Recenzirano
Odprti dostop
This document provides an overview of the metadata, which are needed to characterizeATLAS event data at different levels (a complete run, data streams within a run, luminosity blocks within a run, ...individual events).
Object oriented run control for the CEBAF data acquisition system Quarrie, D.R.; Heyes, G.; Jastrzembski, E. ...
IEEE Transactions on Nuclear Science (Institute of Electrical and Electronics Engineers); (United States),
04/1992, Letnik:
39, Številka:
2
Journal Article, Conference Proceeding
Recenzirano
Odprti dostop
The Eiffel object-oriented language has been selected for the design and implementation of the run control portion in the CEBAF (Continuous Electron Beam Accelerator Facility) data acquisition ...system. The OSF/Motif graphical user interface toolkit and DataViews process control system have been incorporated into this framework. A discussion is presented of the evaluation process, the status of the implementation, and the lessons learned, particularly in the use of object-oriented techniques.< >
CODA: a scalable, distributed data acquisition system Watson, W.A.; Chen, J.; Heyes, G. ...
IEEE Transactions on Nuclear Science (Institute of Electrical and Electronics Engineers); (United States),
02/1994, Letnik:
41, Številka:
1
Journal Article, Conference Proceeding
Recenzirano
A new data acquisition system has been designed for physics experiments scheduled to run at CEBAF starting in the summer of 1994. This system runs on Unix workstations connected via ethernet, FDDI, ...or other network hardware to multiple intelligent front end crates/spl minus/VME, CAMAC or FASTBUS. CAMAC crates may either contain intelligent processors, or may be interfaced to VME. The system is modular and scalable, from a single front end crate and one workstation linked by ethernet, to as many as 32 clusters of front end crates ultimately connected via a high speed network to a set of analysis workstations. The system includes an extensible, device independent slow controls package with drivers for CAMAC, VME, and high voltage crates, as well as a link to CEBAF accelerator controls. All distributed processes are managed by standard remote procedure calls propagating change-of-state requests, or reading and writing program variables. Custom components may be easily integrated. The system is portable to any front end processor running the VxWorks real-time kernel, and to most workstations supplying a few standard facilities such as rsh and X-windows, and Motif and socket libraries. Sample implementations exist for 2 Unix workstation families connected via ethernet or FDDI to VME (with interfaces to FASTBUS or CAMAC), and via ethernet to FASTBUS or CAMAC.< >
In order to facilitate access to the large volumes of data (multiple petabytes per year) which will be produced during data taking and Monte Carlo production at ATLAS, work has proceeded on building ...a system of event-level metadata to allow selections of a subset of events to use as input to an analysis. This was included in the ATLAS Computing Model and was first studied and implemented by the Physics Analysis Tools group based on the decisions of the ESD/AOD Task Force. They used tools developed and supported by the CERN IT group and the ATLAS Database group. During 2005 this structure was put through various tests and evaluations. Also, work by physicists on reconstruction and analysis led to an improved understanding of the requirements on the TAG. This report addresses the effect of these new inputs on the previous work with regard to content and the infrastructure needed to support it.
Abstract Background Mitochondrial superoxide radical (O2•¯ ) production increases after cardiac ischemia/reperfusion (IR). Ischemic preconditioning (IPC) preserves mitochondrial function and ...attenuates O2•¯ production, but the mechanism is unknown. Mitochondrial membrane potential (mΔΨ) is known to affect O2•¯ production; mitochondrial depolarization decreases O2•¯ formation. We examined the relationship between O2•¯ production and mΔΨ during IR and IPC. Materials/methods Rat hearts were subjected to Control or IPC. Mitochondria were isolated at end equilibration (End EQ), end ischemia (End I), and end reperfusion (End RP). mΔΨ was measured using a tetraphenylphosphonium electrode. Mitochondrial O2•¯ production was measured by electron paramagnetic resonance using DMPO spin trap. Cytochrome c levels were measured using high-pressure liquid chromatography. Results IPC preserved mΔΨ at End I (−156 ± 5 versus −131 ± 6 mV, P < 0.001) and End RP (−168 ± 2 versus −155 ± 2 mV, P < 0.05). At End RP, IPC attenuated O2•¯ production (2527 ± 221 versus 3523 ± 250 AU/mg protein, P < 0.05). IPC preserved cytochrome c levels (351 ± 14 versus 269 ± 16 picomoles/mg protein, P < 0.05) at End RP, and decreased mitochondrial cristae disruption (10% ± 4% versus 33% ± 7%, P < 0.05) and amorphous density formation (18% ± 4% versus 28% ± 1%, P < 0.05). Conclusion We conclude that IPC preserves mΔΨ, possibly by limiting disruption of mitochondrial inner membrane. IPC also decreases mitochondrial O2•¯ production and preserves mitochondrial ultrastructure after IR. While it was previously held that slight decreases in mΔΨ decrease O2•¯ production, our results indicate that preservation of mΔΨ is associated with decreased O2•¯ and preservation of cardiac function in IPC. These findings indicate that the mechanism of IPC may not involve mΔΨ depolarization, but rather preservation of mitochondrial electrochemical potential.
PDF
