The fix for the missing observing time on January 9th is as follows (from Robert Bruntz):
The segments will remain in the DB as they were originally published (in H1:DMT-ANALYSIS_READY:1).
A new flag has been created, H1:DMT-ANALYSIS_READY_9JAN2020_OBS_INTENT_FIX:1, which duplicates H1:DMT-ANALYSIS_READY:1, but with the segment [1262582081,1262592115) changed from not active to active (expanding an active segment from [1262592115,1262595538) to [1262582081,1262595538) ). New segments are being copied from H1:DMT-ANALYSIS_READY:1 and published to this flag regularly (every 6 hours, with a 2 hour lag) through at least the end of O3 (planned to be the end of April 2020). Thus, the flag will be a complete duplicate of H1:DMT-ANALYSIS_READY:1, except it will include the ~2 hr 45 min of active segments, and it will be published at higher latency (i.e., the newest segments will be 2-8 hours old; if this is an issue for anyone, contact me, and we might change that). This gives any pipelines which want to use the additional 2 hr 45 min of science time a flag to use while waiting for C01 data to become available.
Once C01 data become available, pipelines should switch to that, thus making the error in H1:DMT-ANALYSIS_READY:1 irrelevant.
Also, the link to my shift, as I didn't originally include it in my aLog.
The fix for the missing observing time on January 9th is as follows (from Robert Bruntz):
Also, the link to my shift, as I didn't originally include it in my aLog.