Run Control Prototype Status M. Gulmini, M. Gaetano, N. Toniolo, S. Ventura, L. Zangrando

Luigi Zangrando, Cern, 16/4/20021

CMS

Run Control Prototype Status

M. Gulmini, M. Gaetano, N. Toniolo, S. Ventura,

L. Zangrando

INFN – Laboratori Nazionali di Legnaro


CMS

RCMS: definitionRCMS: definition

The The RRun un CControl ontrol MMonitor onitor SSystem is defined as the software required to:ystem is defined as the software required to:• configure and set the CMS apparatus ( partitions or whole system)configure and set the CMS apparatus ( partitions or whole system)

• control and synchronize operation of the separate components control and synchronize operation of the separate components

• monitor the separate componentsmonitor the separate components

• handle errors and information messageshandle errors and information messages

• log continuously the current state of the experimentlog continuously the current state of the experiment

• provide a user interface for both control and monitorprovide a user interface for both control and monitor

RCMSInternetIntranet

InternetIntranet

UI

UI

UI

The RCMS architecture enables the users to access and control the experiment from any part of the world


CMS

RCMS contextRCMS context

Session Manager

UIUI

UI

Services Connection

ServicesServicesServices

EVBCtrl

CSCtrl

TRGCtrl

DCSCtrl

EVFCtrl

FED Builder

CS Sub- System

GlblMuCal

DCS Sub- System

EVB Sub-System TRG Sub-System EVF Sub-System

RCMS

RU Builder


CMS

RCMS: block diagram RCMS: block diagram • SECURITY SERVICE (SS)

– It provides login and authentication procedures to RCMS enabling data encryption when needed

• RESOURCE SERVICE (RS)– It manages the elements of the DAQ system:

• configuration of the components• Session and Partition mngm

• Information and Monitor System (IMS)– It collects all the information originated from the sub-

systems. Information is cataloged as:• Messages:

– Errors– Generic– Resource Status Change

• Monitor

• JOB CONTROL– It starts, monitor and kill the software infrastructure

of the RCMS

• PROBLEM SOLVER– It uses the information provides by IMS to catch

severe malfunctions of the apparatus and try to fix them

SecurityService

ResourceService

Info&MonService

Job Ctrl

ProblemSolver

Sub-SystemController

Ser

vice

s C

onne

ctio

n

Session Manager

RCMS

UIUI

UI

UserDB

ConfDB

LogDB

RunBkkpng


CMS

RCMS prototype statusRCMS prototype status

InternetXML -http

InternetXML -http

Sub-SystemXDAQ Resources

SecurityService

ResourceService

Info&MonService

Job Ctrl

ProblemSolver

FunctionManager

XM

L ov

er h

ttp

prot

ocol

s

Session Manager

RCMS

UIUIGUI

UserDB

ConfDB

LogDB

RunBkkpng

UIUIGUI Servlet ContainerApache TomCat XML:DB +

mySQL

FSM

XDAQ Adapter

FSM


CMS

Tools: XML as communication protocolTools: XML as communication protocol

Servlet container (TOMCAT)

Java Servlet

Resource ServiceJava client

XML XML:DB

REL DBJava Objs

XML Parser(Castor)

XML Parser

(Castor)

C++ client

XML Parser

(Castor)

Java client

XML Parser

(Castor)

http

XML


CMS

Information and Monitor Service (IMS)Information and Monitor Service (IMS)

The IMS collects all the information comming from any DAQ resources or RCMS internal components and stores them in the logDB database.

The informations are cataloged in:

• Messages Messages (error, generic, resource status change)(error, generic, resource status change)

• MonitorMonitorSMSM

FMFM FMFM

error msgerror msg

status change msgstatus change msgIMSIMS


CMS

IMS prototype:IMS prototype:

ResourceStatus Change

Error StatisticsError Statistics

MessageLogger (DB)

State logger

Monitor - HistoryDB

Mes

sage

F

ilter

ing

and

Dis

patc

her

Monitor Info

SystemState Display

Error Statistics Alarm Display

MonitorSystems

Clie

nt S

ubsc

riber Messages (Error, Warning

Generic)

IMS

DBDB

FilterFilter

EngineEngine

XPath XPath basedbased

subscriber 1

subscriber nJAXM

XML messageSoap

Message


CMS

IMS StatusIMS Status

• Proposal for the IMS protocol definition (XML schema)

• Tools and technologies:– JAXM for SOAP to XML message– native XML DB (eXist XML:DB +MySQL)– Xalan (Apache) for XPath in the filter engine– JMS (Java Message Service) as complete tool for IMS

• It fits our requirements• Fast and complete • Java bounded

• Full IMS prototype in progress


CMS

GUI GUI

• Graphical User Interface– Java Based– Run Control Panel

• Simple start/stop commands – Monitors Panel

• Get system status• Performance and statistics

– Create/join Sessions• Java Wizard based• Fully based on the Resource Service DB

• Main efforts on handling sessions, partitions, etc. • Run Control and monitor panels based on the running Legnaro Muon Data

Acquisition


CMS

GUI exampleGUI example

Create/join Sessions GUI: GUI:1.1. Types definition (only when the DB is created)Types definition (only when the DB is created)

• Applications typeApplications type• Software packagesSoftware packages• Device’s templatesDevice’s templates• DataTypesDataTypes• SubSystems typeSubSystems type• ......

2.2. Partition creationPartition creation

3.3. Session creationSession creation


CMS

Some GUI panelsSome GUI panels

Applications type definitionApplications type definition SubSystems type definitionSubSystems type definition


CMS

Software panelsSoftware panels

New SoftwareNew Software Software parametersSoftware parameters


CMS

Partition and Session panels (I)Partition and Session panels (I)

New PartitionNew Partition

Partition configuration:Partition configuration:

1.1. number of applicationsnumber of applications

2.2. software packagesoftware package


CMS

Partition and Session panels (II)Partition and Session panels (II)

New SessionNew Sessionapplication mappingapplication mapping


CMS

RCMS prototype statusRCMS prototype status

• Resource Service with Security Service. Interactive GUI to handle run sessions, partitions, etc. Easy to customize according to the application needs (e.g. Test beams, simple test environment, etc.)

• Session Manager

• Function Manager

• XDaq adapter

• Finite State Machine

• First integration and tests with xdaq nodes

• IMS

• Design and technological investigations

• Implementation in progress


CMS

PlansPlans• Continue integration in small daq sysytems (e.g. Muon data acquisition, etc.). Functionality tests

• Run Control and Monitors panel to be completed

• First implementation of the IMS (Information and Monitor Service)

• XML:DB product investigations:– Apache Xindice– Oracle 9i vers. 2 (May)

• GUI product investigations:– Flash Mx (embedded Flash code into Java)

• Move Resource Service protocol (XML) to SOAP

• Performances tests on a 32 machines cluster

• Packaging, software distribution, documentation

• Release 0.1

Documents

Run Control Prototype Status M. Gulmini, M. Gaetano, N. Toniolo, S. Ventura, L. Zangrando