Summary
We request to put in production several new tags (listed below).
Reason for change
Adding velocity columns to FT2 Files
Fix Bad interpolation of FT2 information during processing
Updating the IGRF-13 implementation in the astro package
Test Procedure
We have processed several full LPA runs:
FT1 Validation results: Checking FT1 files in the context of the FT2 reprocessing
Also, we reprocessed FT2 files for all runs up to and including 2021-03-24
Validation and verification steps for FT2: Adding velocity columns to FT2 Files
Rollback procedure
We could switch back to previous version of L1Proc, but will require remaking FT2 files with the old format.
CCB JIRA
- SSC-444Getting issue details... STATUS
Details
Complete set of tags for L1Proc 5.9
GlastRelease: GlastRelease-20-10-04-gr07
ScienceTools: ScienceTools-11-05-01
svac/L1Pipeline: L1Pipeline-05-09-00
calibTkrUtil: calibTkrUtil-03-00-00
fitsGen: fermitools-11-07-01
dataMonitoring/AlarmsCfg: AlarmsCfg-07-00-25
dataMonitoring/Common: Common-07-00-01
dataMonitoring/DigiReconCalMeritCfg: DigiReconCalMeritCfg-02-01-08
dataMonitoring/FastMon: FastMon-05-03-05
dataMonitoring/FastMonCfg: FastMonCfg-02-02-03
dataMonitoring/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
Reason for change:
We request to deploy datamonitoring/AlarmsCfg-07-00-25. In this new tag we updated the warning limit for some quantities: AcdPedPedMeanDeviation_PMTB_TH1 (ACD tile 73), Lac_Thresholds_FaceNeg_TH1_TowerCalLayerCalColumn_13_5_10, Lac_Thresholds_FaceNeg_TH1_TowerCalLayerCalColumn_10_7_6, Lac_Thresholds_FacePos_TH1_TowerCalLayerCalColumn_13_1_4, Lac_Thresholds_FacePos_TH1_TowerCalLayerCalColumn_13_1_1. 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 4 LPA runs ( 636085114, 636256307, 636170710 and 636299993).
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-443Getting issue details... STATUS
Details:
-Relaxing alarm limits for AcdPedPedMeanDeviation_PMTB_TH1 (ACD tile 73) in xml/acdpeds_eor_alarms.xml:
Upper warning limit changed from 12 to 14
Relevant thread: https://www-glast.stanford.edu/protected/mail/datamon/22252.html
-Relaxing alarm limits for some cal Lac thresholds:
Lac_Thresholds_FaceNeg_TH1_TowerCalLayerCalColumn_13_5_10: upper warning limit changed from 2.75 to 2.85
Lac_Thresholds_FaceNeg_TH1_TowerCalLayerCalColumn_10_7_6: upper warning limit changed from 2.75 to 2.85
Lac_Thresholds_FacePos_TH1_TowerCalLayerCalColumn_13_1_4: upper warning limit changed from 2.75 to 2.85
Lac_Thresholds_FacePos_TH1_TowerCalLayerCalColumn_13_1_1: upper warning limit changed from 2.9 to 2.95
Relevant thread: https://www-glast.stanford.edu/protected/mail/datamon/22250.html
Reason for change:
We request to deploy datamonitoring/AlarmsCfg-07-00-23. In this new tag we updated the warning limit for the Lac threshold for three CAL channels. 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 two LPA runs ( 623020039 and 623187486 ).
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-441Getting issue details... STATUS
Details:
relaxing warning limits on the Lac_Threshold for three Cal lod ends:
Lac_Thresholds_FacePos_TH1_TowerCalLayerCalColumn_13_3_3: upper warning limit changed from 2.75 to 2.8
Lac_Thresholds_FaceNeg_TH1_TowerCalLayerCalColumn_3_5_0: upper warning limit changed from 2.85 to 2.9
Lac_Thresholds_FaceNeg_TH1_TowerCalLayerCalColumn_1_1_2: upper warning limit changed from 2.75 to 2.8
Relevant thread: https://www-glast.stanford.edu/protected/mail/datamon/21636.html
Reason for change:
We request to deploy datamonitoring/AlarmsCfg-07-00-22. In this new version we updated the warning limit for the pedestal deviation of CAL channel 2784. 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 two LPA runs ( 622610230 and 621343937 ).
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-440Getting issue details... STATUS
Details:
Relaxing alarm limits for CalXAdcPedPedMeanDeviation_LEX1_TH1 and CalXAdcPedPedMeanDeviation_HEX1_TH1 for CAL channel
2784 (corresponding to Tower 14, layer 4 column 0, face 0).
Upper warning limit changed from 4 to 4.5
Relevant thread: https://www-glast.stanford.edu/protected/mail/datamon/21574.html
Reason for change:
We request to deploy datamonitoring/AlarmsCfg-07-00-21. In this tag we are relaxing the warning limit for the "y_rms" function of the quantities CalXAdcPedPedMeanDeviation_HEX1_TH1 and CalXAdcPedPedMeanDeviation_LEX1_TH1. 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 two LPA runs ( 601361472 and 601401087).
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-439Getting issue details... STATUS
Details:
we are relaxing alarm limits for CalXAdcPedPedMeanDeviation_HEX1_TH1 and CalXAdcPedPedMeanDeviation_LEX1_TH1 :
upper warning limit for the y_rms function changed from 0.25 to 0.3 in both alarms
Relevant thread: https://www-glast.stanford.edu/protected/mail/datamon/21317.html
Reason for change:
We request to deploy datamonitoring/AlarmsCfg-07-00-20. In this new tag the warning limit on the quantity Lac_Thresholds_FacePos_TH1_TowerCalLayerCalColumn_10_5_1 is slightly relaxed.
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 two LPA runs ( 601361472 and 601401087).
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-436Getting issue details... STATUS
Details:
-Relaxing alarm limits for Lac_Thresholds_FacePos_TH1_TowerCalLayerCalColumn_10_5_1:
upper warning limit changed from 2.8 to 2.9
Relevant thread:https://www-glast.stanford.edu/protected/mail/datamon/20618.html
Reason for change:
We request to put AlarmsCfg-07-00-19 in production. In this tag we modified the alarm limits for the quantities CondSummaryWord_TH1 and CondArrTKRTrigger_TH1.
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 two LPA runs (597550635 and 598143941).
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-435Getting issue details... STATUS
Details:
updating alarm limits for CondSummaryWord_TH1 and CondArrTKRTrigger_TH1:
CondSummaryWord_TH1(function="reference_histogram") upper warning limit changed from 110 to 170 (in digi_eor_alarms.xml and fastmon_eor_alarms.xml)
CondArrTKRTrigger_TH1(function="reference_histogram") upper warning limit changed from 50 to 75 (in digi_eor_alarms.xml and fastmon_eor_alarms.xml)
Relevant thread: https://www-glast.stanford.edu/protected/mail/datamon/20504.html
Below I am attaching the distribution of the values for these two quantities (in the last 1.5 years) together with the current (dashed lines) an updated limits (solid lines)
Reason for change:
We request to put AlarmsCfg-07-00-17 in production. In this new tag we updated the alarm limits for some CAL quantities:
CalXAdcPedPedMean/RMSDifference_LEX8/1 for channel 2997 and CalXAdcPedRMS_LEX8 (for the average of all channels).
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 ( 594965662, 595416944, 595439827).
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-434Getting issue details... STATUS
Details:
- CalXAdcPedRMS_LEX8_TH1 (y_average): upper warning limit changed from 5.75 to 5.85Relevant thread: https://www-glast.stanford.edu/protected/mail/datamon/20149.html
- Relaxing limits on CalXAdcPedPedMean/RMSDifference_LEX8/1 for channel 2997:
CalXAdcPedPedMeanDifference_LEX8 new limits: [-20|-15|-|8|15]
CalXAdcPedPedRMSDifference_LEX8 new limits: [-20|-15|-|8|15]
CalXAdcPedPedMeanDifference_LEX1 new limits: [-2|-1|-|1.5|2]
CalXAdcPedPedRMSDifference_LEX1 new limits: [-3|-2|-|2|3]
Relevant thread: https://www-glast.stanford.edu/protected/mail/datamon/20308.html
Reason for change:
We request to put AlarmsCfg-07-00-16 in production. In this tag we modified the alarm limits for the DQM quantity Lac_Thresholds_FaceNeg_TH1_TowerCalLayerCalColumn_13_1_4
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 two LPA runs (594097104, 594179041).
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-433Getting issue details... STATUS
Details:
From release notes for AlarmCfg-07-00-16:
upper warning/error limits changed from 2.9/3.0 to 3.0/4.0
Relevant thread: https://www-glast.stanford.edu/protected/mail/datamon/20217.html
Reason for change:
We request to put AlarmsCfg-07-00-15 in production. In this tag we modified the alarm limits for the quantity RPM_RMS for cal channel 808.
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 two LPA runs (579112092, 579089483).
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-431Getting issue details... STATUS
Details:
From release notes for AlarmCfg-07-00-15:
- relaxing warning limit for RPM_RMS_TH1 (function="y_values") for channel 808:
upper warning limit changed from 0.4 to 0.5
( cal channel 808 in the DQM code corresponds to: tower 8, layer 3, column 4. )
Relevant thread: https://www-glast.stanford.edu/protected/mail/datamon/19646.html
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-430Getting 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-428Getting 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
Reason for change:
We request to put AlarmsCfg-07-00-12 in production. In this tag we modified the alarm thresholds for the following DQM quantities for channel 2784 (corresponding to Tower 14, layer 4 column 0, face 0) :
- CalXAdcPedPedMeanDeviation_LEX1_TH1
- CalXAdcPedPedMeanDeviation_HEX1_TH1
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 two LPA runs (557369228 and 557380639 ).
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-427Getting issue details... STATUS
Details:
From release notes for AlarmCfg-07-00-12:
- Relaxing alarm limits for CalXAdcPedPedMeanDeviation_LEX1_TH1 and CalXAdcPedPedMeanDeviation_HEX1_TH1 for CAL channel 2784 :
For both alarms the upper warning limit is changed from 3.5 to 4.0
Relevant thread: https://www-glast.stanford.edu/protected/mail/datamon/18679.html
Reason for change:
We request to put AlarmsCfg-07-00-11 in production. In this tag we modified the alarm thresholds for the following DQM quantities:
Lac_Thresholds_FaceNeg_TH1_TowerCalLayerCalColumn_13_1_1 and Lac_Thresholds_FaceNeg_TH1_TowerCalLayerCalColumn_8_5_3
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 two LPA runs ( 551155095 and 551167017).
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-425Getting issue details... STATUS
Details:
From release notes for AlarmCfg-07-00-11:
- Relaxing alarm limits for Lac_Thresholds_FaceNeg_TH1_TowerCalLayerCalColumn_13_1_1:
upper warning limit changed from 2.85 to 2.95 - Relaxing alarm limits for Lac_Thresholds_FaceNeg_TH1_TowerCalLayerCalColumn_8_5_3:
upper warning limit changed from 2.75 to 2.85
Relevant thread: https://www-glast.stanford.edu/protected/mail/datamon/18377.html
Reason for change:
We request to put AlarmsCfg-07-00-10 in production. In this tag we modified the alarm thresholds for the following DQM quantities:
Lac_Thresholds_FacePos_TH1_TowerCalLayerCalColumn_10_5_1, CalXAdcPedPedRMSDifference_LEX1_TH1 (for channel 3060) and CalLogEndRangeHitCounter_Range0_TH2_Tower_15. 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 sevral LPA runs (537308355 and 537455796 for Lac_Thresholds_FacePos_TH1_TowerCalLayerCalColumn_10_5_1; 536171086, 536183216 and 536844020 for CalXAdcPedPedRMSDifference_LEX1_TH1 and CalLogEndRangeHitCounter_Range0_TH2_Tower_15.).
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-424Getting issue details... STATUS
Details:
From release notes for AlarmCfg-07-00-10:
- Updating alarm limits on CalXAdcPedPedRMSDifference_LEX1_TH1 for channel 3060 and on CalLogEndRangeHitCounter_Range0_TH2_Tower_15:
CalXAdcPedPedRMSDifference_LEX1_TH1 (in xml/calpeds_eor_alarms.xml):
-lower warning limit changed from -1.5 to -2.5
-lower error limit changed from -2 to -3
(Cal channel 3060 corresponds to Tower = 15, layer = 7, column = 6, face = 0)
CalLogEndRangeHitCounter_Range0_TH2_Tower_15 (in xml/fastmon_eor_alarms.xml):
-upper warning limit risen to 900 (from 500)
-upper error limit risen to 1400 (from 1000)
Relevant thread:https://www-glast.stanford.edu/protected/mail/datamon/17693.html
- Relaxing alarm limits for Lac_Thresholds_FacePos_TH1_TowerCalLayerCalColumn_10_5_1 in xml/recon_eor_alarms.xml:
-upper warning limit changed from 2.75 to 2.8
Relevant thread:https://www-glast.stanford.edu/protected/mail/datamon/17745.html