Finding LAC value with nomSciOps runs
Berrie and I (David Sanchez) had a look at how the code works with nomSciOps runs.
We found that some events have direct diode deposit on the opposite face. This case is not yet taking into account in the code that generated LAC histogram leading to bad LAC value.
This plot is the LAC value distribution for run 077018222. X axis is p0-Ped . We used the following configurations files:
PED : digitization-licos-v3r9p3_077014293_digi_DIGI.FLIGHT_GAIN.calPed.txt
MuSlope : digitization-licos-v3r9p3_077014313_digi_DIGI.FLIGHT_GAIN.muSlope.txt
All files can be found at /afs/slac.stanford.edu/g/glast/ground/releases/calibrations/CAL/LAT-flight_gain/
This is the LEX8 signal histogram for tower 9, layer 4, crystal 0 Face 1. X axis is ADC value . This crystal is one with weird LAC value. This is due to non-empty low energy bin. In fact the fitting procedure use the first non-empty bin as a reference. In such case, this first bin is not relevant. To tackle this issue we have modify the code that generate LAC histograms to cut the events with direct diode deposit.
the following plot are LAC value distribution and LEX8 signal histograms for the same run and crystal
It remains no bad value. It is probably useful to modify all scripts generating LAC, FLE, FHE histograms to take this case into account.
Python script for LAC, FLE, FHE
I wrote a python script to easily run the code (genHists* and fit*) for LAC, FLE, FHE. It also plot threshold distribution if ask.
the script is located here : /a/sulky36/g.glast.u33/sanchez/CALcalib.py