From leitch@hp866b.lanl.gov Wed Jul 11 23:03:10 2001
Date: Mon, 25 Jun 2001 9:15:56 MDT
From: Mike Leitch <leitch@hp866b.lanl.gov>
To: ming@bnl.gov, ahoover@kaon.rhic.bnl.gov
Subject: calibration procedure (such as it is)

muTr Calibration Procedure - MJL - 6/25/01
==========================================

Presently this procedure is fairly complicated and probably only
do-able by muTr experts.

1) To take calibration data:
* log into phoncs account on phoncs0
* make sure to do a setuponcs
* make sure DAQ is working
* you need to know what pcf file in $RC_HW_CONF you are working with,
  usually whatever mutr.s.pcf is linked to.
* in $RC_HW_CONF copy working pcf file to mutr.s.pcf.BASE.calib
  and edit mutr.s.pcf.BASE.calib to use for the GTM file
  GTM.MUTR_1000HZ_CALI.gtm (not GTM.MUTR_1000HZ.gtm)
* cd ~phoncs/mutr/calib
* make sure no muTr run control is running. You can use
  "psit" to look for a muTr run control and "killit" to
  kill any you find. Also look for muTr GUI runcontrol
  and stop it if you find one.
* run calibration script to take a series of runs:
  Just type "docalib &".
* note what log file is being written to (the "docalib" script
  prints out the log file name) (Make sure this log file
  doesn't fill up the phoncs home disk with error messages -
  yes it once happened)
* calib.csh uses run control to take a series of 9 runs at
  calibration DAC amplitudes of 0x00, 0x10, ... 0x80
* data is recorded into /common/buffer2/calibdata
  in prdf files with names like, e.g.
  rc-0016429-MUTR.S-0.prdf
  (where 16429 is the run number, the "-0" is the station-1
  data file, etc.)

2) To analyze calibration data:
* log into phnxmutr account on va011.phenix.bnl.gov
* cd calib
* type "do 22jun01_1234" where "22jun01_1234" is from the
  log file name you noted above when taking data.
* this will do the analysis of the calibration data and produce
  some ntuples, ps files showing the results and a txt file containing
  the resulting pedestals, gains and rms values suitable for input
  to the data base.
* inspect the txt file (e.g. with a name like cal_22jun01_1234.txt)
  to see that results are reasonable.
* if reasonable you can put it into Objectivity:
  edit dbputAll.C to read this new file (cal_22jun01_1234.txt) and
  to use the appropriate time stamps for this calibration then
  run it in root:
  root -b
  .x dbputAll.C

--
Michael J. Leitch                    FNAL E866/NuSea Spokesman
P-25, M.S. H846                      Phone:  (505)667-5481
Los Alamos National Laboratory       Email:  leitch@lanl.gov
Los Alamos, NM 87545                 FAX:    (505)665-7920