Reason for change
mmm
Test Procedure
We have processed data runs in the DEV pipeline with this version of L1Proc.
Rollback procedure
We can switch back to the previous version of L1Proc in case of problems.
CCB Jira
Details
L1Pipeline v1r64
GlastRelease v15r39:
- Systemtestsfor GR v15r39with respect to the previous production release, GR v15r33. There are a certain number of small differences in the ACD and CAL. They all seem consistent with random fluctuations and/or the code changes. The one worry is that all the 'random' fluctuations only seem to occur for ACD and CAL quantities, not TKR. However, the differences are small. And it's not obvious how to disentangle these things without making many new releases were we back out of one thing at the time. This is the drawback when we hold of GR for a while and get a lot of new things in all at once.
- RM diffwith respect to GR v15r33.
Complete set of tags for L1Proc 1.64
Code Versions
GlastRelease (sim/recon) v15r39
ScienceTools (Level 2) : v9r6p2
Science Ops (task defs, scripts):
Level 1 pipeline code and applications running in L1:
svac/L1Pipeline: v1r64*
calibTkrUtil v2r5
calibGenTKR v4r5
dataMonitoring/AlarmsCfg: v4r0p0*
dataMonitoring/FastMonCfg: v1r4p5*
dataMonitoring/DigiReconCalMeritCfg: v1r2p17*
dataMonitoring/Common: v4r1p0*
dataMonitoring/FastMon: v4r1p3*
datMonitoring/IGRF: v1r0p1
svac/Monitor: v1r2p23*
svac/EngineeringModelRoot: v4r3*
svac/TestReport: v6r16*
users/richard/pipelineDatasets: v0r6*
ft2Util: v1r2p23
evtClassDefs v0r6
GPLtools: v1r11