...
File versioning in the L1 pipeline. : The reason for this is that a run will usually be processed multiple times piecemeal (run cut by a downlink/data transfer, missing data showing up, etc). While we only process any contiguous chunk of data once, we always merge up everything every time we process a piece of a run. It's the latest version of a the merged file that will be the most complete and which will be of (most) interest. The infrastructure (Data catalog etc) will need needs to take this into account. LONE-58@JIRA
Run quality status: L1 should update the run quality table to show the L1 processing status and whether new data have come in and the shifters should look at the monitoring again. LONE-60@JIRA
Test Procedure
We have processed both MC and real data on the DEV/TEST server with this version of L1Proc.
Rollback procedure
We can roll Both L1Proc and infrastructure code can be rolled back to the previous version of L1Procversions.
CCB Jira
Details
...
ft2Util: v1r2p15
evtClassDefs v0r4*
GPLtools: v1r10