...
- Pedestal. Use B/13 (non zero-suppressed) run or periodic/solicited triggers from flight mode runs.
- Caculate mean/rms of pedestal values. Check for skewness?
- HV on or off?
- Outlier rejection if HV on.
- How to treat NA tiles.
...
- Veto turn-on. Use any muon runs.
- Estimate 50% point of veto turn on curve.
- High range calibration. Converts PHA values in high range to MIP equivalent.
- Goes from linear (at low PHA) to saturation (at High PHA)
- CNO turn on. Use any run, but needs lots of stats
- Estimate 50% point of CNO turn on curve.
- Range crossover. Uses any run, but needs lots of stats
- Looks for lowest value in high-range, highest value in low range.
- Coherent noise.
- maps out pedestal fluctuations
Pedestal, MIP peak, High range calibration and coherent noise are used in reconstruction and simulation.
Veto, CNO, Range crossover are only used in simulation.
calibGenACD Package Executables and Options
...
- runMuonCalib_Svac.exe -> make mip calibrations from an input recon file or files (can use pathlength correction method)
- runVetoCalib.exe -> find veto set point in terms of PHA counts from an input digi file or files
- runCnoCalib.exe -> find CNO set point in terms of PHA counts from an input digi file or files
- runCoherentNoise.exe -> fit the coherent noise from an input digi file or files
- runRangeFit.exe -> find the range crossover points, for input digi file or files
- runStripChart.exe -> make a time series strip chart to look for flaring up of channels
...
The xml job configuration file should have the following format
<?xml version="1.0" ?>
<!-- job optin file for runMuonCalib.exe --><!DOCTYPE ifile SYSTEM "$(CALIBGENACDROOT)/xml/ifile.dtd" >
<ifile cvs_Header="$Header: $" cvs_Revision="$Revision: $" >
<section name="parameters"> input parameters for ACD pedestal and gain calibration
<item name="instrument" value="LAT">instrument type to be calibrated </item>
<item name="<parameterName>"value="<parameterValue>"> Various Job Parameter settings, one per item</item>
</section>
</ifile>
...
...
The following parameter names mirror the command line arguments give above:
...
An example calibration header might look like this (in text format)
#SYSTEM = acdCalib
#instrument= LAT
#timestamp = Wed Jan 18 16:35:58 2006
#calibType = ACD_ElecGain
#fmtVersion = v1r0p0
#startTime = 135005345:1
#stopTime = 135005389:466011
#triggers = 9796697/10799542
#source = 0
#mode = 0
...
...
startTime and stopTime show the first and last triggers seen in the data used for this calibration.
...
source and mode don't mean anything yet.