Page History
...
Run Number | Reason | Date | L1Proc | GR version | rePipe | L1Proc |
|---|---|---|---|---|---|---|
564602913 | Botched attempt at a repipe -> Do not rePipe! Pre-P305 format!!! | 2018-11-22 | L1Proc-5.6 | GlastRelease-20-10-04-gr01 |  | |
| 565721985 | Botched attempt at a repipe, repiped and marked as Complete | 2018-12-05 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 |  | |
| 565942990 | stuck "in progress", repiped and marked as Complete | 2018-12-08 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | |
|
| 566022500 | HP "in progress", repiped and marked as Complete | 2018-12-09 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | TS - No apparent errors in L1Proc and marked as checked by the Data Quality monitors. Do we just mark as complete? | |
| No, the run is missing data (as verify correctly reports, you can check the mergeEvent or Verify logs). This is probably why the run was missed the first time around. But the halfPipe correctly reported that it was InProgress. I repiped, obtained a complete set of data, and updated the status to Complete. running | HP "in progress", repiped and marked as Complete | 2018-12-11 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | TS - single error listed for digiHistAlarm in L1Proc but it's marked as checked by the data quality monitors. Do we just mark as complete? No, the run is missing data (as verify correctly reports, you can check the mergeEvent or Verify logs). This is probably why the run was missed the first time around. But the halfPipe correctly reported that it was InProgress. I repiped, obtained a complete set of data, and updated the status to Complete. | running |
| 567301141 | stuck "in progress", repiped and marked as Complete | 2018-12-23 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | | |
567598970 | Missing Data - Delivery 181227007 couldn't be dispatched - Marked as Incomplete and finalized. | 2018-12-27 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 |  | |
| 567581889 | Missing Data - Delivery 181227007 couldn't be dispatched - Marked as Incomplete and finalized. | 2018-12-27 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | | |
| 569069307 | in progress and errors about missing datagrams | 2019-01-13 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | | |
| 569213577 | in progress and errors about missing datagrams | 2019-01-15 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | | |
| 572617673 | HP "in progress", repiped and marked as Complete | 2019-02-23 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | | |
| 572853518 | stuck "in progress". Leftover chunkToken. Fixed. | 2019-02-26 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | | |
| 574781844 | "in progress", incomplete data, missing datagrams | 2019-03-20 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | | |
| 575044322 | "in progress", incomplete data, missing datagrams | 2019-03-23 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | | |
| 575762229 | "in progress", incomplete data, missing datagrams | 2019-03-31 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | | |
| 576305031 | Run was terminated by the "LAT configuration corruption" event. Marked as Incomplete and finalized. | 2019-04-07 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | | |
| 576658880 | "in progress", incomplete data | 2019-04-11 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | | |
578530168 | corrupted data in monitoring | 2019-05-02 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | | |
| 580907445 | in progress, mergeIndices reports 5 missing datagrams | 2019-05-30 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | | |
| 582073028 | in progress, mergeIndices reports missing datagrams | 2019-06/13 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | | |
...