...
There are updates to the SVAC ntuple and the monitoring to adapt to this new GR.
| Wiki Markup |
|---|
\[I'm sorry for all the white space between the lines but Firefox 3.0 seems to have a problem with the Confluence editor.\] |
Test Procedure
We have processed real data on the DEV server with this version of L1Proc.
...
1/ If a run has no Moot key, we still retrieve the LAtC key from the data and use it to retrieve the correct trigger configuration (se we can deduce the correct trigger engines).
2/ If a run has a Moot key we use it as intended.
...
svac/Monitor: v1r2p1
- Change HFC for Hip and DFC for Dgn in MonInput_OBFStatus.cxx because of corresponding name changes in GR v15r8.
- Change getStatus32() by getStatusWord() to match with the new GLAST release (v15r8).
svac/EngineeringModelRoot: v4r1p3
- Changes induced by GR v15r8: Added the Moot key. Added filter prescale factors and indices for all the filters. Added some Gleam gamma-filter quantities and updated to new names of Gleam filters.
svac/TestReport: v6r9
- Changed the range for Datagram Histos so the complete distribution is included.
dataMonitoring/DigiReconCalMeritCfg: v1r1p32
- Remove quantity AcdVtxActiveDist. This addresses Jira GDQMQ-161.
- Change truncation from 1.1 mip to 2.5 mip in plots Recon_ReconAcdPhaMipsCorrectedAngle_PMTX_Zoom_TH1_AcdTile. This addresses Jira GDQMQ-162.
- New ACD rate asymmetry trending quantities. This addresses Jira GDQMQ-163.
dataMonitoring/Common: v3r1p6
- Now a pAlarm object is instantiated for each pAlarmSet object, even when the corresponding ROOT object cannot be found in the file. The corresponding output status is set to UNDEFINED and it appears in the summary. Usefull for debug to make sure we don't screw up thing when messing around with the variable names. Relevant jira(s): GDQMQ-159
...