Reason for change
Bug fixes for the monitoring is the driver for this request. They affect critical quantities like GPS out of lock, LAT mode and longitude. We also have a new GlastRelease which contains a bug fix to the event time stamp in case of lost GPS Lock (we should let the UDL do its job!) in addition to updated versions of the CAL calibration code.
Test Procedure
We have processed real data and MC on the DEV server with this version of L1Proc.
Rollback procedure
L1Proc can be rolled back to the previous version.
CCB Jira
Details
L1Pipeline v1r55
-
GlastRelease v15r6p1:
- New versions of CAL calibration code.
- Bug fix for the event time stamp: Should really let the UDL do its job and not use 20MHz if we lose GPS lock! JIRA GRINF-48
- Systemtestsfor GR v15r6p1wrt GR v15r5 show no differences.
- RM diffwith respect to the previous production release, GR v15r5.
dataMonitoring/FastMonCfg: v1r2p0
- Update MergedHisto File with CondArrCNO_CalLoOpensWindow_TH1 - GDQMQ-139
- Updated xml/configLCI.xml with newest quantities for LCI runs - GDQMQ-141
- Updated xml/config.xml with a cut to remove sollicited triggers from FastMon CondSummaryWord_TH1 histogram - GDQMQ-142
- Updated xml/config.xml with a new range for CondSummaryWord_WithSolicited_TH1 histogram - GDQMQ-143.
- Relevant jira(s): GDQMQ-139, 141, 142, 143
- Renamed CondArrCalCNO_CalLoOpensWindow_TH1 to CondArrCNO_CalLoOpensWindow_TH1 in xml/config.xml. Relevant jira(s): GDQMQ-139
dataMonitoring/DigiReconCalMeritCfg: v1r1p25
- Change also (Fast mon) quantities FastMon_Evt_DataTransferId and FastMon_MetaContext_LATC_Master from outputnumber to valuechange[0]
- Change quantity LastDataTransferId from type outputnumber to valuechange[0]. This addresses jira GDQMQ-146
.
- Added Normalized rates for FastMon GPS_OUTofLock. This addresses Jira GDQMQ-138.
- Added normalized rates for GPS_OUTofLock. This addresses Jira GDQMQ-138.
- Added rates for CTBParticleType==0 and == -1. Change range of histogram for CTBParticleType to accomodate the values -1 and 0, which were not expected according to documentation provided.
dataMonitoring/FastMon: v3r2p1
- Bug fix when calculating the phi angle of the 3D Position vector, now using safer ROOT.TVector3 methods.
- Now handling LATC_master key in LPA runs with meta.hardwareKey and in LCI runs with meta.writeCfg. Relevant jira(s): GDQMQ-145
svac/Monitor: v1r1p20
- Changes to accomodate quantity type ValChange_ into database. That addresses jira GDQMQ-146.
Complete set of tags for L1Proc 1.55
Code Versions
GlastRelease (sim/recon) v15r6p1*
ScienceTools (Level 2) : v9r5p4
Science Ops (task defs, scripts):
Level 1 pipeline code and applications running in L1:
svac/L1Pipeline: v1r55*
dataMonitoring/AlarmsCfg: v1r1p1
dataMonitoring/FastMonCfg: v1r2p0*
dataMonitoring/DigiReconCalMeritCfg: v1r1p25*
dataMonitoring/Common: v3r1p5
dataMonitoring/FastMon: v3r2p1*
datMonitoring/IGRF: v1r0p1
svac/Monitor: v1r1p20*
svac/EngineeringModelRoot: v4r0p0*
svac/TestReport: v6r8
users/richard/pipelineDatasets: v0r4
ft2Util: v1r2p15
evtClassDefs v0r4
GPLtools: v1r10