Reason for change

The main reason for change is that we now have in place all the alarms on ACD/CAL monitoring products we agreed with the subsystem experts. The proposed version of the dataMonitoring/AlarmsCfg package is v4r10p2, as opposed to v4r7p5, originally running in L1Proc 1.68.

The detailed description of the changes is in the last section.

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

SSC-154@JIRA

Details

v4r10p2

  • Alarm limits for the alarms added in tags v4r10p0 and v4r10p1 relaxed a little bit.

v4r10p1

  • New alarms on fastMon eor CalX_Total_NHit_TH1 and CalX_NHit_TH1_Tower_*.
  • Relevant jira(s): GDQMQ-230

v4r10p0

  • New alarms on digi eor CalX_Total_NHit_TH1 and CalX_NHit_TH1_Tower_*.
  • Relevant jira(s): GDQMQ-230

v4r9p3

  • Alarms tuned on CalGainsAnalyzer.
  • Relevant jira(s): GDQMQ-279

v4r9p2

  • Alarms tuned on CalPedsAnalyzer.
  • Relevant jira(s): GDQMQ-279

v4r9p1

  • Alarms tuned on calHist.
  • Relevant jira(s): GDQMQ-279

v4r9p0

  • Alarms tuned on AcdPedsAnalyzer.
  • Relevant jira(s): GDQMQ-279

v4r8p1

  • Put an alarm on digi eor Delta_CCSDSTime_EvtTime_Epu0_TH1 and Delta_CCSDSTime_EvtTime_Epu1_TH1.
  • Relevant jira(s): GDQMQ-280

v4r8p0

  • Low limits on digi trend/Rate_AcdGemCNO_GARC lowered to 0.3/0.5.
  • Alarm added on digi trend OutF_Ratio_EvtSize_CompressedEvtSize quantity.
  • Relevant jira(s): GDQMQ-276