Summary
IGRF was updated L1Proc on to extend the IGRF model ( SSC-470 - Getting issue details... STATUS )
However, this change also required an update to astro, as we discovered due to multiple failures in L1Proc starting on
Reason for change
Extend the IGRF model beyond 2024 in astro, to match the contents of IGRF-03-04-00.
Test procedure
Tests to compare the output of the astro package with the distributed fortran code from NOAA is here: Upgrading to IGRF 14 in the astro and IGRF packages (courtesy of Nicola)
Rollback procedure
No rollback is possible, as runs newer than 12/15/2024 won't process otherwise.
Code update procedure
This was done in a non-standard way, as both GR and L1 were patched "in place" (due to the lack of RM at present).
- from here:
/afs/slac.stanford.edu/g/glast/ground/releases/volume05/GlastRelease-20-10-04-gr07 - delete the entire
astropackage fromGlastRelease-20-10-04-gr07, clone it from git and check outastro-04-04-00 recompile astro in situ, with the following command:
/afs/slac/g/glast/applications/SCons/2.1.0/bin/scons -C GlastRelease --with-GLAST-EXT=/afs/slac/g/glast/ground/GLAST_EXT/redhat6-x86_64-64bit-gcc44 --site-dir=../SConsShared/site_scons --compile-opt astro
CCB JIRA
SSC-472 - Getting issue details... STATUS
Details
Complete set of tags for L1Proc 5.9
GlastRelease: GlastRelease-20-10-04-gr07, containing astro: astro-04-04-00
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-04-01
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
Summary
We are requesting to update the IGRF model in L1Proc to version 14th, which includes 2025-2030.
Reason for change
The current IGRF model expires on 12/31/2024. We need to deploy the extension included in IGRF-14.
Code update procedure
IGRF will be patched "in situ" without requiring a new version of L1Proc, simplifying the deployment step.
We will use a symlink to update IGRF, in the same manner as we are doing for AlarmsCfg
Detailed steps:
- L1 build location:
/afs/slac.stanford.edu/g/glast/ground/releases/volume11/L1Proc/5.9 - rename the existing IGRF and symlink:
mvIGRF IGRF-03-01-05; ln -s IGRF-03-01-05 IGRF - clone IGRF:
git clone https://github.com/fermi-lat/IGRF.git IGRF-03-04-01; cd IGRF-03-04-01; git checkout IGRF-03-04-01 eval `/afs/slac/g/glast/isoc/flightOps/rhel6_gcc44/ISOC_PROD/bin/isoc isoc_env -c --add-env=root`- compile the new package:
cd python; make clean; make - replace the symlink
Test procedure
IGRF-03-04-01 was tested separately. Results reported here: https://github.com/fermi-lat/IGRF/pull/1
Rollback procedure
Revert the symlink to point to the older version of IGRF
CCB JIRA
SSC-470 - Getting issue details... STATUS
Details
Complete set of tags for L1Proc 5.9.1
GlastRelease: GlastRelease-20-10-04-gr07
astro (installed within GR): astro-04-03-00
ScienceTools: ScienceTools-11-05-01
L1Pipeline: L1Pipeline-05-09-01
calibTkrUtil: calibTkrUtil-03-00-00
fitsGen: fermitools-11-07-01
IGRF: IGRF-03-04-01
dataMonitoring/Common: Common-07-00-01
dataMonitoring/DigiReconCalMeritCfg: DigiReconCalMeritCfg-02-01-08
dataMonitoring/FastMon: FastMon-05-03-05
dataMonitoring/FastMonCfg: FastMonCfg-02-02-03
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
Summary
astro was patched on the fly in L1Proc on
Recording this change in CCB for posterity
Reason for change
astro fails extrapolation for altitudes below 500km.
Due to degradation of the orbit, we are observing lots of L1 failures.
Test procedure
This was patched "live" in L1Proc, to avoid reprocessing for failed runs.
Rollback procedure
No rollback is possible, as runs newer than 11/14/2024 won't process otherwise.
Code update procedure
This was done in a non-standard way, as both GR and L1 were patched "in place" (due to the lack of RM at present).
First of all, we patched the version of astro included in GR 20-10-04-gr07:
- clone astro from git, checkout tag
astro-04-02-00 - patch the code and push to branch
fix-altitude - tag from the branch as
astro-04-03-00
Next, we patched GR in place after making an additional copy for testing):
- the location is here:
/afs/slac.stanford.edu/g/glast/ground/releases/volume05/ - made a copy of
GlastRelease-20-10-04-gr07and renamed the un-patched version toGlastRelease-20-10-04-gr07-arch - deleted the entire
astropackage fromGlastRelease-20-10-04-gr07, cloned it from git and checked outastro-04-03-00 recompiled astro in situ, with the following command:
/afs/slac/g/glast/applications/SCons/2.1.0/bin/scons -C GlastRelease --with-GLAST-EXT=/afs/slac/g/glast/ground/GLAST_EXT/redhat6-x86_64-64bit-gcc44 --site-dir=../SConsShared/site_scons --compile-opt astro
CCB JIRA
SSC-469 - Getting issue details... STATUS
Details
Complete set of tags for L1Proc 5.9
GlastRelease: GlastRelease-20-10-04-gr07, containing astro: astro-04-03-00
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 AlarmsCfg-07-01-04 in L1proc. In this new tag we relaxed the limits for the Lac thresholds of 2 cal channels, and the limit for the pedestal deviation of ACD tile 49 (PMT B)
Test Procedure:
This version of AlarmsCfg has been tested processing locally the monitoring products from two LPA run (753502966 and 748852859).
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-468 - Getting issue details... STATUS
Details:
from AlarmsCfg/doc/release.notes:
AlarmsCfg-07-01-04 10-Nov-2024 maldera
- Updating alarm limits on Lac threshold:
Lac_Thresholds_FaceNeg_TH1_TowerCalLayerCalColumn_3_5_0: upper warning limit changed from 2.9 to 3.0 (error limit rised from 3.0 to 3.5)
Lac_Thresholds_FaceNeg_TH1_TowerCalLayerCalColumn_11_1_11: upper warning limit changed from 2.8 to 2.9
- Relaxing warning limits for acd ped deviaton for tile 49, pmt B
AcdPedPedMeanDeviation_PMTB_TH1: upper warning limit changed from 8 to 10 (for channel 49) channels 49 and 81 exluded from the computation of the y_rms
Relevant thread: https://www-glast.stanford.edu/protected/mail/datamon/5305.html
Reason for change:
We request to deploy AlarmsCfg-07-01-03 in L1proc. In this new tag we relaxed the limits for the Lac threshold of cal channel corresponding to tower 3, layer 6, column 6, pos. face.
Test Procedure:
This version of AlarmsCfg has been tested processing locally the monitoring products from a LPA run (748107887)
.
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-467 - Getting issue details... STATUS
Details:
from AlarmsCfg/doc/release.notes:
Updating alarm limits on Lac threshold:
Lac_Thresholds_FacePos_TH1_TowerCalLayerCalColumn_3_7_6: upper warning limit changed from 2.75 to 2.85
Relevant thread: https://www-glast.stanford.edu/protected/mail/datamon/4838.html
Reason for change:
We request to deploy AlarmsCfg-07-01-02 in L1proc. In this new tag we relaxed the limits for the alarms related to the spacecraft altitude.
Test Procedure:
This version of AlarmsCfg has been tested processing locally the monitoring products from a LPA run (42863605).
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-466 - Getting issue details... STATUS
Details:
from AlarmsCfg/doc/release.notes:
- -Updating alarm limits on Mean_FastMon_SpaceCraft_Altitude:
low warning limit changed from 500 to 480
Relevant threads:https://www-glast.stanford.edu/protected/mail/datamon/4445.html
Reason for change:
We request to deploy AlarmsCfg-07-01-01 in L1proc.
In this tag we updated the DQM limits for the lac threshold of few CAL channels and for the average cal pedestals RMS
Test Procedure:
This version of AlarmsCfg has been tested processing locally the monitoring products from different LPA runs (734985932, 735128086, 735150831, 735230438, 735275826).
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-464 - Getting issue details... STATUS
Details:
from AlarmsCfg/doc/release.notes:
- Updating alarm limits on Lac thresholds for 4 channels:
Lac_Thresholds_FacePos_TH1_TowerCalLayerCalColumn_13_3_3: upper warning limit changed from 2.8 to 2.9
Lac_Thresholds_FaceNeg_TH1_TowerCalLayerCalColumn_3_7_6: upper warning limit changed from 2.75 to 2.85
Lac_Thresholds_FaceNeg_TH1_TowerCalLayerCalColumn_13_3_2: upper warning limit changed from 2.75 to 2.85
Lac_Thresholds_FacePos_TH1_TowerCalLayerCalColumn_3_1_1: upper warning limit changed from 2.75 to 2.85
- Updating warning limit on CalXAdcPedRMS_LEX8_TH1:
upper warning limit changed from 5.85 to 5.95
Relevant threads https://www-glast.stanford.edu/protected/mail/datamon/4038.html
Reason for change:
We request to deploy datamonitoring/AlarmsCfg-07-00-38. In this new tag we updated the DQM limits the for pedestal deviation of for CAL channel 2784 ( corresponding to Tower 14, layer 4 column 0, face 0) ) for LEX1 and HEX1 ranges
Test Procedure:
This version of AlarmsCfg has been tested processing locally the monitoring products from one LPA run (724241190).
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-460 - Getting issue details... STATUS
Details:
-Relaxing alarm limits for CalXAdcPedPedMeanDeviation_LEX1_TH1 and CalXAdcPedPedMeanDeviation_HEX1_TH1 for CAL channel 2784:
Upper warning limit changed from 5.0 to 5.5
Upper error limit changed from 5.5 to 6.0
Relevant threads https://www-glast.stanford.edu/protected/mail/datamon/3260.html
Reason for change:
We request to deploy datamonitoring/AlarmsCfg-07-00-37. In this release we updated the DQM limit the for the RMS of the distribution of the ACD pedestal deviations
Test Procedure:
This version of AlarmsCfg has been tested processing locally the monitoring products from two LPA run (706230133, 706331486).
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-458
-
Getting issue details...
STATUS
Details:
Relaxing warning limit for y_rms of acd pededestal deviaton (PMT A):
AcdPedPedMeanDeviation_PMTA_TH1 y_rms: upper warning limit changed from 3 to 3.2
relevant thread: https://www-glast.stanford.edu/protected/mail/datamon/2330.html
Reason for change:
We request to deploy datamonitoring/AlarmsCfg-07-00-36. In this new tag we updated the DQM limits the for pedestal deviation of ACD tile 8, PMTA, and we excluded this channel from the computation of the pedestal deviation y_rms
Test Procedure:
This version of AlarmsCfg has been tested processing locally the monitoring products from one LPA run (698916419).
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-456 - Getting issue details... STATUS
Details:
Relaxing warning limits for acd ped deviaton for tile 8, pmt A
AcdPedPedMeanDeviation_PMTA_TH1: lower warning limit changed from -8 to -11 (for channel 8)
channel 8 excluded from the computation of the y_rms
relevant thread: https://www-glast.stanford.edu/protected/mail/datamon/1906.html
Reason for change:
We request to deploy datamonitoring/AlarmsCfg-07-00-35. In this new tag we updated the limits the following DQM quantities:
Lac_Thresholds_FacePos_TH1_TowerCalLayerCalColumn_13_5_10
Lac_Thresholds_FacePos_TH1_TowerCalLayerCalColumn_2_4_3
Test Procedure:
This version of AlarmsCfg has been tested processing locally the monitoring products from different LPA runs ( 695303900, 695833867).
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-455 - Getting issue details... STATUS
Details:
Relaxing alarm limits on Lac thresholds for 2 channels:
- Lac_Thresholds_FacePos_TH1_TowerCalLayerCalColumn_13_5_10: upper warning limit changed from 2.75 to 2.85
- Lac_Thresholds_FacePos_TH1_TowerCalLayerCalColumn_2_4_3: upper warning limit changed from 2.75 to 2.85
relevant thread: https://www-glast.stanford.edu/protected/mail/datamon/1811.html
Reason for change:
We request to deploy datamonitoring/AlarmsCfg-07-00-33. In this new tag we updated the limits on some DQM quantities:
Lac_Thresholds_FaceNeg_TH1_TowerCalLayerCalColumn_13_1_4, Lac_Thresholds_FacePos_TH1_TowerCalLayerCalColumn_1_1_2, AcdPedPedMeanDeviation_PMTB_TH1 (channel 82).
Test Procedure:
This version of AlarmsCfg has been tested processing locally the monitoring products from different LPA runs ( 682758265, 684628507, 684964766).
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-454 - Getting issue details... STATUS
Details:
-Relaxing alarm limits on Lac thresholds for two CAL channels:
Lac_Thresholds_FaceNeg_TH1_TowerCalLayerCalColumn_13_1_4: upper warning limit changed from 3 to 3.2
Lac_Thresholds_FacePos_TH1_TowerCalLayerCalColumn_1_1_2: upper warning limit changed from 2.8 to 2.9
relevant thread: https://www-glast.stanford.edu/protected/mail/datamon/1289.html
-Relaxing alarm limits on AcdPedPedMeanDeviation_PMTB_TH1 for channel 82:
Lower warning limit changed from -8.0 to -15.0
Lower error limit changed from -15.0 to -20.0
relevant thread: https://www-glast.stanford.edu/protected/mail/datamon/1133.html
Reason for change:
We request to deploy datamonitoring/AlarmsCfg-07-00-32.
In this new tag we updated the limits on some DQM quantities:
Lac_Thresholds_FacePos_TH1_TowerCalLayerCalColumn_1_4_0,
ReconAcd2PhaMipsCorrectedAngle_PMTA_Zoom_TH1_AcdTile_62,
ReconAcd2PhaMipsCorrectedAngle_PMTB_Zoom_TH1_AcdTile_46
ReconAcd2PhaMipsCorrectedAngle_PMTB_Zoom_TH1_AcdTile_59
ReconAcd2PhaMipsCorrectedAngle_PMTB_Zoom_TH1_AcdTile_61
Test Procedure:
This version of AlarmsCfg has been tested processing locally the monitoring products from different LPA runs ( 678106138, 678613557, 676595731,655238687, 678766831)
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-452 - Getting issue details... STATUS
Details:
-Relaxing warning limits on ReconAcd2PhaMipsCorrectedAngle_PMT*_Zoom_TH1_AcdTile_* for 4 ACD channels:
tile 62 PMTA
tile 46 PMTB
tile 59 PMTB
tile 61 PMTB
lower warning limit changed from 0.9 to 0.8
Relevant thread: https://www-glast.stanford.edu/protected/mail/datamon/0813.html
-Relaxing alarm limits on Lac_Thresholds_FacePos_TH1_TowerCalLayerCalColumn_1_4_0:
upper warning limit changed from 2.75 to 2.85
Relevant thread: https://www-glast.stanford.edu/protected/mail/datamon/0962.html
Reason for change:
We request to deploy datamonitoring/AlarmsCfg-07-00-31. In this new tag we updated the limits on two DQM quantities:
CalXAdcPedPedMeanDeviation_LEX1_TH1 and CalXAdcPedPedMeanDeviation_HEX1_TH1 for CAL channel 2784
Test Procedure:
This version of AlarmsCfg has been tested processing locally the monitoring products from one LPA run (670231532)
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-451 - Getting issue details... STATUS
Details:
Relaxing alarm limits for CalXAdcPedPedMeanDeviation_LEX1_TH1 and CalXAdcPedPedMeanDeviation_HEX1_TH1 for CAL channel 2784:
Upper warning limit changed from 4.5 to 5.0
Upper error limit changed from 5.0 to 5.5
Relevant threads: https://www-glast.stanford.edu/protected/mail/datamon/0409.html and https://www-glast.stanford.edu/protected/mail/datamon/0445.html
Reason for change:
We request to deploy datamonitoring/AlarmsCfg-07-00-30. In this new tag we updated the limits on the DQM quantities Lac_Thresholds_FaceNeg_TH1_TowerCalLayerCalColumn_8_5_3 and Lac_Thresholds_FacePos_TH1_TowerCalLayerCalColumn_13_3_2.
A more 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 2 LPA runs ( 666409910, 666501563)
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-450
-
Getting issue details...
STATUS
Details:
-Relaxing alarm limits on Lac thresholds for 2 channels:
Lac_Thresholds_FaceNeg_TH1_TowerCalLayerCalColumn_8_5_3: upper warning limit changed from 2.85 to 2.95
Lac_Thresholds_FacePos_TH1_TowerCalLayerCalColumn_13_3_2: upper warning limit changed from 2.75 to 2.9
relevant thread: https://www-glast.stanford.edu/protected/mail/datamon/23834.html
Be the first to like this