...
Bug fixes for the monitoring is the driver for this request. They affect critical quantities like GPS out of lock and , 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.
...
| Wiki Markup |
|---|
*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|https://jira.slac.stanford.edu/browse/GDQMQ-146]. \- Added Normalized rates for FastMon GPS_OUTofLock. This addresses Jira [GDQMQ-138|https://jira.slac.stanford.edu/browse/GDQMQ-138]. \- Added normalized rates for GPS_OUTofLock. This addresses Jira [GDQMQ-138|https://jira.slac.stanford.edu/browse/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: v3r2p0v3r2p1
- 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
...
dataMonitoring/DigiReconCalMeritCfg: v1r1p25*
dataMonitoring/Common: v3r1p5
dataMonitoring/FastMon: v3r2p0v3r2p1*
datMonitoring/IGRF: v1r0p1
...