1. Status of RPC software in CMSSW
OUTLINE:
Raw data processing
Local Muon reconstruction
Data Quality Monitoring
Visualization
Simulation
RPC/Trigger meeting, June 2006
Ilaria Segoni, PH-CERN

2. Global Software DashBoard
During the first 6 months of 2006, RPC software task force has been working hard
on catching up and developing all the major components of the software needed:
CMS Week
Dec 2005
Spring
2006
NOW
11/27/2018
Ilaria Segoni , PH-CERN

3. The Muon Developers Task Force and their Objectives
Large taskforce working on developing Muon software in CMSSW coordinated by N.Amapane
& T.Cox (reconstruction) and P. Arce (simulation). For a complete list of tasks and responsibilities
see
This is not simply a porting from ORCA (for most parts), since the framework has been completely
redesigned:
Algorithms are implemented in completely bound modules
One single executable to be configured at run time to include loading of modules in
a defined sequence
The event is the data container:
11/27/2018
Ilaria Segoni , PH-CERN

4. Overview on Current RPC Software Status
All the CMSSW subsystems and packages with their interfaces have been defined, we have about 11 Subsystems involving RPC in CMSSW_0_7_0_pre5 (see ):
L1Trigger Packages for L1 trigger emulation/simulation
RecoLocalMuon Local reconstruction (RecHits, Segments).
RecoMuon Muon track reconstruction.
SimG4CMS Geant simulation.
SimMuon Digitization.
VisReco Visualization.
CondFormats Channel mapping
DataFormats Definition of classes modeling Digi, Hits
DQM Data Quality Monitoring.
EventFilter Raw data unpackers and Digi producers
Geometry xml geometry files, code to model the
detector geometry
11/27/2018
Ilaria Segoni , PH-CERN

5. RPC Raw Data Processing
POOL Source
Raw Data
Digi
Event
Unpacker
DAQ
Package EventFilter/RPCRawToDigi (I.S., M.Maggi):
Drives the raw data unpacking and produces the RPCDigi collection committed to the event
Consumes raw data from Global DAQ or from Pool source with glob al DAQ format (DCC)
The RPCDigi format is defined: BXN and StripId (DataFormats/RPCDigi)
Code for readout channel mapping to RPCDetId is ready (CondFormats/RPCObjects),
need to start using DB with actual mapping
Tested on dummy data with final DCC format
11/27/2018
Ilaria Segoni , PH-CERN

6. Muon Candidates Reconstruction
Muon candidates identification needs reconstruction of tracks across all
Muon detectors and Tracker. An orientation chart (from Nicola’s talks):
Subsystem RecoLocalMuon
Subsystem RecoMuon
11/27/2018
Ilaria Segoni , PH-CERN

7. Local Muon Reconstruction
Digi
Clusters/RecHits
Event
RecoLocalMuon
Local: “within RPC detector unit (roll)”
RecHits: 2D coordinates of the Hit within
a Roll, from the charge cluster centre and
the chamber position.
Main Components and Status:
Subsystem Geometry (M.Maggi, P.Zych): for the geometry model, based on XML description and Software Model. Status: done p
Subsystem RecoLocalMuon (M.Maggi, A.Grelli): Builds Clusters and
Rec Hits from Digi. Status: done p
Local RPC reconstruction needs to be tested
11/27/2018
Ilaria Segoni , PH-CERN

8. RPC in Muon Reconstruction
After RecoLocaMuon RPC hits can be included in track
fit to identify muon candidates
Global infrastructure, tracking code and navigating tools
are already in place (R.Bellan, C.Liu)
RPC-specific part to implement for Muon reco: DetLayers.
They are being ported from ORCA (I.S.), barrel part
is done, Endcap will be done within a week
11/27/2018
Ilaria Segoni , PH-CERN

9. Collectors can serve other collectors Clients can serve other Clients
DESIGN OF DQM IN CMSSW
(Emilio M. Christos L.)
“DQM PRODUCERS”: applications that process the (event) data and produce the
“monitorable” (collection of histograms, scalars, messages)
“DQM COLLECTORS”: applications that perfom source-client connection tasks:
Tell Clients which information is available, receive the requests for information from clients,
transfer the requested information from sources and send it to clients
“DQM CLIENTS”: applications that retrieve and process the information produced by
the sources, (e.g. displaying, running quality tests).
Producer
Collector
Client
The DQM structure has changed since ~2 weeks:
Producer
Collector
Client
New features:
Multiple Collectors
Collectors can serve other collectors
Clients can serve other Clients
11/27/2018
Ilaria Segoni , PH-CERN

10. PLANS FOR RUNNING DQM AT MTCC
DQM producers will run in the Filter IP5 (with the raw data unpacking modules for each
detector, if selection algorithms are available they will be given priority)
Within IP5 private network one collector node will (on demand) collect the data from the DQM
producers and will ship it to the detector PCs
Client application(s) will run on the detector PC’s, still within IP5 private network, they will:
run quality tests on the histograms
produce a local graphical user interface
produce a web interface through which data will be available to CERN and remote sites
store the DQM-snapshots (see later)
CERN and REMOTE SITES:
web interfaces
IP5 Network
F.F.
Detector PC’s: local GUI,
web interfae
Possibility of bridging for allowing a remote site to run locally the client
application
11/27/2018
Ilaria Segoni , PH-CERN

11. Local Muon Reconstruction
The RPC DQM-producers
The analysis is for both Barrel and Endcap, it consists of different CMSSW packages (Marcello M., Ilaria S.)
There are two DQM-analysis packages in CMSSW:
DQM/RPCMonitorModule: a service to the unpacker, it analyzes the information on the
raw data saved by the unpacker (EventFilter/RPCRawToDigi) in a transient object
(RPCEventData).
DQM/RPCMonitorDigi: an edm::EDAnalyzer, it analyzes the RPCDigi and RecHit
collections committed to the event by RPCRawToDigi and RecoLocalMuon/RPCRechit
POOL Source
Raw Data
Digi
Unpacker
DAQ
Clusters/RecHits
Local Muon Reconstruction
RPCMonitorDigi
RPCMonitorModule
Event
11/27/2018
Ilaria Segoni , PH-CERN

12. Data Concentrator Card
RPCMonitorModule
RPCMonitorModule carries out data integrity check and basic detector functioning tasks
The histograms are organized in folders corresponding to the hardware read-out organization
DCC ->RMB -> LB-TB Link -> LB
Data Concentrator Card
Splitters:
1 to 2
or 1 to 4
PAC GB
&
Sorter
RMB
TC GB &
18 Optical links,
data distributed to
4 PAC & one RMB
Slave LB
Master LB
RPC Chambers
Filter Farm
DCC-level histograms:
DCC header and trailer
intergity
L1A increment
CRC
BXN
#of events with DCC discarded
#RMB with data
RMB with Data
11/27/2018
Ilaria Segoni , PH-CERN

13. Chamber Data DCC/RMB-level histograms:
# of TB-LB Link with data
TB-LB Link with data
DCC/RMB/LB-TB Link-level histograms:
# of LB with data
LB with data
DCC/RMB/LB-TB Link/LB-level histograms:
Data truncated flag
# of bits with signal
Bits with signal
Partition number
Half Partition
Chamber Data
LB number
11/27/2018
Ilaria Segoni , PH-CERN

14. RPCMonitorDigi RPCMonitorDigi:
Histograms are organized in folders corresponding to the description of the RPC geometry
In CMSSW. The granularity is given by h-partitions (or rolls)
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
RPCRecHit analysis just introduced
The Clusterization by hand has been replaced by using the information on cluster used for
reconstructing the Rechit
New histograms will be produced with the RecHit local coordinates and errors
11/27/2018
Ilaria Segoni , PH-CERN

15. Efficiency Studies
Working with Camilo C. on a new monitoring task: h-partition efficiency
The efficiency will be produced by
extrapolating DT and CSC segments to
RPC and looking for matching hits (we
are starting from DT segments extrapolation)
A simple propagator already available
in CMSSW, fancier propagators will be
available in future CMSSW releases
We propagate segments (e.g. from DT) to the
RPC’s mounted on same DT => propagation
can be simple wrt Magnetic field effects and
MCS
11/27/2018
Ilaria Segoni , PH-CERN

16. Historical Plots OBJECTIVE:
Histograms representing the evolution over time of relevant quantities will be produced
The variables that will be plot versus time are the average of:
cluster size (muons)/roll
cluster size (noise)/roll
number of clusters/roll
efficiency/roll
occupancy/roll
noise/roll
noise/roll masking hot channels
We’ll include also information on fraction of events with corrupted data
Estimate on number of variables:
For MTCC geometry: 7 X 60 rolls = 420
For geometry at CMS startup: 7 X 2316 rolls ~ 16K
Time granularity for X-axis bin: run
Given the large number of variables to save at every run the offline DB will be used for storage
and retrivial (the application that calculates such quantities is the client running at CERN)
See for further info
on historical plots and discussion on DQM usage of databases.
11/27/2018
Ilaria Segoni , PH-CERN

17. The Client Application
Producer
CLIENT: any application that consumes the monitorable
available from the collector and processes it (e.g.
displaying it, running quality tests on histograms, producing
the web page(s) …)
The central CMSSW-DQM services provide two type of client applications:
Local IGUANA-GUI: provided entirely by DQM central systems (Giulio E., Andrea C.)
State machine client with web interface: base class with standard functionalities provided
by DQM central system (Emilio M., Dimitrios T., for configuration Ilaria S.), to be customized
by detector groups
=> for muon systems (RPC, CSC, DT) I am customizing it in the package
DQM/RPCMonitorClient (name must be changed).
11/27/2018
Ilaria Segoni , PH-CERN

18. The IGUANA GUI The root tree structure in which the
Monitoring elements are organized
is visible on the left.
The user can browse this list and
choose on the fly what to display.
The plots have the interactivity of
a root canvas
Plots are automatically refreshed
at each update
It is possible to configure through Xml file the layout of displayed histograms
11/27/2018
Ilaria Segoni , PH-CERN

19. The State Machine Client with Web Interface
Monitoring information subscription list is configured through xml file at run time
(but can be changed through drop down menu, see below)
Quality tests are configured through xml file at run time
What we have now for muon customization of this type of client:
Buttons for controlling the state
of the application
Drop-down menu for (un)subscribing
to new monitoring information
on the fly
Drop-down menu to select and
visualize histograms
Buttons to start(stop) checking the
Result of automated quality tests
semi-predefined* plots with the information for a summary
description of the state (detector state or quality of data).
*not necessarily hard coded, could be a configurable list
basic reference plots
Two additional displays
are in the page
11/27/2018
Ilaria Segoni , PH-CERN

20. The Quality Tests
The central DQM services provide a set of quality tests that can be run on the histograms:
Comparison to reference (based on c2 test)
Comparison to reference (based on Kolmogorov test)
Contents within X-range
Contents within Y-range
Identical contents
Mean value within expected range
Check for dead channels
Check for noisy channels
Contents along diagonal …
The quality tests are configured at run time through an xml file
Alarms are the product of the quality tests
Processing alarms: at the moment I just print them out (by clicking on the quality test related
buttons). But: too many alarms => impossible to get a comprehensive picture like this
DQM central services with IGUANA group just started to work on common tool for visualizing
DQM status
11/27/2018
Ilaria Segoni , PH-CERN

21. DQM Visualization with IGUANA
IGUANA has very advanced graphical tools and detector geometry description
lt is going to be used for visualizing the status of DQM quality tests
A 2D visualization of the detector will be provided (to allow visualizing all modules at once, up to layers
N.B. IGUANA client cannot run the quality tests => we will exploit new design where clients can be servers:
A Simple client runs the tests and acts as a server to the IGUANA client
Iguana Client can the be itself a server to a web Client => Visualization on the web interface will also be possible
The final tool will have two main features:
Detector modules shown with color code representing current quality tests status
Interactivity, by clicking on modules histograms will be displayed and alarms will be printed
For MTCC only feature 1 will be available
11/27/2018
Ilaria Segoni , PH-CERN

22. RPC visualization example: SimHits
Event Visualization
(I.Osborne)
RPC visualization example: SimHits
Currently one can visualize:
RPC reconstruction geometry
for Barrel &Endcap. Source is
an ideal geometry from XML file.
Validated and released.
RPC simulation geometry (full
Geant4 description with materials
and sensitive volumes). Released.
RPC digi (released).
RPC SimHits (correct and released).
For RPC RecHits implementation exists,
will soon be verified and released.
11/27/2018
Ilaria Segoni , PH-CERN

23. Visualization has been used for validating and correcting
Event Visualization
Visualization has been used
for validating and correcting
SimHits and Geometry,
e.g. by spotting incorrect hits
location
11/27/2018
Ilaria Segoni , PH-CERN

24. Visualization: RPC Geometry 3D
11/27/2018
Ilaria Segoni , PH-CERN

25. Visualization: RPC Geometry 2D
11/27/2018
Ilaria Segoni , PH-CERN

26. Coordinator of Muon simulation: P.Arce
RPC Simulation
Coordinator of Muon simulation: P.Arce
XML Geometry Description: P.Zych (Warsaw-IEP)
Reviewed w.r.t. engineers drawings
RPC Geometry Package: (M.Maggi)
DetUnit will not be full chamber but Roll (2-3-4 / chamber)
SimHits:
Ported from OSCAR (with corrections)
Detailed checks in progress (B.de la Cruz, I.Josa, Madrid-CIEMAT)
Digitisation:
M.Maggi (INFN)
ORCA-like model implemented recently
Significant changes, specially for RPCs (e.g. different Digi format)
11/27/2018
Ilaria Segoni , PH-CERN

27. Done implementation, needs testing with real data Muon reconstruction:
Summary
Raw data processing:
Done implementation, needs testing with real data
Muon reconstruction:
Done up to local reconstruction, needs integration with tracking algorithms of the other muon systems
Data Quality Monitoring:
Done up to plots requiring only RPC data. Implementation of checks involving segment propagation from DT and CSC started
Visualization:
Done for geometry, SimHits and Digi, to be tested
Simulation:
Done first implementation. Needs timing simulation and
finishing validation
11/27/2018
Ilaria Segoni , PH-CERN