...
If you have spaces, typos, invisible characters in your file names, it will CRASH THE PIPELINE so before you update the rdb database, send e-mail to francesco.longo@ts.infn.it (and copies to focke@slac.stanford.edu borgland@slac.stanford.edu). They may ask you to wait for a less critical time(it's the same pipeline for TVAC, you know). Remember, you can use PROC_LEVEL DEV or TEST to run your own reconstruction if you don't want to wait for the pipeline.
...
Here's one way (by Dave Smith). From the eLog, click on "list root files" to find the name of the directory on noric where the recon files are. In that directory, you can do a grep. For example,
dsmith@noric06 $ cd /nfs/farm/g/glast/u37/BeamTest06/rootData/700000698/v4r0909p2/recon
dsmith@noric06 $ grep asym *.log
recon-v1r030603p4_700000698_00000-07469.log:XmlBaseCnv INFO successfully parsed document $(LATCalibRoot)/CAL/CU06/mc_asym.jun8th2006.CU_pass1_Pisa.xml aka /afs/slac.stanford.edu/g/glast/ground/releases/calibrations//CAL/CU06/mc_asym.jun8th2006.CU_pass1_Pisa.xml
recon-v1r030603p4_700000698_07470-14939.log:XmlBaseCnv INFO successfully parsed document $(LATCalibRoot)/CAL/CU06/mc_asym.jun8th2006.CU_pass1_Pisa.xml aka /afs/slac.stanford.edu/g/glast/ground/releases/calibrations//CAL/CU06/mc_asym.jun8th2006.CU_pass1_Pisa.xml
recon-v1r030603p4_700000698_14940-22409.log:XmlBaseCnv INFO successfully parsed document $(LATCalibRoot)/CAL/CU06/mc_asym.jun8th2006.CU_pass1_Pisa.xml aka /afs/slac.stanford.edu/g/glast/ground/releases/calibrations//CAL/CU06/mc_asym.jun8th2006.CU_pass1_Pisa.xml
dsmith@noric06 $
You can do the same for the other 4 types of CAL calib.xml files that are used in recon, e.g. ci_intnonlin, peds, mpd, thold.
CAL calibrations - XTalk And Charge Injection
Trending calibGenCal outputs
Here is the trending of calibGenCal outputs for the 3 CU CAL modules. Three time phases are included: NRL (pre-CU) and Pisa (2 phases). The 3 files are FM109, FM119and FM101. Asymmetry amplitudes are VERY stable while slight variations are observed for pedestal position (up to ~10 ADC units, ~5 ADC units in average) and MeV/DAC (up to ~4%, ~1.5% in average), due to the change of power supply in Pisa.
Trending CPTs
Here is the trending of the 3 CU CAL module performances from CPTs taken at Pisa (2 suites) and at CERN (PS and SPS). The 3 files are FM109-Pisa-PS-SPS, T02-FM119-Pisa-PS-SPSand T03-FM101-Pisa-PS-SPS for all time phases, and FM109-PS-SPS, T02-FM119-PS-SPSand T03-FM101-PS-SPS for the CERN phases only. Performances are found to be VERY stable at CERN, with slight differences wrt Pisa phases (for instance LE+/LE- diode ratio variation up to ~5%, ~2% in average), again due to the change of power supply.
Here are the same plots for PS, SPS and GSI phases: FM109-PS-SPS-GSI, T02-FM119-PS-SPS-GSIand T03-FM101-PS-SPS-GSI. No change was found.
Gain intercalibration procedure at SPSunmigrated-wiki-markup
The procedure for CAL gain intercalibration at PS and SPS uses the [CalTuple|http://www.slac.stanford.edu/exp/glast/ground/software/status/documentation/EngineeringModel/latest/CalXtalResponse/latest/] of all 4-range readout runs taken at different scanning positions. *It is based on the signal (in MeV) stored in the CalXtalFaceSignalAllRange\[tower\]\[layer\]\[column\]\[side\]\[range\] array*. At SPS we checked the constants obtained at PS (towers 2 and 3), especially for HEX8 for which the lever arm in energy deposit was not so large at PS. We also calibrated tower 1 for which LEX1/HEX8 was not well calibrated at PS.
To intercalibrate gains of each given log end, we summed almost (see below) all runs available (to maximize the statistics) and fitted the profile histogram of R_i (signal for gain #i) vs R_i+1 (signal for gain #i+1) to get the slope. This profile is limited to the events where a) R_i does not saturate, b) R_i+1 < saturation value of R_i and c) the ratio R_i/R_i+1 is close to 1 (within a band parallel to and centered on the y=x line).
...
In conclusion, only R_1/R_2 (LEX1/HEX8) slopes for tower 1 were propagated in the DB by modifying the HEX8 MeV/DAC (see below).
Update of CAL calibration constants in DB (Aug 7th) pdf resumé
...