The Run Control and Monitoring System of the CMS Experiment Presented by Andrea Petrucci INFN, Laboratori Nazionali di Legnaro, Italy On behalf of the DAQ Group of CMS collaboration ACAT 2007, April 2007, Amsterdam, Netherlands

2 Outline 2ACAT April 2007, AmsterdamAndrea Petrucci - LNL-INFN Run Control and Monitor System :  Architecture Logical Layer Services Components Technologies  At the Magnet Test and Cosmic Challenge (MTCC) Control structure Operation Components Results  GRICC Project

3 What is CMS? 3ACAT April 2007, AmsterdamAndrea Petrucci - LNL-INFN The Compact Muon Solenoid (CMS) experiment is one of two large general-purpose particle physics detectors being built on the proton- proton Large Hadron Collider (LHC) at CERN in Switzerland. to explore physics at the TeV scale to discover the Higgs boson to look for evidence of physics beyond the standard model to be able to study aspects of heavy ion collisions The main goals of the experiment are:

4 Run Control and Monitor System 4ACAT April 2007, AmsterdamAndrea Petrucci - LNL-INFN The Run Control and Monitor System (RCMS) is responsible for controlling and monitoring the CMS experiment during the data taking. RCMS views the experiment as a set of partition, where a partition is a grouping of entities that can be operated independently. Main operations are configuration, monitoring, error handling, logging and synchronization with other subsystems.

55ACAT April 2007, AmsterdamAndrea Petrucci - LNL-INFN Baseline DAQ Configuration 512 inputs 2024 outputs CMS Data Acquisition Control and Monitor requirements O(10 4 ) distributed Objects to – control – configure – monitor On-line diagnostics Interactive system

6 RCMS is integrated in the CMS On-line system : It controls the “DAQ component” –Data transport –Event processing It monitors the “Detector Control System” DCS – manages the slow controls of the whole experiment. 6ACAT April 2007, AmsterdamAndrea Petrucci - LNL-INFN Run Control and Monitor System The SOAP protocol and the Web Services have been adopted as the main means for communication. The online process environment is XDAQ, a C++ framework for a distributed Data Acquisition System.

7 RCMS Logical Structure 7ACAT April 2007, AmsterdamAndrea Petrucci - LNL-INFN A Session is the allocation of the hardware and software of a CMS partition needed to perform data- taking. Multiple Sessions may coexist and operate concurrently. Each Session is associated with a Top Function Manager, that coordinates all the actions. Top Sub-Detector DAQ Resources Services

8 –SECURITY SERVICE login and user account management; –RESOURCE SERVICE (RS) information about DAQ resources and partitions; –INFORMATION AND MONITOR SERVICE (IMS) Collects messages and monitor data; distributes them to the subscribers; –JOB CONTROL Starts, monitors and stops the software elements of RCMS, including the DAQ components; RCMS Services 8ACAT April 2007, AmsterdamAndrea Petrucci - LNL-INFN

9 Function Manager 9ACAT April 2007, AmsterdamAndrea Petrucci - LNL-INFN Input Handler : It handles all the input events of the FM (GUIs or other FMs, errors, states, logs and monitor messages) Event Processor: It handles all the incoming message and decide where to send them. It has processing capability Finite State Machine (FSM): The behavior of the FM is driven by a FSM. Resource Proxy: It handles all the outgoing connections with the resources. The purpose of a Function Manager (FM) is to control a set of resources. Input Handler Event Processor FSM Engine Resource Proxy Function Manager Resources State Flow Error Flow Monitor Flow Control Flow Customizable

10 Resource Service 10ACAT April 2007, AmsterdamAndrea Petrucci - LNL-INFN RS Manager tool RS DB RS API DAQ Configurator The Resource Service (RS) stores the process configuration of the On-line System. features Flexible data store Java API Configuration documents can be built on the fly from relational schema Versioning system Oracle and MySQL Implementation

11 Log Collector 11ACAT April 2007, AmsterdamAndrea Petrucci - LNL-INFN Collects log information from log4j compliant applications (i.e. on-line process). … Publish Subscriber System Display System Storage System Log Collector Relational DB Oracle,MySQL Message System Access via JDBC Access via TCP RCMS applications and XDAQ applications Send log information directly to a Display System (Chainsaw). Stores log information in a database and visualizes them (LogDBViewer). Distributes/publishes log information through a message system (Java Message Service).

12 RCMS main components 12ACAT April 2007, AmsterdamAndrea Petrucci - LNL-INFN Log Collector WebApp Chainsaw Log Viewer JobControl Process Control Firefox JSP/Ajax GUI Config data Conditions data Process Config Log Messages Commands Notifications RCMS RS Manager Manager/Editor DAQ Configurator Configuration Function Manager Framework RS API RunInfo API Hwcfg API RS DB GCK DB RunInfo DB Log DB Hwcfg DB User Interface

13 RCMS Technologies 13ACAT April 2007, AmsterdamAndrea Petrucci - LNL-INFN Technologies and tools: Web Applications,Java Servlets (Apache Tomcat) WebService (Axis, WSDL, SOAP) Web Tecnologies (Ajax,JSP) Databases –Oracle –MySQL ArchitectureImplementation Resource Service (RS)Resource Service Information and Monitor Service (IMS)LogCollector SubSystem Controllers (FMs)RCMS Framework Top Function ManagerRCMS Framework GUIsDefault JSP GUI - RCMS Framework JobControlXDAQ Framework

14 Magnet Test and Cosmic Challenge 14ACAT April 2007, AmsterdamAndrea Petrucci - LNL-INFN The main goals of the Cosmic Challenge were: Test Muon alignment systems. Commission the several sub-detectors (Drift Tubes - DT, Hadron Calorimeter – HCAL, Tracker, etc.) and Cosmic Trigger. demonstrate cosmic ray reconstruction with multiple sub-detectors. The Magnet Test and Cosmic Challenge (MTCC) is a milestone of the CMS experiment, it completes the commissioning of the magnet system (coil & yoke) before its lowering into the cavern. Scale MTCC versus CMS Data Sources:20 out of 600 3% Filter Nodes: 14 out of % Trigger rate: 100 Hz out of 100 kHz 0.1% Event size: 200 kB out of 1 MB20% Scale MTCC versus CMS Data Sources:20 out of 600 3% Filter Nodes: 14 out of % Trigger rate: 100 Hz out of 100 kHz 0.1% Event size: 200 kB out of 1 MB20%

15 FMs Control Structure at MTCC I & II 15ACAT April 2007, AmsterdamAndrea Petrucci - LNL-INFN Web Browser (GUI) Level 0 FM Level 1 FM Level 2 FM User interaction with Web Browser connected to Level 0 FM. Level 0 FM is entry point to Run Control System. Level 2 FMs are sub-system specific custom implementations. Level 1 FM interface to the Level 0 FM and have to implement a standard set of inputs and states. TOP LTC CSCDAQ RPCDT TRK ECAL HCAL FBRBFF Resources FECFED Resources are on-line system components

16 RCMS at MTCC I & II ACAT April 2007, AmsterdamAndrea Petrucci - LNL-INFN TopDAQ LTC HCAL ECAL DT CSC RPC TRK RCMS Operation Scenario –Sub-system function managers were written using the RCMS software –The run configuration was communicated via a global configuration key –The Run Info DB was used to store end-of- run summary information and status information about the run. It also contained the schema to generate Run Numbers and Run Sequence Numbers. N Sub-Detector controlled8 Function Managers used14 Online resources controlled~ 100

17 RCMS Components at MTCC I & II 17ACAT April 2007, AmsterdamAndrea Petrucci - LNL-INFN global key local key configuration logmessage TopDAQ LTC-Trg HCAL ECAL DT CSC RPC Global Configuration Keys RPC RS RPC RS LTC-Trg RS LTC-Trg RS EMU RS EMU RS DT RS DT RS DAQ RS DAQ RS global key ECAL RS ECAL RS HCAL RS HCAL RS TRK RS TRK RS LOG DB Top RS Top RS Collector Configuration A Global configuration Key identified a sub- system configuration. The configuration local to the sub-system were decouple from each other and the top configuration.

18 MTCC Data taking 18ACAT April 2007, AmsterdamAndrea Petrucci - LNL-INFN

19 MTCC result 19ACAT April 2007, AmsterdamAndrea Petrucci - LNL-INFN RCMS software was stable. Separation of Subsystem installations worked well. Recorded ~ 160 M events on a period of one month

20 RCMS and GRIDCC 20ACAT April 2007, AmsterdamAndrea Petrucci - LNL-INFN It is a project of 3-years and started in September 2004 Web site: What is GRIDCC ? The Grid enabled Remote Instrumentation with Distributed Control and Computation (GRIDCC) is a project funded by the European community, aimed to provide access to and control of distributed complex instrumentation. The CMS RCMS is one of the main applications for the GRIDCC project. The RCMS software is the core of the Instrument Element of the GRIDCC.

21 ACAT April 2007, AmsterdamAndrea Petrucci - LNL-INFN Thank you for your attention. Any Questions?