NTUA-CMS I. , . , . , . - - PowerPoint PPT Presentation

NTUA-CMS

• I. Παπακριβόπουλος, Γ. Μπάκας, Ε. Ανδρεαδάκη,

Κ. Κουσουρής, Γ. Τσιπολίτης

CMS Central DCS Team

Development and maintenance of the Detector Control System (DCS) responsible for controlling (Finite State Machine model) and monitoring (sensors, crates, etc.) the detector. Tools:

• WinCC_OA (Framework by Siemens)
• JCOP (Joint Controls Project) Framework (CERN EN department)
• Detector custom framework “CMS framework” (CMS Central DCS Team)

1/11/2017

2

CMS Central DCS Team

Each subdetector has its own system (DCS), developed by the subdetector DCS team which is finally integrated into the central system. This implies that every subdetector:

• Has a system with a unique structure
• Monitors subdetector specific hardware
• Performs subdetector specific commands and actions

The role of the Central DCS team is to provide:

• General rules and guidelines (ease of integration)
• Tools for development to the subdetectors
• Monitoring CMS generic hardware (ELMBs, Wiener crates etc.)
• General support regarding WinCC_OA to CMS
• Other services like database expertise etc.
• On call service during detector running periods

1/11/2017

3

NTUA in CMS central DCS

Our involvement in the CMS DCS team includes:

• Ongoing training on the various framework components, the tools, and the different system

structures (central and subdetector) aiming to become DCS experts assisting in the on call service of the team.

• Participation in projects of the CMS DCS team including maintenance, development and

improvement of the CMS framework.

1/11/2017 ΤΣΙΠΟΛΙΤΗΣ ΓΕΩΡΓΙΟΣ

4

Projects

• Improvement of the monitoring component for the Wiener VME crates and the ELMBs for the CMS
• Development of a tool cross referencing the information of a project and the one contained in the

backup database.

• Script that checks for publications in the LHC network (DIP publications) and subscribes to them
• Development of the DCS for the test beams on the HGCAL prototypes (in progress)

1/11/2017 ΤΣΙΠΟΛΙΤΗΣ ΓΕΩΡΓΙΟΣ

5

Wiener – ELMB component

Originally: A single component (CMSfwRackElmb) responsible for monitoring both ELMBs and Wiener crates. Problem: Under some circumstances (e.g. addition of new hardware), the component needs to be reinstalled. This is very laborious for a single component making it more prone to failure. Solution: Creation of two separate components, one for each type of hardware. However during development, many common actions were identified. Therefore, we additionally created one “parent” component handling all the common functionality.

1/11/2017 ΤΣΙΠΟΛΙΤΗΣ ΓΕΩΡΓΙΟΣ

6

Wiener – ELMB component

1/11/2017 ΤΣΙΠΟΛΙΤΗΣ ΓΕΩΡΓΙΟΣ

7

Parent Component Two new Components

Wiener – ELMB component

1/11/2017

8

Easier future development of components for monitoring other hardware, due to existing functionalities in the “parent” component.

Projects

• Improvement of the monitoring component for the Wiener VME crates and the ELMBs for the CMS
• Development of a tool cross referencing the information of a project and the one contained in the

backup database.

• Script that checks for publications in the LHC network (DIP publications) and subscribes to them
• Development of the DCS for the test beams on the HGCAL prototypes (in progress)

1/11/2017 ΤΣΙΠΟΛΙΤΗΣ ΓΕΩΡΓΙΟΣ

9

CMSfwInstallUtils

WinCC_OA and JCOP enable the connection between a project and a database. CMS uses this functionality to store information regarding the structure of the monitoring project in a database. This allows the recreation of the whole DCS or part of it, in case of failure in point 5. We created a component that cross checks between the information in the system and the database, a tool necessary when manipulating a system containing massive amounts of data. This tool is integrated in the already existing CMSfwInstallUtils component.

1/11/2017

10

CMSfwInstallUtils

• This is the main screen of

the CMSfwInstallUtils component

1/11/2017 ΤΣΙΠΟΛΙΤΗΣ ΓΕΩΡΓΙΟΣ

11

Configuration database check

• The subcomponent we developed,

checks for inconsistencies between the project and the database.

1/11/2017 ΤΣΙΠΟΛΙΤΗΣ ΓΕΩΡΓΙΟΣ

12

Configuration database check

• The subcomponent we developed,

checks for inconsistencies between the project and the database(red cells).

1/11/2017 ΤΣΙΠΟΛΙΤΗΣ ΓΕΩΡΓΙΟΣ

13

Additional datapoint attributes

• After the first check, the subcomponent

enables the user to check for further inconsistences concerning other datapoint attributes (address, archiving, alerts).

• The component also produces a table

containing results, assisting the user to identify the problematic datapoints if any.

1/11/2017

14

Configuration database check

• Additionally it provides the option of

demonstrating only the inconsistent datapoints.

1/11/2017 ΤΣΙΠΟΛΙΤΗΣ ΓΕΩΡΓΙΟΣ

15

Projects

• Improvement of the monitoring component for the Wiener VME crates and the ELMBs for the CMS
• Development of a tool cross referencing the information of a project and the one contained in the

backup database.

• Script that checks for publications in the LHC network (DIP publications) and subscribes to them
• Development of the DCS for the test beams on the HGCAL prototypes (in progress)

1/11/2017

16

Data Interchange Protocol (DIP)

• Communication Protocol, developed at CERN for data exchanging between different systems

(e.g. LHC and CMS).

• The protocol requires a DIP Name Server which is the “middle man” between the systems.
• Each system can Publish data or Subscribe to data published in the server.

1/11/2017

17

LHC SERVER CMS

Publish Publish Subscribe Subscribe

Data Interchange Protocol (DIP)

The structure or names of the data in the server can be changed by the publisher without the possibility of notifying the subscriber. As a result, the subscriber is subscribed to something that doesn’t exist resulting in notifications about errors. To resolve this problem, a script was created which queries the server every 24 hours listing the published data. If there is an inconsistency between the published data and the data that a project is subscribed to, then the project re-subscribes to the new data.

1/11/2017

18

Projects

• Improvement of the monitoring component for the Wiener VME crates and the ELMBs for the CMS
• Development of a tool cross referencing the information of a project and the one contained in the

backup database.

• Script that checks for publications in the LHC network (DIP publications) and subscribes to them
• Development of the DCS for the test beams on the HGCAL prototypes (in progress)

1/11/2017

19

High Granularity CALorimeter (HGCAL)

• HGCAL is an upgrade for the end cap part of the Calorimeters (preshower, ECAL, HCAL)
• The goal is to develop a DCS for the test beams (May - July 2017) that will be performed on the

HGCAL prototype

1/11/2017

20