Reason for change:
We request to put AlarmsCfg-07-00-13 in production. In this tag we modified the alarm limits for the LAC threshold of two CAL channels:
Lac_Thresholds_FacePos_TH1_TowerCalLayerCalColumn_13_1_1
Lac_Thresholds_FaceNeg_TH1_TowerCalLayerCalColumn_3_5_0
A detailed description can be found in the last section of this page.
Test Procedure:
This version of AlarmsCfg has been tested processing locally the monitoring products from three LPA runs (560096436, 560775384, 560821232).
Rollback procedure:
The package can be rolled back to the previous version by flipping a soft link. Also note that the package is completely independent from any other package running in the pipeline and will not cause a version change of L1Proc.
CCB JIRA:
SSC-430 - Getting issue details... STATUS
Details:
From release notes for AlarmCfg-07-00-13:
- Relaxing alarm limits for Lac_Thresholds_FacePos_TH1_TowerCalLayerCalColumn_13_1_1 and Lac_Thresholds_FaceNeg_TH1_TowerCalLayerCalColumn_3_5_0:
Lac_Thresholds_FacePos_TH1_TowerCalLayerCalColumn_13_1_1: upper warning limit changed from 2.8 to 2.9
Lac_Thresholds_FaceNeg_TH1_TowerCalLayerCalColumn_3_5_0: upper warning limit changed from 2.75 to 2.85
Relevant thread:https://www-glast.stanford.edu/protected/mail/datamon/18863.html
Summary
We request to put in production several new tags (listed below).
Reason for change
Pass 8.3 aka P305.
Handle building components from github.
Test Procedure
We have processed several full LPA runs:
And reprocessed ft2 files for the same runs:
Rollback procedure
We can easily switch back to previous version of L1Proc .
CCB JIRA
SSC-428 - Getting issue details... STATUS
Details
https://confluence.slac.stanford.edu/display/SCIGRPS/Release+of+P305+data+and+updated+FT2+files
Complete set of tags for L1Proc 5.7
GlastRelease: GlastRelease-20-10-04-gr02
ScienceTools: ScienceTools-11-05-01
svac/L1Pipeline: L1Pipeline-05-07-00
calibTkrUtil: calibTkrUtil-04-00-00
fitsGen: fitsGen-07-01-03
dataMonitoring/AlarmsCfg: AlarmsCfg-07-00-12 (Why is this here? It has its own CCB process. And as long as I'm going off in this direction, shouldn't calibrations have some kind of control?)
dataMonitoring/Common: Common-07-00-01
dataMonitoring/DigiReconCalMeritCfg: DigiReconCalMeritCfg-02-01-08
dataMonitoring/FastMon: FastMon-05-03-05
dataMonitoring/FastMonCfg: FastMonCfg-02-02-03
datMonitoring/IGRF: IGRF-03-01-04
svac/Monitor: Monitor-03-14-03
svac/TestReport: TestReport-12-03-02
svac/findGaps: findGaps-02-03-00
users/richard/pipelineDatasets: pipelineDatasets-01-00-00
ft2Util: ft2Util-02-04-00
evtClassDefs: evtClassDefs-01-01-05
GPLtools: GPLtools-02-00-00-wf03
ROOT: ROOT 5.34.03-gr01