cms trigger supervisor framework

21
Compact Muon Solenoid Thomas Themel TU Wien June 2009 Institut für Hochenergiephysik, ÖAW CMS Trigger Supervisor Framework Ildefons Magrans de Abril Marc Magrans de Abril Gian Pieo Di Giovanni Philipp Glaser Tobias Noebauer Alexander Winkler Philipp Wagner Jose Melo Franz Mittermayr Christian Hartl

Upload: romney

Post on 01-Feb-2016

39 views

Category:

Documents


0 download

DESCRIPTION

CMS Trigger Supervisor Framework. Ildefons Magrans de Abril Marc Magrans de Abril Gian Pieo Di Giovanni Philipp Glaser Tobias Noebauer Alexander Winkler Philipp Wagner Jose Melo Franz Mittermayr Christian Hartl. CMS and the need for the TS. - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: CMS Trigger Supervisor Framework

Compact Muon Solenoid

Thomas ThemelTU WienJune 2009

Institut für Hochenergiephysik, ÖAW

CMS Trigger Supervisor Framework

Ildefons Magrans de AbrilMarc Magrans de AbrilGian Pieo Di GiovanniPhilipp GlaserTobias NoebauerAlexander WinklerPhilipp WagnerJose MeloFranz MittermayrChristian Hartl

Page 2: CMS Trigger Supervisor Framework

2

CMS and the need for the TS

• Like the entire CMS experiment, the L1 trigger is a very complex system.

“64 crates, O(103) boards with an average of 15 MB of downloadable firmware and O(102) configurable registers per board, 8 independent DAQ partitions, and O(103) links that must be periodically tested in order to assure the correct connection and synchronization”

“27 research institutes from Europe, Asia and America”

Page 3: CMS Trigger Supervisor Framework

3

CSCTFCSCTF

The Trigger Supervisor

GMT GT/TCS GCTDTTFRPC

DT

CSC

CSCTF

1

HCAL

RCT

ECAL

Trigger Supervisor

RCMS

Page 4: CMS Trigger Supervisor Framework

4

Goals

• Present a unified interface to the entire L1 trigger system to RCMS* to allow– Configuration– Monitoring– Interconnection Tests– Logging– Error Management

* Run Control and Monitoring System

Page 5: CMS Trigger Supervisor Framework

5

Other constraints

• Distributed system• Disconnected development of

subsystems• Different software environments

– RCMS in Java– Subsystem applications in C++

• Partially based on CMS-developed XDAQ framework

Page 6: CMS Trigger Supervisor Framework

6

It's almost as bad as the internet!

• Distributed design based on web services• What is distributed?

– Subsystem application development– Running the subsystems

• What is centralized?– Development repository (TriDAS CVS)– Build system– All parts of the system based on TS framework– Configuration database

Page 7: CMS Trigger Supervisor Framework

7

The Trigger Supervisor Cell

• The building blocks of the TS system are called cells.

• A central cell coordinates global operations.

• Each subsystem crate runs its own cell.• Cells support defined protocol for

standard operations.• Additionally, cells are extensible to

provide subsystem-specific features.

Page 8: CMS Trigger Supervisor Framework

8

Architecture

11

TS Cell

TS CellTS CellTS Cell …

Subsystem Cell GUI

Central Cell GUI

Hardware access

customized by every subsystem

SOAPCommon configuration DB

SOAP

0..nController side

0..n

1

1

1

1 1

1 111

0..n

RCMSRCMS

OSWI OSWI OSWI

Tree like structure where the central node and the leafs are based on a common “control cell” implemented with XDAQ

Page 9: CMS Trigger Supervisor Framework

9

The TS framework

• C++ (server-side)• Based on XDAQ

– Runtime– Web services support– Build system– Logging– Parts of the monitoring– Database access

Page 10: CMS Trigger Supervisor Framework

10

Adding functionality to TS cells

• TS framework provides “empty” cell• Main entry points for extension:

– Commands• Function calls

– Operations• Stateful interactions

– Panels• Web GUI

– DataSources• Monitoring

Page 11: CMS Trigger Supervisor Framework

11

Commands

• Defining commands yields– A generic GUI

– A SOAP interface for remote calls

Page 12: CMS Trigger Supervisor Framework

12

Operations

• Operations are based on finite state machines

Page 13: CMS Trigger Supervisor Framework

13

Operations 2

• Implicit GUI/remote call support• Transitions work like commands

Page 14: CMS Trigger Supervisor Framework

14

Panels

• Ajaxell, an AJAX GUI library– Client side based on Dojo toolkit– Allows much nicer web GUIs than older

HTTP/CGI paradigm– Prime example: L1 TM Editor

Page 15: CMS Trigger Supervisor Framework

15

Panels 2

Page 16: CMS Trigger Supervisor Framework

16

Data Sources

• A DataSource defines a set of variables for monitoring, accessible over a standard interface.

• Implicitly supports Cell GUI, central collection and storage in a database through XMAS*.

*XDAQ Monitoring and Alarming Service

Page 17: CMS Trigger Supervisor Framework

17

Data Sources 2

Page 18: CMS Trigger Supervisor Framework

18

Communication with other subsystems

• Since we can create so many nice SOAP interfaces, we also want to call them

• Also need to interact with XDAQ services for database access etc

• TS framework provides varisous “CellXhannel” implementations to simplify this– CellXhannelCell to call other TS cells– CellXhannelTStore for DB access

Page 19: CMS Trigger Supervisor Framework

19

Role of the Central Cell

Page 20: CMS Trigger Supervisor Framework

20

References and Documentation

Trigger Supervisor TWiki page: https://twiki.cern.ch/twiki/bin/view/CMS/TriggerSupervisor

• Concepts & Design:

– The CMS Trigger Su pervisor: Control and Hardware Monitoring System of the CMS Level-1 Trigger at CERN, PhD Thesis, Universitat Autònoma de Barcelona, I. Magrans

– Concept of the CMS Trigger Supervisor, CMS NOTE 2005/011, Ildefons Magrans, Joao Varela, Claudia Wulz

• Code level information

– User's Guide TS v.1.6

CV S:

http://isscvs.cern.ch/cgi-bin/cvsweb.cgi/TriDAS/?cvsroot=tridas

Page 21: CMS Trigger Supervisor Framework

21

Class Diagram

Subsystem

TS

XDAQ