rpc dpg status and plans

CMS Physics Days, DPG session, 23 May 2007

Marcin Konecki (University of Warsaw)

for RPC DPG group

RPC DPG status and plans

•Reports on each Physics Days ~1/month

•Coordination Meetings ~2/month

Marcello Maggi – INFN Bari

CMS WEEK RPC Meeting 19/06/07Marcin Report

CMS Physics Days, DPG session, 23 May 2007

Marcin Konecki (University of Warsaw)

for RPC DPG group

RPC DPG status and plans

•Status and recent progress - geometry, simulation - L1 emulator - RBC emulator - R2D - DQM - reconstruction

•Preparation for Global Runs

•Plans for CSA07

Marcin Konecki, University of Warsaw-3/20-

Geometry, RecHit

• Geometry changes in 140: RPCGeometry, RPCGeometryBuilder, MuonCommonData (xml files), MuonNumbering

RPCDigi refers now to local strip numbering; L1Emulator, RPCUnpacker adopted to the change

• RPCRecHit become 2D to allow better use for track reconstruction

Maggi, Pugliese


Simulation: cluster sizeMuon

1 2 3 4 5MTCC data: The part of strip where the muon was crossing RPC is determined with a help of DT reconstruction. Cluster size distribution for each slice of strip determined independently.

From each distribution the mean value has been calculated as function of the slice centre position.

CMSSW: RPCSimAvarage which use the parameterization extracted by the experimental cl. size distribution given by MTCC data.

Raffaello Trentadue


Simulation: current work

• EXISTS: Noise simulation (version 0 – same level everywhere). Need to be tested and integrated (Avila, Gomez, Sanabria)

• PLANS: Cluster size tails (Tupputi) It requires large MC statistics for cosmics

• PLANS: X-talk effect (requires a re-design of RPCdigitizer) (Trentadue)

• PLANS: Timing to be ported from ORCA soon


Status of RBC emulator

The goal: a not so heavy package that can be used as an event filter, with the possibility of using it for the MTCC data too.

It must select the events according to the chosen majority, bunch crossing, pattern (single or neighbour sectors).

A preliminary classes structure of a RBC Trigger is already done and committed; these classes still need to be filled.

At this stage there is a working event filter routine (ready to be committed).

The first release can generate a plot that allows to visualize the event in 3D (X and Y axis represent a 2D vision of wheel and sector and Z axes represents the number of fired chambers).

Example of a triggered single event (selected majority = 4)

C. Viviani


Status of L1 Trigger

T. Früboes

• Trigger inefficiencies understood, prepared fix to be released in 14x (necessary to generate huge number of muons for pattern generation).


Status of L1 Trigger

T. Früboes

•RPC trigger patterns are delivered with EventSetup. This is preparation for accessing patterns from DB

•Improvements in patterns generation. Generated patterns finally fit into hardware

•Keeping up to date with changes in framework (library-pluggins separation)

•RPC trigger emulator is now used to help debugging hardware. States of emulation on different stages of pipeline used to verify hardware implementation of algorithm


RawToDigi

Raw Data (64 bit data words, belongs to DCC):BX record (16 bits)current BX

•TB record (16 bits)tb number in dcc, link input number

•LB record (16 bit)Link board data (lb id in link, coded fired strips and FEBs)

RPC DIGI (belongs to DetUnit):

• (int) strip (0..~95)strip in DetUnit coordinates (local frame)

•(int) bxcurrent bunch crossing identification

The relation between RawData and Digis is not straightforward, requires dedicated map of connections and decoding of records. One LB record may correspond to several digis

Packages: RPCRawToDigi (decoding), RPCObjects (cabling map), RPCConnectivity (cabling map building), RPCFileReader (created raw data from technical readout data XML files and opposite).

Building of the cabling map (sqlite file) read OMDS, which is independent of CMSSW geometry. Map is still under debugging.

M. Bluj, A. Kalinowski, M. Konecki


RawToDigi

PERFORMANCE Successfully used in MTCC

Version of package with some timing optimization released

It has been tested that sequence digi-raw-digi producesinitial data. There are however some features:- map contains only initial connection (ie. Staged version), some CMSSW digis (baseline) will be lost- splitter is present in DB. One digi generates several raw data- there are some cases where digis where lost: -- problem in rotation of a few chamber in barrel -- incompatible DB-CMSSW numbering in endcaps -- lost links in DB (???)

REGIONAL RECONSTUCTION

Not a problem from R2D point, need clear example how to proceed in CMSSW framework (contrary to ORCA based on global hit collections which make regionality difficult.

Single mu, link splitting

<t> ~ 0.1 ms/event

M. Bluj, A. Kalinowski, M. Konecki


monitoring of RawToDigi

• In view of the Commissioning the dedicated fast module for data integrity checks to be embedded in the HLT application is under deep review.

The responsible person: Michal Szleper (Warsaw) has started to look in CMSSW to check which strategy to use. The module (skeleton) is needed before GR withactive HLT.


RPC DQM

Working version exists

Study of MTCC data still ongoing

New IGUANA GUI (Lomidze) is progressingg

Automatic Histogram checking (Cimmino, Noli)

CSC segment extrapolation for local efficiency measurements (Carrillo)

RPC trigger monitoring (Warsaw) needs more efforts

M. Maggi, P. Paolucci


• Commissioning requires the capability of running RPC standalone. Reconstruction needs RPC seeding. First version (barrel) exists: MuonSeedGenerator/RPCSeedGenerator can compute this seeding

• Pt is calculated by arranging the four observed chambers (one for station) in all possible combinations of three chambers. For every one of these groups of hits, we estimate the radius of curvature and then the pt (according to the formula pt = qBR).

Reconstrution

D. Pagano


Reconstruction

• Due to limited resolution of RPC the momentum estimation is bad for muons with pt > 10 GeV.

• There is a working prototype, authors are looking for improvement in pt estimation & extensions to endcaps

Pt = 10 GeV/c

Pt = 50 GeV/c

D. Pagano


Preparation for Trigger tests and Global Run

• Available hardware for Tower tests, Trigger Vertical Slice Tests, Global Run:

– Detector candidate is YB+2,

– Electronics (DAQ+PAC) and software will be ready mid June

– All (control, signal, TTC) “long” cables (USX-USC) will be installed mid June

– YB+2 alone does not fit PAC (“pointing at vertex”) geometry,

– PAC Trigger based on “RBC like” pattern in Sec. 11;

– RBC technical trigger will be ready mid June?


Software for Trigger tests

Module for interconnection and trigger algorithms tests:– Uses pulsers and diagnostic VME readouts,– Reads/stores pulse patterns/muon candidates in XML files:

• Patterns for pulses are generated with CMSSW,• Muon candidates form VME readouts compared with emulator,

– Central Java manager for setup and control of the tests,– Communication with XDAQ via SOAP and with DB via JDBC

(Hibernate),– used for pattern tests, but some functionalities under development

CMSSW: old code (RPCFileReader) for technical readout from Trigger Boards (TB) has ben rewritten in XML. The simulation data can be written in XML files and injected to the hardware on OPTO chip. The data from TB can be dumped to XML files (same format) and read into CMSSW. Code works with 140+.

A. Kalinowski

M. Pietrusinski, K. Bunkowski


Current tests (14-23.05)

• Trigger pattern test:– send signals generated by CMSSW to opto devices on TBs,

– fully propagate by RPC trigger,

– compare with CMSSW emulator result on each level of the system;

• DAQ tests:– Last version of DCC firmware successfully tested in Warsaw,

– FED system tests:• subdet-backend to central DAQ, following

https://twiki.cern.ch/twiki/bin/view/CMS/DAQ-CI-subdet-DAQ;

• moved to June (due to collistions with the 1st Global Run).


Tests 11-22.06, 23-30.06• FED system tests• Tower tests & Vertical slice tests:

– readout of detector data via diagnostic readouts (for tower tests from LBs only),

– propagate with RPC test framework to CMSSW (with xml files) for chamber understanding and DQM,

– trigger provided by PAC with cosmic patterns (from one sector only);• Pattern test II +„Dry HLT” tests:

– pulse signal on opto on TBs,

– propagate through DAQ to EvF ("dry HLT") (to be agreed with Emilio Meschi),

– propagate through emulator in CMSSW and compare with data form VME.

Last week of June (GR week) – no interface with other subsystems.


Tests 22-31.07

• Participation in Global Run:–detector: YB+2,–PAC trigger based on cosmic pattern in

Sec. 11,–RBC trigger possible, current status:

The RBC (RPC Balcony Collector) production was completedRBC boards are ready to be installed in the LBBoxes; Half wheel is equipped with 3 RBCs that can be operated as during MTCC (via copper cables), providing sector-level cosmic trigger The RPC Trigger Board to be used as TTU (Technical Trigger Unit) is almost ready under the hardware point of view, but some work is needed for the firmware and software tasks The full chain RBC-TTU is not ready for the 1st Global Run - No RPC wheel-level cosmic trigger available


CSA07: RPC Calib Stream

Test of the RPC calibration stream for fast RPC data analysis

• The DQM on Filter Farm and on Storage Manager allows for few Hzs monitoring

• Enough for most of the monitorables quantities but NOT ENOUGH for fast local efficiency studies:~1MEvent per chamber x 150 “Sectors” = 150 MEventFew KHz => results in one day but Few Hz => results in 10 years…

Emulate the application as in the Filter Farm: O(10kB/s) on dedicated RPC Farm where DQM modules produces predefined set of histograms

T0 -> T1s express lineT1 -> T2s data transfer

O(1GB) of data/day to produce real time analysis

CSA07

Looking for manpower!


Summary:

• Important progress in ongoing work simulation, r2d, emulators, reconstruction, stable DQM

• new rechits and geometry OK. (apart of two small issues discovered with R2D – under investigation)

• active preparation for GR + own tests procedures!

• more manpower needed for HLT RPC stream

SUMMARY

rpc dpg status and plans

Documents