1. DQM for the RPC subdetector M. Maggi and P. Paolucci

2. DQM workshop - 28 feb 07 2 M. Maggi and P. Paolucci Outlook RPC DQM requirements event Data DQM – what we have done and learned during the MTCC we need more “sophisticated” DQM tools to access online database (non event data) guidelines and open issues DQM group composition conclusions

3. DQM workshop - 28 feb 07 3 M. Maggi and P. Paolucci RPC DQM requirements I DQM 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 DB RPC CPUs (to design) delay ? seconds ?

4. DQM workshop - 28 feb 07 4 M. Maggi and P. Paolucci RPC DQM requirements II Quasi-online: LV1 muon events DCS and XDAQ access via Condition DB RPC CPUs delay of minutes ? Offline monitoring: for RPC experts to have a full analysis Using full events and reconstruction tools using DBs CMS CPus delay ? hours ?

5. DQM workshop - 28 feb 07 5 M. Maggi and P. Paolucci 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 POOL Source Raw Data Digi Unpacker DAQ Clusters/RecHits Local Muon Reconstruction RPCMonitorDigi RPCMonitorModule Event

6. DQM workshop - 28 feb 07 6 M. Maggi and P. Paolucci 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

7. DQM workshop - 28 feb 07 7 M. Maggi and P. Paolucci Guidelines answers YES, we need history/trendig plots (efficiency, occupancy, cluster size…) YES, we need correlation trends YES, we need tools to extract complex info from condition DB and repository YES, we are using IGUANA to present DQM results MORE, we have to work on how make histo/result persistent MORE, we developed a first prototype of a synoptic view YES, we have a clear hierarchical view of the plots NO, automatic analysis procedures, for the moment YES, we can converge on a run quality flags but we have to work on

8. DQM workshop - 28 feb 07 8 M. Maggi and P. Paolucci RPC synoptic view We are working on to have a full synoptic view of our system with interactive features, alarm, warning and error

9. DQM workshop - 28 feb 07 9 M. Maggi and P. Paolucci 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)

10. DQM workshop - 28 feb 07 10 M. Maggi and P. Paolucci Do we need.. More.. Tools ? YES For 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 DBRoot files DB query histograms DB replication

11. DQM workshop - 28 feb 07 11 M. Maggi and P. Paolucci 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

12. DQM workshop - 28 feb 07 12 M. Maggi and P. Paolucci A way to use DB OMDS@IP5 ORCON@IP5 ORCOFF@T0 HLT-CMSSW applicationReconstruction-CMSSW application read/write objects read/write Transformation (O2O) DCS/DQM Application DQM/Offline Application

13. DQM workshop - 28 feb 07 13 M. Maggi and P. Paolucci 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

14. DQM workshop - 28 feb 07 14 M. Maggi and P. Paolucci 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/DQM Napoli –5 people  sharing with DCS Pavia –2 people  sharing with Reco & Ev Displ. trigger DQM: Warsaw group  sharing with trigger activities We need people from the endcap groups

15. DQM workshop - 28 feb 07 15 M. Maggi and P. Paolucci 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….