From:	FNALD::KPITTS       "Kevin Pitts"  3-NOV-1997 15:19:38.55
Subj:	COT calibration runs


Hi,
  Here is a first pass at the COT calibration runs which we plan for
run 2.  We are supposed to present this information to the DAQ upgrade
meeting on Wednesday, November 11.   The details below are fuzzy in some 
places on purpose, in other places due to my lack of knowledge of the run 1 
calibration system.
  I envision that calibrations done on a regular basis (e.g. once per day
or once per store) to be diagnostic and the true calibrations (like
ASD timing) to be done infrequently (e.g. when hardware changes.)
In other words, I was thinking that item 1. below actually have two
different aspects: 1. calibration, and 2. diagnostic.
  The TDC calibration will be exclusively diagnostic.  The details are
left to Mike Kelly.
  Special runs listed below calibrations refer to a commissioning 
period before normal data taking has begun.
  Please help me clarify and correct the items on this list.
Also, let me know of any additional calibrations or special runs
that should be added to the list.
              cheers,
               Kevin

============================================================================

Description of calibration runs:

  1.  ASD timing calibration
       frequency:  once per day
       (note: true timing info for the database would be taken less
              frequently.)
       run condition:  HV off
       length: few minutes (assumed to be dominated by setup/download time)
       configuration: acquire data by even/odd channels (all crates)
       data size: 30240 channels * 250 hits/channel * 4 bytes/hit = 30MB
                  (250 hits = 50 hits at 5 different time slots)
       processing:  data would be processed by consumer process on 
                    run control (or equivalent) machine.  
       storage:  raw calibration data discarded.   Results (t0s, slopes)
                 stored in calibration database.
       trigger:  a L1A will be delivered (by the TS) a fixed number
                 of cycles after the calibration pulse

  2.  ASD dE/dx calibration
       frequency:  infrequent 
       run condition:  HV off
       length: few minutes (assumed to be dominated by setup/download time)
       configuration: acquire data by even/odd channels (all crates)
       data size: 30240 channels * 250 hits/channel * 4 bytes/hit = 30MB
                  (250 hits = 50 hits at 5 different charges)
       processing:  data would be processed by consumer process on 
                    run control (or equivalent) machine.  
       storage:  raw calibration data discarded.   Results stored in 
                 calibration database.
       trigger:  a L1A will be delivered (by the TS) a fixed number
                 of cycles after the calibration pulse

  3.  TDC calibration
       frequency:  once per day
       run condition:  HV off
       length: few minutes (assumed to be dominated by setup/download time)
       configuration: acquire data by all channels
       data size: 30240 channels * 250 hits/channel * 4 bytes/hit = 30MB
                  (250 hits = 50 hits at 5 different time slots)
       processing:  data would be processed by consumer process on 
                    run control (or equivalent) machine.  
       storage:  Results (t0s, slopes) stored in calibration database.
       trigger:  a L1A will be delivered (by the TS) a fixed number
                 of cycles after the calibration pulse

Description of special runs

  1.  Minimum bias data
       run condition:  minimum bias
       length: one hour
       data taking configuration: standard
       data size: standard

  2.  Waveform data 
       run condition: minimum bias
       length: one hour
       data taking configuration: COT only with GBIP->VME readout of 
           full waveform data
       data size: standard COT + 5kB per event (single channel)