Reason for change

This is the first version of L1Proc using the GR v14 series. Even though GR v14r11 has a few missing things that are critical for launch (like the filter status bits), it has still been chosen to be the branching point and the first launch candidate release.

GR v14r11 and ST v9r5p4 are also in synch concerning the versions of Root and cfitsio. 

There are also a few bug fixes and updates to the monitoring, in particular we now have the normalized rates for each trigger engine.

In addition, we now have a dedicated TKR monitoring from Hiro. Because of this we use calibTkrUtil v2r2p1 which is a slightly more recent version that what is in GR v14r11. Note that nothing in GR depends or uses calibTkrUtil i.e. it is only included for bookkeeping reasons. This new version of calibTkrUtil will be included in a subsequent GR.

Test Procedure

We have processed both MC and real data on the DEV server with this version of L1Proc.

Rollback procedure

We can roll back to the previous version of L1Proc.

CCB Jira

SSC-44@JIRA

Details

GlastRelease v14r11:
- The GR v14 series has gone through extensive MC based testing by the C&A group. it has also been verified that this GR can process real data. It should also be noted that this GR uses Root 5.18.00b.
- Systemtests for GR v14r11show many differences with respect to the previous production version of GR, but this is as expected.
- RM diff with respect to the previous production release, GR v13r11p9. I will not detail the changes here as there are understandably too many.

Science Tools v9r5p4:
Science Tools has been built against Root 5.18.00b to be consistent with GR v14r11. 

ft2Util: v1r2p15
- Identical to the previous version except that it contains a lot more documentation (added because of the upcoming ft2Util code review).  

calibTkrUtil v2r2p1: 
- New version for TKR monitoring running in the L1 pipeline.  

dataMonitoring/FastMon: v3r1p4
- Added quantity evt_data_transfer_id that contains de data transfer id and fixed meta_context_run_id that now contains the real run id, aka run.startedat. Relevant jira(s): GDQMQ-115

dataMonitoring/FastMonCfg: v1r1p11
- Fix variable type for meta_LATC_master and evt_data_transfer_id to uint32 in baseConfig. Relevant jira(s): GDQMQ-115
- New quantity : evt_data_transfer_id that contains the data transfer id, retrieved from the evt header, via LSEReader.runId(). Relevant jira(s): GDQMQ-115

dataMonitoring/DigiReconCalMeritCfg: v1r1p16
- Added new FastMon trending quantity FastMon_Evt_DataTransferId and FastMon_MetaContext_LATC_Master that have type outputnumber, the last value in the time bin is considered. That addresses Jiras GDQMQ-115 and 107.
- Change variable type object for quantity DataTransferId. Prefix will be Number_ instead of OutF_.  The variable type will be UInt_t instead of Float_t.  That addresses Jira GDQMQ-115.
- Add DataTransferId. That addresses Jira GDQMQ-115.
- Additional monconfig file (monconfig_trackermon_trending.xml) to handle high level tracker monitoring information produced by Hiro Tajima etal. This addresses Jira GDQMQ-119.
- Added new histograms. This addresses Jira GDQMQ-113 and GDQMQ-114.

dataMonitoring/Common: v3r1p5
- Debug message added in the ACD/CAL peds/gains fitting tool. Relevant jira(s): GDQMQ-65.
- Bug fix in the ACD/CAL peds/gains fitting tool (check on a zero division error). Relevant jira(s): GDQMQ-65.

svac/Monitor: v1r1p10
- Added new FastMon trending quantities FastMon_Evt_DataTransferId and FastMon_MetaContext_LATC_Master that are of type outputnumber. JIRAs GDQMQ-115 and GDQMQ-107
- Change variable type object for quantity DataTransferId. Prefix will be Number_ instead of OutF_. New object was defined for that MonSecondListNumber. It is identical to MonSecondListUInt, the the prefix used is Number_ instead of OutUI_.
- Changes in code to handle high level tracker monitoring information produced by Hiro Tajima etal. This addresses Jira GDQMQ-119. Several of the base/classes needed to be changed:
- Added possibility of normalize rates stored in multidimensional variables. This is useful for Trigger Engines, for instance. This addresses the Jira GDQMQ-83.

svac/TestReport: v6r8
- Tracked through JIRA GDQMQ-9and this Confluence page.
- Checking CCSDS time vs event time stamp: JIRA GDQMQ-120.
- Checking GPS second counter: JIRA GDQMQ-120
- Checking extended GEM scalers: JIRA GDQMQ-120.
- Checking number of event consistency with extended GEM sequence counter: JIRA GDQMQ-120.
- Checking livetime consistency: JIRA GDQMQ-120.
- Handling error details in xml: JIRA GDQMQ-85.
- Checking Ground Id: JIRA GDQMQ-120.
- Checking Latc Key: JIRA GDQMQ-120.

org-glast-dataqualitymonitoring : v0r1p14
- Updated ingestion script to support integers

Complete set of tags for L1Proc 1.50

Code Versions

GlastRelease (sim/recon) v14r11*

ScienceTools (Level 2) : v9r5p4*

Science Ops (task defs, scripts):

Level 1 pipeline code and applications running in L1:

svac/L1Pipeline: v1r50*

dataMonitoring/AlarmsCfg: v1r1p0
dataMonitoring/FastMonCfg: v1r1p11*

dataMonitoring/DigiReconCalMeritCfg: v1r1p16*
dataMonitoring/Common: v3r1p5*
dataMonitoring/FastMon: v3r1p4*
datMonitoring/IGRF: v1r0p1

svac/Monitor: v1r1p10*
svac/EngineeringModelRoot: v3r14p3
svac/TestReport: v6r8*

calibTkrUtil v2r2p1* 

users/richard/pipelineDatasets: v0r4

ft2Util: v1r2p15*

evtClassDefs v0r3

GPLtools: v1r10