1. Introduction

The online DQM analysis for the CSC Level-1 Track-Finder is available only inside the .cms network:
http://csc-dqm.cms:20570/urn:xdaq-application:lid=1450
This module must first be initialized and then launched using the init and start buttons on the page.

The offline CSCTF DQM history is automatically updated every 10-15 minutes. It is publicly accessible on following address:
http://cms-csc.web.cern.ch/cms-csc/DQM/TrackFinder/plots/browser.html
The most of the plots on the CSCTF DQM web pages are the expert level plots. In this document we comment on these plots and identify several high-profile plots, which has to be checked routinely by a non-expert shifter.

2. Monitorables

The overall status of the system

Status of the CSCTF readout
Description: The FMM status of the DDU in the Track-Finder crate Evaluation: The DDU should always be in normal running (status==8) Actions: If the TF DDU persistently goes out of normal (status!=8) -> contact the CSC shifter/responsible Tests: EMU -> DDU status Request: To be monitored routinely Main Contact: Khristian Kotov, Gian Piero Di Giovanni Additional Contacts: Darin Acosta

Integrity of the CSCTF data

Description: * “DDU FFFF-Ethernet Spacer” — presence of a short block with a distinct FFFF-signature between two consecutive events. These data are related to Ethernet connection between DDU and PC adaptor in local DAQ mode of data taking. They fill up the last Ethernet packet to its required size at the end of event data transmission. * “Undefined Buffer” — a chunk of data of maximally allowed event size with no DDU Header or Trailer. * “DDU C-Words” — data pattern 0xC***, which should not appear in normal data, but is generated by the DDU if it is in error state. * “DDU Header Missing” — data block between two DDU Trailers (including the second one), in which no DDU Header was found. * “DDU Trailer Missing (overflow)” — DDU event started with DDU Header but reached a maximally allowed event size and did not end with the DDU Trailer. * “DDU Trailer Missing (2 headers in a row)” — data block between two DDU Headers (including the first one), in which no DDU Trailer was found. * “SP Word Count” — calculated from headers, the SP event size did not match the counted length between SP Header and SP Trailer. * “Out of SP Buffer” — calculated from headers, the SP event size is bigger than the length of the buffer containing this event. Technically this check is performed before the previously mentioned “SP Word Count” check). * “SP Trailer Missing” — The SP event buffer has the SP Header, but lacks the SP Trailer * “SP Header Missing” — The SP event buffer has the SP Trailer, but lacks the SP Header (similar to “DDU Header Missing”). Evaluation: Must always be empty Actions: If non-empty contact the CSC shifter/responsible Tests: EMU -> Data integrity Request: To be monitored routinely Main Contact: Khristian Kotov, Gian Piero Di Giovanni Additional Contacts: Darin Acosta

Synchronization Errors
Description: The status of communication path between the detector electronics and the Track-Finder crate. Evaluation: The distributions should be empty at all times Actions: If not, inform the CSC shifter/responsible Tests: EMU -> Data Block Header Request: First thing to look at. Main Contact: Khristian Kotov, Gian Piero Di Giovanni Additional Contacts: Darin Acosta

Inputs

Trigger Primitive Occupancy

CSC Occupancy Plots

Description: The η-φ occupancy of the CSC Track-Finder input data for every station in ME+ and ME- endcaps. Evaluation: The distributions should not have dead and hot areas. Can be evaluated by comparing it to the occupancies from a "good" run Actions: If has dead/hot channels, inform the CSC shifter/responsible Tests: EMU -> ME +- occupancy Request: First thing to look at! Main Contact: Khristian Kotov, Gian Piero Di Giovanni Additional Contacts: Darin Acosta

Chambers

CSC ID Occupancy

CSC ID Occupancy Plot

click(large), dblclick(back)

Description: Occupancy distribution for the chambers in a given sector and station. The index runs from 1 to 9 (max) Actions: If one of the entry is empty, it could be indicative of a chamber malfunctioning. Tests: Inputs -> CSCs Occupancy Request: Skip the plots unless problems were identified in the previous occupancy plots. If the chamber is not off due to some know issue, report the problem in the CSC elog. System View: select a TF (1->12) & a FPGA (1->5) Main Contact: Khristian Kotov (kkotov@cernNOSPAMPLEASE.ch), Gian Piero Di Giovanni (digiovan@cernNOSPAMPLEASE.ch) Additional Contacts: Darin Acosta (darin.acosta@cernNOSPAMPLEASE.ch)

LCT Quality

Quality code of the CSCTF input Trigger Primitives

click(large), dblclick(back)

Description: The TP quality codes: * q=0 (invalid), * q=1 (ALCT && CLCT && accel), * q=2 (ALCT && CLCT && accel), * q=3 (ALCT && CLCT), * q=4 (invalid), * q=5 (ALCT && CLCT), the rest: * q=ALCT.quality + CLCT.quality + 6 Actions: No Tests: EMU -> Occupancy System View: select a TF (1->12) & a FPGA (1->5) Main Contact: Khristian Kotov (kkotov@cernNOSPAMPLEASE.ch), Gian Piero Di Giovanni (digiovan@cernNOSPAMPLEASE.ch) Additional Contacts: Darin Acosta (darin.acosta@cernNOSPAMPLEASE.ch)

Synchronization

Timing of one CSC wrt. to the others

Description: Arrival bunch crossing of incoming LCTs of all other chambers with respect to the arrival of the LCTs for a single chamber. If all LCTs arrive at the Track Finder in the same bunch crossing then the central ‘zero’ bin is filled. This would correspond to the highest trigger efficiency. Actions: No Tests: EMU -> Relative Timing System View: select a TF (1->12) & a FPGA (1->5) Main Contact: Khristian Kotov (kkotov@cernNOSPAMPLEASE.ch), Gian Piero Di Giovanni (digiovan@cernNOSPAMPLEASE.ch) Additional Contacts: Darin Acosta (darin.acosta@cernNOSPAMPLEASE.ch)

Output

Tracks Occupancy

CSCTF Tracks Occupancy Plot
Description: The η-φ occupancy of the tracks found in ME+ and ME- endcaps by the CSC Track-Finder. Evaluation: The distributions should not have dead and hot areas (except gaps in the sector boundaries) Actions: Inform the CSC shifter/responsible Tests: EMU -> Tracks' occupancy Request: First thing to look at! Main Contact: Khristian Kotov, Gian Piero Di Giovanni Additional Contacts: Darin Acosta

Timing of tracks

Tracks' timing

Description: The top plot shows if the BX analyzer delays any of the stations to form a track. The bottom plot shows if tracks are well captured in the the CSCTF readout window. Evaluation: Most of the tracks in the bottom plot should be in the middle (BX=3) of the BX=[0-7) readout window. Actions: If most of the tracks are not in the BX=3, inform the CSC shifter/responsible Tests: EMU -> Internal Timing Properties Request: Check it once in a while when the CSCTF configuration key changes. Main Contact: Khristian Kotov, Gian Piero Di Giovanni Additional Contacts: Darin Acosta

Tracks' types

Tracks' types
Description: The top plot --- number of tracks found in the event (i.e. 7 consecutive BXs) in the sector. Bottom left --- track's mode and stations, crossed by the track. Bottom right --- number of stations/LCTs used to buld the tracks Evaluation: No evaluation Actions: No actions Tests: EMU -> Tracks Request: Main Contact: Khristian Kotov, Gian Piero Di Giovanni Additional Contacts: Darin Acosta

4. Definitions

CSCID

Each trigger sector in stations ME2, ME3, and ME4 consists of three 20⁰ chambers and six 10⁰ chambers. They are numbered as shown in Figure 8, as seen from the IP. In station ME1 we have two 30⁰ subsectors in each 60⁰ sector. Each 30⁰ subsector consists of nine 10⁰ chambers. Note that cathode strips in ME1/1 are divided into inner radius ME1/1a and outer-radius ME1/1b regions. Remember ME1/1a is read out, but it is not included in the CSC trigger. We number the chambers and subchambers in each 30⁰ ME1 subsector from 1 to 12 (again, viewing from the IP) as shown in Figure 9.

LCT Quality TMB Definition

LCT correlated quality definition as in TMB manual.

Show LCT Quality Definition from TMB Hide LCT Quality Definition from TMB

LEGENDA:

• ACC: ALCT accelerator muon bit
• A: ALCT was found
• C: CLCT was found
• A4: (N_A>=4), where N_A=number of ALCT layers = alct quality +3
• C4: (N_C>=4), where N_C=number of CLCT layers
• CPAT: cathode pattern trigger, i.e. (P>=2 && P<=10) at present

Selection	Quality Definition
if (C4 && (P==10) && A4 && !ACC)	Q=15 (HQ muon, straight)
else if (C4 && (P==8 or P==9) && A4 && !ACC)	Q=14 (HQ muon, slight bend)
else if (C4 && (P==6 or P==7) && A4 && !ACC)	Q=13 (HQ muon, more &#147)
else if (C4 && (P==4 or P==5) && A4 && !ACC)	Q=12 (HQ muon, more &#147)
else if (C4 && (P==2 or P==3) && A4 && !ACC)	Q=11 (HQ muon, more &#147)
reserved for HQ muons with future patterns	Q=10
reserved for HQ muons with future patterns	Q=9
else if (C4 && CPAT && A4 && ACC)	Q=8 (HQ muon, but accel ALCT)
else if (C4 && CPAT && A && !A4)	Q=7 (HQ cathode, but marginal anode)
else if (C && !C4 && CPAT && A4)	Q=6 (HQ anode, but marginal cathode)
else if (C && !C4 && CPAT && A && !A4)	Q=5 (marginal anode and cathode)
reserved for LQ muons w/2D info, in future	Q=4
else if (C && A && (P==1))	Q=3 (any match but layer CLCT)
else if (C && !A)	Q=2 (some CLCT, no ALCT [unmatched])
else if (A && !C)	Q=1 (some ALCT, no CLCT [unmatched])
else	Q=0 (should never be assigned)

-- GianPieroDiGiovanni - 2009-08-27