Abstract

The ATLAS experiment is one of the experiments at the Large HadronCollider, constructed to study elementary particle interactions incollisions of high-energy proton beams. The individual detectorcomponents as well as the common experimental infrastructure aresupervised by the Detector Control System (DCS). The DCS enablesequipment supervision using operator commands, reads, processes andarchives the operational parameters of the detector, allows for errorrecognition and handling, manages the communication with externalcontrol systems, and provides a synchronization mechanism with thephysics data acquisition system. Given the enormous size andcomplexity of ATLAS, special emphasis was put on the use ofstandardized hardware and software components enabling efficientdevelopment and long-term maintainability of the DCS over the lifetimeof the experiment. Currently, the DCS is being used successfullyduring the experiment commissioning phase.

Highlights

  • ATLAS is a general purpose High Energy Physics (HEP) experiment, scheduled to start data taking in 2008 at the Large Hadron Collider (LHC) at CERN, Geneva, Switzerland

  • This paper focuses on the Detector Control System (DCS) architecture, common hardware components and standards, the design and implementation of the DCS back-end software, as well as operational aspects

  • The design and implementation of the ATLAS DCS is based on 4 building blocks:

Read more

Summary

Introduction

ATLAS is a general purpose High Energy Physics (HEP) experiment, scheduled to start data taking in 2008 at the Large Hadron Collider (LHC) at CERN, Geneva, Switzerland. Within JCOP, standards for the use of DCS hardware were established and a commercial controls software product has been selected to serve as the basis for all DCS applications. This software package was substantially extended by a comprehensive framework of software components and implementation policies. This paper focuses on the DCS architecture, common hardware components and standards, the design and implementation of the DCS back-end software, as well as operational aspects.

Requirements
ATLAS operation model
System architecture
Hardware components
64 Channel
ELMB Hardware
ELMB software
Standardized commercial systems
DCS Control Station PC
Software components
JCOP Framework
CANopen OPC server
Object persistency and user interfaces
Access control
Configuration database
Conditions database
Data visualization
Read-Out chain
Operations layer
Secondary module with two possibilities:
Mode selection Allows toggling between two modes:
Subsystem control
Findings
Conclusions
Full Text
Paper version not known

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 call

Disclaimer: 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.