Reason for change
We request to put AlarmsCfg-XX-YY-ZZ and DigiCalReconMeritConfig-aa-bb-cc in production.
These new tags implements a few changes to the alarm limits on mean number of track, on the pedestel difference of cal channel 3060-LEX1 and on the nomalized rates.
We are also updating the nomalization flies used to get the normalized rates.
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.
per i files di normalizzazione?
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-398 - Getting issue details... STATUS - Request to update DQM alarm settings
Details
- relaxing the alarms limits for the quantities CalXAdcPedPedMeanDifference_LEX1_TH1 and CalXAdcPedPedRMSDifference_LEX1_TH1 for the Cal channel 3060 (Tower 15, layer 7 column 6, face 0). This change is not related to the Pass8 switchover:
- CalXAdcPedPedMeanDifference_LEX1_TH1: limts changed from aaa to bbb..
- CalXAdcPedPedRMSDifference_LEX1_TH1: limits changed from ccc to ddd
- Relevant thread:https://www-glast.stanford.edu/protected/mail/datamon/14535.html
- Changing the alarm limits for Mean_ReconTracks:
- limits changed from .... to....
- Updating normalization files in DigiReconCalMeritCfg using the runs processed with pass8:
- updetred files: FactorsToNormRates_EarthLimb.txt and FactorsToNormRates_noEarthLimb.txt
- using runs from xxyyyzz to xxyyzz
- updating alarm limits for the normalized rates of different classes of events: