A new version of DC pulser calibration data analyzer is ready for your trial.
I made a directory, t0new, in track2 account and copied a tcl input file and
kumac files there.
This is standard recsis user package. The control variables and parameters
are set in the tcl input file. The results are stored in a ntuple which can
be viewed by provided kumac's. So far the results are only pulser peak
positions. I would write another subroutine to calculate the t0's for the
data base by adding corrections. It is good enough for now to assess the data
quality and do a full analysis.
There are three analysis mode:
a) preview
If preview is set to true, only raw tdc spectra (in ns) by superlayers
are stored in the hbook file.
kumac: tdc_prev.kumac
b) single superlayer mode
If preview is set to false and single_sl_mode true, one can select one
superlayer to analyze. The pulser peak information along with the
TDC spectra for each individual wire in the superlayer are stored in
the hbook file.
kumac: peak_adb_ssl.kumac
peak_wire_ssl.kumac
t0_adb_ssl.kumac
t0_wire_ssl.kumac
c) full analysis mode
If preview is set to false and single_sl_mode false, all superlayers switched
on by tcl variables will be analyzed. Only pulser peak information will be
in the hbook file.
kumac: peak_adb_ssl.kumac
peak_wire_ssl.kumac
t0_adb_ssl.kumac
t0_wire_ssl.kumac
peak1d.kumac
peak_adb.kumac
peak_wire.kumac
t0_adb.kumac
t0_wire.kumac
To find peaks, the program requires windows to be set for both pulser peaks.
The peak searching procedure can still be improved.
Regards,
Liming
PS. 1. Thanks Franz for his DC electronic ID subroutines.
2. The track2 account is full. Please remove obsolete files if you know any.
Please run the program with the following path for now:
/net/fs1/home/qin/bin/SunOS/t0
3. Though the program is reasonably fast on my alpha, it may not be very
fast on jlabs's during the day.