Reason for change

After the file versioning the site name that used to be appended to the file name is now a separate parameter. Unfortunately it was not removed from the file name. Because of this all files registered with the data catalog with L1Proc 1.52 have a '@SLAC_XROOT' incorrectly appended to the file name. While it does not break the data processing or file registration, it does break everything that tries to retrieve the files. Also, the command to register new datasets had a bug (the fileFormat was mistakenly harcoded to "root", instead to the appropriate fileFormat).

We are now also posting the alarms from the TKR monitoring to the Logwatcher. This was already planned and it was deemed unpractical to try to remove this from the code because of the emergency nature of this request. 

Test Procedure

We have processed both MC and real data on the DEV server with this version of L1Proc and verified that files can be correctly retrieved.

Rollback procedure

L1Proc can be rolled back to the previous version (not that it would be very useful).

CCB Jira

SSC-56@JIRA

Details

L1Pipeline v1r53
- removed the site name (@SLAC, @SLAC_XROOT) that was incorrectly appended to the file name
- fixed a bug in the fileFormat field (now it's the actual file Format instead of "root")

AlarmsCfg v1r1p1
- Added config files (alarms) for trackermon quantities. This addresses Jira GDQMQ-119.

Complete set of tags for L1Proc 1.53

Code Versions

GlastRelease (sim/recon) v15r2

ScienceTools (Level 2) : v9r5p4

Science Ops (task defs, scripts):

Level 1 pipeline code and applications running in L1:

svac/L1Pipeline: v1r53*

dataMonitoring/AlarmsCfg: v1r1p1*
dataMonitoring/FastMonCfg: v1r1p11

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

svac/Monitor: v1r1p13
svac/EngineeringModelRoot: v3r14p4
svac/TestReport: v6r8

calibTkrUtil v2r2p2

users/richard/pipelineDatasets: v0r4

ft2Util: v1r2p15

evtClassDefs v0r4

GPLtools: v1r10