1. Binary Online Monitoring
2. Setup files
   1. DSP set up file: dspSetUp
   2. TDC set up files: tdcSetUp
   3. Detector Description Files
   4. Geometry file: geomSetUp
3. Environment Variables
4. If something goes wrong
5. Using sctmon to modify parameters
6. Created Histograms

Binary Online Monitoring

The binary online DQM, part of the SCT monitoring program tb_rmon, monitors the performance of the detectors by creating histograms for:

• wire maps,
• number of hits per event,
• hit position correlations between different detector planes,
• tracking efficiencies of the detectors under test (DUT's) for tracks reconstructed in the anchor planes.

The monitoring program requires setup files which describe the DSP and TDC configuration and the detectors itself. These files can be edited or listed using the sctmon command. In order to find the setup files the binary monitoring environment variables have to be set, which is done on login.

Setup Files

There are three different types of set up files describing 1) the DSP configuration, 2) the TDC configuration, 3) the detectors itself, and 4) the geometry.

DSP Setup File: dspSetUp

The file dspSetUp describes the configuration of the DSP's i.e.: which detector is connected to which DSP and link. The following example explains the format of the file:

#
# dsp  link   detectorName 
#
  0     0     ucsc1          
  1     0     lbic2_0        
  1     1     lbic2_1     
  2     0     att3        

Lines starting with # are considered as commend lines and not read by the program. In this example the detector ucsc1 is connected to DSP 0 link 0. The detector lbic2 consists of two planes, lbic2_0 and lbic2_1, which are connected to dsp 1 link 0 and link 1 respectively. Detector att3 is connected to DSP 2 link 0.

For every detector name there must be a detector description files named detectorName.det. The DSP number must start with 0 and no number must left out, otherwise the program will quit. The link number must be between 0 and 3.

TDC Setup Files: tdcSetUp

The online monitoring program expects four TDC channels (the fourth, clock is not used):

clock

time between the beam trigger and the 40 MHz clock.

syncTrig

time between the beam trigger and the synchronized beam trigger. This signal is synchronized to the clock by the trigger card.

trigger

beam trigger.

delayTrig

delayed beam trigger.

#          tdc        
#what     channel   range low/high
#
trigger:   1         0      1024
delayTrig: 2       100       500
syncTrig:  3         0      1024

Detector Description Files

For each detector that is read out there must be a detector description file. The file name convention is: detName.det where detName is the detector name (as stated in dspsetUp). The description file contains the following informations: number of readout chips (CDP128), hit type, the pitch in µ, the detector edge and the bad channel list. The following example shows the format of the file.

#
#   ucsc2 
#
nChips:   3
hitType:  1
pitch:   75
edge:     1
#
#
badChannels: 
1,2,3, 4,10- 56
100-300
END 

The bad channel list is surrounded by the two key words badChannels: and END. Bad channels are specified by a single channel number (read out channel number) or as an range, single channels and ranges are separated by commas.

The edge of a detector specifies if the 0's or the highest readout channel is close to the connector of the support board. The allowed values are +1 and -1. These numbers are important for the correlations. Two detectors with the same edge sign are correlated and anticorrelated with different sign.

Geometry File: geomSetUp

The geometry file contains for every detector an alignment parameter (offset) and a readout channel range that is used for tracking.

The strip position (in units of 75 µm) is calculated by:
pos = channel# * pitch * edge - offset;
whit pitch in units of 75 µm and edge +1 or -1. The offset should be chosen so that the difference between the detector and a reference detector (ucsc1) is peaked around zero.

The two chantoUse numbers (see example below) specify which read out channel range is used for the tracking. If a track is found in the anchor planes but the predicted position in the detector under test is outside the specified range, the track is rejected for the efficiency calculation. If chanToUse is -1, the whole detector is used.

#
#
# det  offset chanToUse
#
ucsc1     0.0    -1
lbic2_0   1.9    100 80

Binary Environment Variables

DSP_SETUP

This variable must point to the directory in which the DSP (dspSetUp) and TDC (tdcSetUp) setup files are.

DET_DESCRIB

Directory of the detector description files.

If something goes wrong

Using sctmon to modify parameters

The shell script sctmon is an utility to modify or list the parameter of the configuration files. Emacs is used as the editor (you quit emacs with C^x C^c, and y or n, if you want to safe it or not). sctmon is (hopefully) self explanatorily.