Strip detector Code algorithm

The program is data driven, in the sense that a top subroutine looks through the input data and calls routines to process those detectors it finds.

Each of the 5 sorts of record calls an appropriate routine. E.g., for APV5 data:

  1. Event - APV5_USER
  2. Start of Burst - APV5_SOB
  3. End of Burst - APV5_EOB
  4. Start of Run - APV5_SOR
  5. End of Run - APV5_ROR
In addition, for detectors other than the telescope, a routine APV5_HBN is called. In this, the data to be included in the ntuple DST is declared.

For raw data processing, each routine is passed the entire data record written online and a pointer to the start of their data within it. In DST processing the pointer is set to -1, and the detectors should ge the data from the common block declared in APV5_HBN.

It is up to each detector to decide how to react to the data.

All detectors used so far have read-out all channels in a digital form for each event, and for these detectors the following steps are done for each event:

  1. Conversion of input to real format
  2. Bad channel identification
  3. Pedestal subtraction
  4. Common mode correction
  5. Hit search
  6. histograming and analysis using tracks.
  7. Calculation of pedestals and RMS for use above.
For binary detectors most of the above is redundant, but the alignment and here

Comments to : Bill Murray