Representation and usage of knowledge for initialization of accelerator control equipment

A knowledge based application, called SETUP, to initialize and diagnose the CERN/PS accelerators' control equipment is described. The object model and the general features of control algorithms are presented, together with their relation to the knowledge description of the setting up of the system. The different ways of the integration of the SETUP in the control system are outlined

The PHENIX Experiment at RHIC

The physics emphases of the PHENIX collaboration and the design and current status of the PHENIX detector are discussed. The plan of the collaboration for making the most effective use of the available luminosity in the first years of RHIC operation is also presented.Comment: 5 pages, 1 figure. Further details of the PHENIX physics program available at http://www.rhic.bnl.gov/phenix

The Supervisor of the ATLAS Detector Control System

The design and the implementation of the supervisor system of the ATLAS Detector Controls are described. The interaction with the Data Acquisition system, which is needed for the coherent operation of the experiment, and in particular the use of Finite State Machine tools, is discussed

Design and Implementation of the ATLAS Detector Control System

The overall dimensions of the ATLAS experiment and its harsh environment, due to radiation and magnetic field, represent new challenges for the implementation of the Detector Control System. It supervises all hardware of the ATLAS detector, monitors the infrastructure of the experiment, and provides information exchange with the LHC accelerator. The system must allow for the operation of the different ATLAS sub-detectors in stand-alone mode, as required for calibration and debugging, as well as the coherent and integrated operation of all sub-detectors for physics data taking. For this reason, the Detector Control System is logically arranged to map the hierarchical organization of the ATLAS detector. Special requirements are placed onto the ATLAS Detector Control System because of the large number of distributed I/O channels and of the inaccessibility of the equipment during operation. Standardization is a crucial issue for the design and implementation of the control system because of the large variety of equipment and the high number of different groups involved working all around the world. The functions of the two main components of the DCS, namely the distributed Back-End software system, which will be based on a commercial SCADA package, and the sub-detector's Front-End systems, with extensive use of the CAN fieldbus, are explained. The standard readout chain of the Detector Control System, which comprises both Back-End software and general-purpose Front-End equipment, is described and its performance is discussed

Role Based Access Control System in the ATLAS Experiment

The complexity of the ATLAS experiment motivated the deployment of an integrated Access Control System in order to guarantee safe and optimal access for a large number of users to the various software and hardware resources. Such an integrated system was foreseen since the design of the infrastructure and is now central to the operations model. In order to cope with the ever growing needs of restricting access to all resources used within the experiment, the Roles Based Access Control (RBAC) previously developed has been extended and improved. The paper starts with a short presentation of the RBAC design, implementation and the changes made to the system to allow the management and usage of roles to control access to the vast and diverse set of resources. The paper continues with a detailed description of the integration across all areas of the system: local Linux and Windows nodes in the ATLAS Control Network (ATCN), the Linux application gateways offering remote access inside ATCN, the Windows Terminal Servers offering remote access to the Detector Control System (DCS) and to Windows machines inside ATCN, the PVSS SCADA software, the distributed file system, the central network attached file system. The RBAC implementation uses a directory service based on Lightweight Directory Access Protocol to store the users (~3000), roles (~320), groups (~80) and access policies. The information is kept in sync with various other databas es and directory services: human resources, central CERN IT, CERN Active Directory and the Access Control Database used by DCS

Role Based Access Control system in the ATLAS experiment

The complexity of the ATLAS experiment motivated the deployment of an integrated Access Control System in order to guarantee safe and optimal access for a large number of users to the various software and hardware resources. Such an integrated system was foreseen since the design of the infrastructure and is now central to the operations model. In order to cope with the ever growing needs of restricting access to all resources used within the experiment, the Roles Based Access Control (RBAC) previously developed has been extended and improved. The paper starts with a short presentation of the RBAC design, implementation and the changes made to the system to allow the management and usage of roles to control access to the vast and diverse set of resources. The paper continues with a detailed description of the integration across all areas of the system: local Linux and Windows nodes in the ATLAS Control Network (ATCN), the Linux application gateways offering remote access inside ATCN, the Windows Terminal Servers offering remote access to the Detector Control System (DCS) and to Windows machines inside ATCN, the PVSS SCADA software, the distributed file system, the central network attached file system. The RBAC implementation uses a directory service based on Lightweight Directory Access Protocol to store the users (~3000), roles (~320), groups (~80) and access policies. The information is kept in sync with various other databas es and directory services: human resources, central CERN IT, CERN Active Directory and the Access Control Database used by DCS