Reason for change
The new version (v5r16p2, as opposed to v5r15p1) takes care of a new noisy cal channel (1160) and features a few new alarms on the filter rates, compression level and bandwith usage. See below for details.
Test Procedure
We have processed monitoring products from real on-orbit data (LPA) locally with this version of AlarmsCfg.
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
Details (release notes for dataMonitoring/AlarmCfg for v5r16p2)
v5r16p2
- Added alarms on the compression level and bandwidth in the digi trending. Precisely, alarms have been added on the following quantities:
- Time::Mean_CompressionLevel
- Time::Rate_CompressedEvtSizeInBytes
- Time::Mean_CompressedEvtSizeBytes
- Relevant jira(s): GDQMQ-313
v5r16p1
- Added alarms on the filter rates in the digi trending:
- Time::Rate_FswFilters_DGN
- Time::Rate_FswFilters_HIP
- Time::Rate_FswFilters_GAMMA
This is essentially to make sure that all the filters are correctly running in the nominal science configuration.
- Relevant jira(s): GDQMQ-312
v5r16p0
- Alarm limits (warning max and error max) changed in calpeds_eor for channel 1160 for the ""y_values" alarms on:
- CalXAdcPedRMS_LEX1_TH1 (1.2, 1.8 -> 3.6, 3.6) and
- CalXAdcPedRMS_LEX8_TH1 (10.0, 15.0 -> 30.0, 30.0)
- Relevant jira(s): GDQMQ-314