dqm for the rpc subdetector m. maggi and p. paolucci

DQM for the RPC subdetector

M. Maggi and P. Paolucci

DQM workshop - 28 feb 072


Outlook

RPC DQM requirementsevent Data DQM – what we have done and learned during the MTCCwe need more “sophisticated” DQM tools to access online database (non event data)guidelines and open issuesDQM group compositionconclusions



RPC DQM requirements IDQM has to monitor the RPC detector/trigger behavior

and measure and summarize their performances:Online monitoring in FF:

pre-scaled subset of LV1 muon events (rate ?)delay is 0 ? CMS CPUs (how many ?)

Online monitoring in event consumer: pre-scaled subset of LV1 muon events (rate ?)Full use of DCS and XDAQ data via DBRPC CPUs (to design)delay ? seconds ?



RPC DQM requirements IIQuasi-online:

LV1 muon eventsDCS and XDAQ access via Condition DBRPC CPUsdelay of minutes ?

Offline monitoring:for RPC experts to have a full analysisUsing full events and reconstruction toolsusing DBsCMS CPusdelay ? hours ?



Event Data monitoring STATUS I

DQM-analysis packages developed for RPC in CMSSW and test during the MTCC:

EventFilter/RPCRawToDigi (Segoni - Maggi): It drives the raw data unpacking and produces the RPCDigi collection committed to the event.DQM/RPCMonitorModule (Segoni – Maggi): it carries out data integrity check and basic detector functioning tasks

POOLSource

Raw Data Digi

UnpackerDAQ

Clusters/RecHits

Local Muon Reconstruction RPCMonitorDigi

RPCMonitorModule

Event



Event Data monitoring STATUS II DQM/RPCMonitorDigi: Uses the digi produced by the

unpacker (i.e. for each h-partition the collection strip with signal and the BX ) to perform chamber performance checks:

BXN # of digi Occupancy Cluster multiplicity Cluster size

Sync: Specific trigger studies

Chamber efficiency is produced by extrapolating DT segments to the RPC mounted on the same DT chamber and looking for matching hits



Guidelines answersYES, we need history/trendig plots (efficiency, occupancy, cluster size…)YES, we need correlation trendsYES, we need tools to extract complex info from condition DB and repositoryYES, we are using IGUANA to present DQM resultsMORE, we have to work on how make histo/result persistentMORE, we developed a first prototype of a synoptic view YES, we have a clear hierarchical view of the plotsNO, automatic analysis procedures, for the moment YES, we can converge on a run quality flags but we have to work on



RPC synoptic view

We are working onto have a fullsynoptic view of our system with interactivefeatures, alarm, warning and error



Do we need .. More .. Tools ? YES

For RPC it is CRUCIAL to correlate event data DQM info with PVSS and XDAQ non event data:

Chamber efficiency .vs. Noise (XDAQ) Chamber efficiency .vs. Current (PVSS) Noise (XDAQ) .vs. Temperature (PVSS) Cluster size .vs Temperature (PVSS) …………………………………………..

To let understand the behavior of the RPC system we need: few summary plots for the DQM shifter (online) more plots for RPC shifter (quasi-online) a complete way to analyze data for the RPC expert (offline)



Do we need .. More .. Tools ? YESFor MTCC data we developed the following tool CAT

For data tacking we want to integrate it in the DQM but we need to take some decisions:

1. How access online at the Condition DB: direct access to the DB or to a replication of the DB ??

2. Which and how many plots we want to store permanently ??

3. Do we need reference plots also for correlated data ??4. Can we show/store in the DQM full DCS and XDAQ

histograms/results too ??

Analysis tools

Online DB Root files

DB query

histograms

DB replication



Histos produced during the MTCC using CAT

RMS distribution of the 23 chambers for a 4 days period with magnet ON and stable conditions

Having 480 chambers only in the barrel it was very useful to have summary plot from DCS (retrieving data from cond. db). We need to think about more summary plots from DQM–DCS–XDAQ

RMS = 0.5 A

Chamber to check using more info from DCS-DQM-XDAQ for RPC expert



A way to use DB

OMDS@IP5 ORCON@IP5 ORCOFF@T0

HLT-CMSSW application Reconstruction-CMSSW application

read/writeread/write objects read/write read/write

objects

Transformation (O2O)

DCS/DQM

Application

DQM/Offline

Application



The open issues … for us

How many CPUs on Filter Farm will be used for DQM (0-10% of HTL) ?

Which muon trigger downscale we can effort ?Can we have a muon rate of KHz in the Filter Farm ?

What can we run on the Storage Manager ?Which latency we can effort for non-event data (Online DB duplication in IT) ?Do we need dedicated RPC CPUs and disks to run the quasi-online DQM ?How have an unique graphical interface for DCS-DQM-XDAQ to help people in shift ?

Questions will be already answered here



RPC DQM group composition

The group works in the DPG under the supervision of M. Maggi and myself and in contact with Muon DPG people.detector DQM:

Bari – 4 people sharing with Offline/DQMNapoli – 5 people sharing with DCSPavia –2 people sharing with Reco & Ev Displ.

trigger DQM: Warsaw group sharing with trigger activities

We need people from the endcap groups



Conclusions

The RPC-specific components of the DQM structure in CMSSW are well under development and tested on MTCC data with proper Global DAQ format.The development now must focus now on:

Interface DQM with the Condition DB Production of historical plots, with interface to off-line DB Select a few number of “smart” summary histo/plot/tables Use also higher level objects (muon tracks, reco tools….) We are developing: detector visualization and web interface, quality test producing warning, error and alarm and tree-like structure for histo, plot….

dqm for the rpc subdetector m. maggi and p. paolucci

Documents