Run Number | Reason | Date | Time | Dls | L1Proc | GR version | rePipe | L1Proc |
---|---|---|---|---|---|---|---|---|
626729954 | Highly fragmented run (>66 chunks). doRun/scanXxx processes fail. Moreover it's spread over 7 deliveries. | 2020-11-10 | 19:39:13-21:14:04 | 20111001[345], 20111100[1237] | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
625160754 | mergeEvt: 6 missing datagrams in apid 956, gapfinder doesn't report any gaps | 2020-10-23 | 201023010 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | |||
624820000 | switch from hequs to the bullets | 2020-10-19 | ||||||
624516636 | mergeEvt: 6 missing datagrams in apid 956, gapfinder doesn't report any gaps | 2020-10-16 | 20101600[45] | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | |||
623917505 | mergeEvt: 7 missing datagrams in apid 956 | 2020-10-09 | 06:25:04-08:02:32 | 201009007 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
622822397 | mergeEvt: 5 missing datagrams in apid 957 | 2020-09-26 | 14:13:16-15:48:06 | 20092601[12] | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
622211988 | verify finds a gap of 3 datagrams in EPU0, and of 4 in EPU1 | 2020-09-19 | 20091901[02] | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | |||
622149260 | mergeEvt: 4 datagrams missing at the start of apid 956 | 2020-09-18 | 19:14:19-20:49:09 | 200919001 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
621835509 | mergeEvt: incomplete apid 956, probably 7 datagrams missing at the end (apid 957 has 7 more) | 2020-09-15 | 200915005 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | |||
621824100 | mergeEvt: 8 missing datagrams in apid 957 | 2020-09-15 | 200915003 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | |||
621806986 | mergeEvt: 6 missing datagrams in apid 957 | 2020-09-14 | 2009{14013,15001} | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | |||
621664373 | mergeEvt: 1 non closed datagram at the end of apid 957, gapfinder: no datagram gaps for 2020-09-13 | 2020-09-13 | 200913004 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | |||
621612709 | mergeEvt: 5 missing datagrams in apid 957, gapfinder: no datagram gaps for 2020-09-12 | 2020-09-12 | 14:11:48-15:27:32 | 20091201[012] | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
621600789 | mergeEvt: 5 missing datagrams in apid 957, gapfinder: no datagram gaps for 2020-09-12 | 2020-09-12 | 10:53:08-12:01:40 | 200912009 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
621435528 | mergeEvt: 5 missing datagrams in apid 956, gapfinder: no datagram gaps for 2020-09-10 | 2020-09-10 | 12:58:47-14:10:30 | 20091001[01] | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
621236535 | mergeEvt: 6 missing datagrams in apid 956, gapfinder: there was a gap an hour earlier, retransmitted | 2020-09-08 | 05:42:14-07:17:04 | 20090800[56] | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
621081007 | mergeEvt: 5 missing datagrams in apid 956, gapfinder: no gaps for this run | 2020-09-06 | 10:30:06-11:43:23 | 200906010 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
620894265 | Michael screwed it up by accidentally rolling back the finished doRun.200904006.620894265 | 2020-09-04 | 20090400[67] | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | |||
620460723 | mergeEvt: 6 missing datagrams in apid 957, gapfinder: no gaps for 2020-08-30 | 2020-08-30 | 06:12:02-07:46:53 | 20083000[67] | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
620375156 | missing datagrams | 2020-08-29 | 200829007 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | |||
620369451 | caused 200829007.mergeIndices to fail because of an extra evt file. Repipe created identical evt files, thus L1Proc will not be rolled back, the run just needs to be finalized. | 2020-08-29 | 20082900[67] | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | |||
619313054 | mergeEvt: >1400 missing datagrams in both apids at the beginning of the run, gapfinder: no gaps around midnight of 2020-08-30 | 2020-08-16 | 23:24:13-00:33:20 | 20081700[23] | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
618823233 | mergeEvt: 6 missing datagrams in apid 956, gapfinder: no gaps for the morning of 2020-08-11 | 2020-08-11 | 07:20:32-08:36:42 | 20073000[68] | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
618805328 | mergeEvt: 8 missing datagrams in apid 957, gapfinder: no gaps for the morning of 2020-08-11 | 2020-08-11 | 02:22:07-03:31:26 | 20081100[45] | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
617777656 | mergeEvt reports 8 missing datagrams in apid 956, but gapfinder doesn't report any gaps for 2020-07-30 | 2020-07-30 | 20073000[45] | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | |||
617190465 | mergeEvt reports 8 missing datagrams in apid 957, but gapfinder doesn't report any gaps for 2020-07-23 | 2020-07-23 | 200723007 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | |||
615811484 | mergeEvt reports 6 missing datagrams, but gapfinder doesn't report any gaps | 2020-07-07 | 10:44:43-12:19:34 | 2007070{09,10} | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
615599718 | mergeEvt reports 6 missing datagrams, but gapfinder doesn't report any gaps | 2020-07-04 | 04Â 23:55:17-05Â 01:06:34 | 20070500[23] | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
615508121 | one digitization fails: "... 2 CalDigis are missing readouts for Event ...". | 2020-07-03 | 22:28:40-23:37:33 | 20070314, 200704001 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | - | |
615073887 | missing datagrams. Gapfinder doesn't report any gaps for the evening of 2020-06-28. | 2020-06-28 | 21:51:26-23:06:42 | 20062900[12] | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
614967205 | mergeEvt reports 6 data gaps in apid 957. Gapfinder doesn't report any gaps 2020-06-27. | 2020-06-27 | 16:13:24-17:48:15 | 20062701[23] | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
614162399 | mergeEvt reports 5 datagaps in apid 956. However gapfinder doesn't find any gaps. | 2020-06-18 | 20061800[89] | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | |||
612445752 | The run had data gaps, which were supposed to be filled by a redump. Unfortunately one piece was in the inaccessible part of the SSR. The run will stay incomplete. | 2020-05-29 | 20052900[89] | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | - | ||
612183340 | HalfPipe labels the run as "InComplete". MergeEvt reports missing datagrams. There were several data gaps 2020-05-26. At least some were filled. | 2020-05-26 | 10:55:39-12:30:30 | 200526007, 20052700[125] | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
612171931 | HalfPipe labels the run as "InComplete". MergeEvt reports missing datagrams. There were several data gaps 2020-05-26. At least some were filled. | 2020-05-26 | 07:45:30-09:20:21 | 20052600[567], 200527001 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
612166226 | HalfPipe labeled this run as "InComplete". MergeEvt said it's complete. However when repiping 200526005 (for 612171931) mergeIndices relabeled it, and failed with an error message hinting to this run. MK: the error was due to an evt file with slight different name. However, rolling back the HalfPipes resulted in exactly the same evt file contents. Thus, I didn't roll back L1Proc. | 2020-05-26 | 06:10:25-07:14:16 | 20052600[45] | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
611880377 | HalfPipe labels the run as "InComplete". MergeEvt reports missing datagrams. Gapfinder doesn't report a gap for the duration of the run. | 2020-05-22 | 22:46:16-23:58:37 | 200522015, 20052300[12] | L1Proc-5.7 | GlastRelease-20-10-04-gr02 |
Run Number | Reason | Date | Time | Dls | L1Proc | GR version | rePipe | L1Proc |
---|---|---|---|---|---|---|---|---|
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 | ||||
566235626 | HP "in progress", repiped and marked as Complete | 2018-12-11 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||||
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 (MK: update: data complete but no recon). MEM: rolled back checkRun and finalized. | 2019-01-13 | 010 011 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | |||
569213577 | in progress and errors about missing datagrams (MK: update: data complete but no recon). MEM: rolled back checkRun and finalized. | 2019-01-15 | 006 007 | 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 (MK: update: stat is InProgress, no recon file in db). MEM: apparently the halfPipe was rolled back after run was already reprocessed. Re-set as Complete and finalized. | 2019-03-23 | 013 014 | 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 | ||||
584730839 | in progress, complete data, missing datagrams | 2019-07-13 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||||
585187986 | This was actually complete. A botched rollback of halfPipe (190719003) produced leftover chunkTokens. Set to Complete and finalized. | 2019-07-19 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||||
585193691 | Both halfPipe and RePipe failed at delivering a complete set of data (this included a botched rollback of halfPipe 190719003). Set to Incomplete (due to 11 missing datagrams) and finalized. | 2019-07-19 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||||
585535991 | in progress, complete data, missing datagrams | 2019-07-23 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||||
585690096 | in progress, missing datagrams | 2019-07-24 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||||
586076888 | see thread. However it seems the recon file is complete. Reprocessing complete. Everything seems to have worked including the cleanupCompleteRun process. | 2019-07-29 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||||
586893790 | bunch of tasks in "Waiting" state preventing a rollback. Once that is cleared a rollback should hopefully fix everything | 2019-08-07 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | N/A | |||
586905200 | see thread . Seems the run is complete and can be just finalized. | 2019-08-07 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||||
587042253 | Several failed tasks with errors of the form: "IOError: Can't stage in <filename>". Looks like it was an xrootd hiccup. Will try rolling back but since it's so old, it will probably require a repipe. Rollback worked now complete | 2019-08-09 12:46 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | N/A | |||
587104373 | This one just looks like cleanupCompleteRun didn't run properly as everything else in both parts of the runs was listed as success. There is a chunk token directory but no token. However, the verify log complains about closing reasons for both EUP0 and EPU1. I'm think that means we need to repipe everything. | 2019-08-10 6:54 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||||
588742217 | Run is incomplete according to the halfPipe. | 2019-08-29 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||||
590065315 | Run still Incomplete in L1. Looks like cleanupCompleteRun didn't get triggered. | 2019-09-13 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||||
591931054 |  failure in checkRun 191005003.591931054. 2 missing datagram. | 2019-10-05 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||||
595240349 | 9 missing datagrams | 2019-11-12 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||||
595405654 | missing datagrams | 2019-11-14 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||||
595576882 | missing datagrams. In progress | 2019-11-16 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||||
595963106 | Missing datagrams due to decompression errors- Both halfPipe and rePipe report 6789 orphans (which translate to 53 missing datagrams). Set to Incomplete and finalized. | 2019-11-20 | 17:18:24 - 18:32:18 | 191120013 191121001 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
596299562 | HalfPipe reports "inProgress", gapfinder doesn't report any data gaps for 2019-11-24 21:30-24:00 | 2019-11-24 | 14:46:00 - 16:01:21 | 191124009 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
596916997 | missing datagrams | 2019-12-01 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||||
597315084 | HalfPipe reports "inProgress", gapfinder doesn't report any data gaps for 2019-12-06 05:00-14:00 | 2019-12-06 | 08:51:23 - 10:06:10 | 191206009 010 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
598223809 | HalfPipe reports "inProgress", missing datagrams, gapfinder doesn't report any data gaps for 2019-12-16 | 2019-12-16 | 21:16:48 - 22:51:39 | 191217001 002 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
598581385 | HalfPipe reports "inProgress", missing datagrams, gapfinder doesn't report any data gaps for 2019-12-21 | 2019-12-21 | 00:36:24 - 01:53:08 | 191221003 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
598645966 | HalfPipe reports "inProgress", missing datagrams, gapfinder doesn't report any data gaps for 2019-12-21 | 2019-12-21 | 18:32:45 - 20:07:36 | 191221009 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
598758794 | HalfPipe reports "inProgress" | 2019-12-23 | 05:39:57 - 08:44:23 | 191223003 004 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
599272563 | HalfPipe reports "inProgress". Datagram errors | 2019-12-29 | 2:22:25 - 4:58:04 | 191229002 003 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
599746995 | HalfPipe reports "inProgress", missing datagrams, gapfinder doesn't report any data gaps for 2020-01-03 | 2020-01-03 | 12:23:14 - 13:58:05 | 200103009 010 011 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
599809968 | HalfPipe reports "inProgress", missing datagrams, gapfinder doesn't report any data gaps for 2020-01-04 | 2020-01-04 | 05:52:47 - 07:14:52 | 200103009 010 011 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
600328891 | HalfPipe reports "inProgress". Datagram errors | 2020-01-10 | 10:43:13 | 200110005 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
601777922 | HalfPipe reports "inProgress", but mergeEvt doesn't report any datagram errors! Gapfinder doesn't report any data gaps for 2020-01-27. | 2020-01-27 | 02:07:06 - 03:41:57 | 200127002 003 004 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
601783627 | HalfPipe reports "inProgress". Missing datagrams. Gapfinder doesn't report any data gaps for 2020-01-27. | 2020-01-27 | 00:32:01 - 02:06:55 | 200127004 005 006 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
601890911 | HalfPipe reports "inProgress". Missing datagrams. Gapfinder doesn't report any data gaps for the morning of 2020-01-28. | 2020-01-28 | 07:55:10 - 09:04:44 | 200128006 008 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
602153762 | HalfPipe reports "inProgress". Missing datagrams. Gapfinder doesn't report any data gaps for 2020-01-31. No decompression errors in makeEvt. | 2020-01-31 | 08:56:01 - 10:07:38 | 200131007 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
603637679 | HalfPipe reports "inProgress". Missing datagrams. Gapfinder doesn't report any data gaps for 2020-02-17. No decompression errors in makeEvt. | 2020-02-17 | 13:07:57 - 14:42:49 | 200217009 010 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
603974262 | Run is complete. mergeEvt.200221009.603974262 reports 6 missing datagrams. gapfinder doesn't report any data gaps for the time interval. | 2020-02-21 | 10:37:41 - 12:12:31 | 200221009 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
604573262 | HalfPipe reports "inProgress". Missing datagrams. Gapfinder doesn't report any data gaps for 2020-02-28. | 2020-02-28 | 09:01:01 - 10:35:52 | 200228008 - 009 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
605908182 | HalfPipe reports "inProgress". Missing datagrams. Gapfinder doesn't report any data gaps for 2020-03-15. | 2020-03-15 | 19:49:41 - 21:24:31 | 200315002 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
607059914 | Highly fragmented run (231 chunks). doRun/scanXxx processes fail. | 2020-03-28 | 200328005, 006, 008 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | |||
609843485 | HalfPipe reports "InProgress". GapFinder doesn't report any data gaps of 2020-04-29. | 2020-04-29 | 200429007 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | |||
610323623 | mergeIndices labeled this run as Incomplete, but mergeEvt as Complete! MK: Repipe resulted in the same chunks. Checking the old merit file didn't reveal any gaps within the run. Thus I relabeled the run to "Complete" and rolled-back checkRun. | 2020-05-05 | 200505001, 002 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | |||
610711547 | mergeEvt reports missing datagrams. Gapfinder doesn't report any data gaps for 2020-05-09. | 2020-05-09 | 10:05:46 - 11:23:53 | 200509008, 009 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
610791211 | HalfPipe labels the run as Incomplete, mergeEvt reports missing datagrams. Gapfinder doesn't report any data gaps for 2020-05-10. | 2020-05-10 | 08:13:30 - 09:30:17 | 200510006, 007 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | ||
610968381 | mergeEvt reports missing datagrams | 2020-05-12 | 200512007, 008 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | |||
610996774 | mergeEvt reports missing datagrams | 2020-05-12 | 200512014, 015 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | |||
611162210 | mergeEvt reports missing datagrams | 2020-05-14 | 200514011, 012 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 | |||
611782769 | HalfPipe labels the run as "Incomplete". MergeEvt reports missing datagrams. Gapfinder only reports a gap after 21:19. | 2020-05-21 | 19:39:28 - 20:50:13 | 200522001 | L1Proc-5.7 | GlastRelease-20-10-04-gr02 |
/afs/slac/g/glast/ground/bin/pipeline createStream --define "downlinkID=990101001,runID=237063408" RePipe
/nfs/farm/g/glast/u28/RePipe/990101001 will contain the RePiped output (should this have a --stream <run number> flag in the command for clarity in the monitoring pages?)
if you set an environment variable, rn, to the run number (i.e. setenv rn <run number>) you can do the following command to start the repipe and have the output in the format expected for the instruction linked to below.
/afs/slac/g/glast/ground/bin/pipeline createStream --stream $rn --define "downlinkID=$rn,runID=$rn" RePipe
More details:Â Instructions for rolling back a halfPipe stream and susbsequent L1 stream and Reprocessing runs from a RePiped job
Run Number | Reason | Date | L1Proc | GR version | rePipe | L1(Re)Proc | Export |
---|---|---|---|---|---|---|---|
369152685 | ACQ Complete, L1 not finalized. Fixed in P300x. | 2012-09-12 | L1Proc-4.0 | GR-17-35-24-gr35 | 4.0 | ||
478706331 | ACQ Complete, L1 not finalized. Fixed in P300x. | 2016-03-03 | L1Proc-5.4 | GR-20-10-02 | 5.4 | ||
478756313 | ACQ Complete, L1 not finalized. Fixed in P300x. | 2016-03-04 | L1Proc-5.4 | GR-20-10-02 | 5.4 | ||
504919670 | Leap Second Run. Set to Incomplete and finalized. | 2016-12-31 | L1Proc-5.6 | GR-20-10-04-gr01 | 5.6 | ||
508046861 | ACQ InProgress. Repiped and reprocessed. | 2017-02-09 | L1Proc-5.6 | GR-20-10-04-gr01 | 5.7 | ||
512115535 | ACQ Complete, L1 Complete/Failed. Fixed in P300x. | 2017-03-25 | L1Proc-5.6 | GR-20-10-04-gr01 | 5.6 | ||
516617903 | ACQ Complete, L1 Complete/Failed. Fixed in P300x. | 2017-05-16 | L1Proc-5.6 | GR-20-10-04-gr01 | 5.6 | ||
531419768 | ACQ Complete, L1 Complete , recon on xrootd (root://fermi-gpfs05//glast/Data/Flight/Level1/LPA/prod/5.6/recon/r0531419768_v000_recon.root) but not in datacat. Run was reprocessed correctly in P300x. No follow-up needed. | 2017-11-03 | L1Proc-5.6 | GR-20-10-04-gr01 | 5.6 | ||
534500370 | ACQ Complete, L1 Complete/Failed. Fixed in P300x. | 2017-12-09 | L1Proc-5.6 | GR-20-10-04-gr01 | 5.6 | ||
549415721 | ACQ Complete, L1 Complete , recon on xrootd (root://fermi-gpfs05//glast/Data/Flight/Level1/LPA/prod/5.6/recon/r0549415721_v000_recon.root) but not in datacat. Run was reprocessed correctly in P300x. No follow-up needed. | 2018-05-31 | L1Proc-5.6 | GR-20-10-04-gr01 | 5.6 | ||
553318321 | ACQ Complete, L1 Failed. Repiped and reprocessed. | 2018-07-16 | L1Proc-5.6 | GR-20-10-04-gr01 | 5.7 | ||
554179852 | ACQ Complete, L1 Failed. Repiped and reprocessed. | 2018-07-25 | L1Proc-5.6 | GR-20-10-04-gr01 | 5.7 | ||
554396875 | ACQ Complete, cleanupCompleteRun.getTimes terminated by reaper. Run was reprocessed correctly in P300x. No follow-up needed. | 2018-07-27 | L1Proc-5.6 | GR-20-10-04-gr01 | 5.6 | ||
555737292 | ACQ Complete, L1 InProgress. Finalized. | 2018-08-12 | L1Proc-5.6 | GR-20-10-04-gr01 | 5.6 | ||
557026900 | ACQ Complete, L1 InProgress. Finalized. | 2018-08-27 | L1Proc-5.6 | GR-20-10-04-gr01 | 5.6 | ||
559965007 | Truncated Run. Set to Incomplete and finalized. | 2018-09-30 | L1Proc-5.6 | GR-20-10-04-gr01 | 5.6 | ||
562253064 | Missing Data. Set to Incomplete and finalized. Missing data sent by MOC 9/24/19, reprocessed with 5.7 - versions numbers generated are less than the v305 version from the reprocessing so ingest is not happening at the FSSC. File version edited by hand and re-exported. | 2018-10-26 | L1Proc-5.6 | GR-20-10-04-gr01 | 5.7 | ||
562258990 | This run was missing entirely. Retrieved by MOC 9/24/19 and reprocessed with 5.7. | 2018-10-26 | L1Proc-5.6 | GR-20-10-04-gr01 | 5.7 | ||
562264544 | Missing Data. Set to Incomplete and finalized. Missing data sent by MOC 9/24/19, reprocessed with 5.7 - versions numbers generated are less than the v305 version from the reprocessing so ingest is not happening at the FSSC. File version edited by hand and re-exported. | 2018-10-27 | L1Proc-5.6 | GR-20-10-04-gr01 | 5.7 | ||
564602913 | Repiped, reprocessed with 5.7, re-exported. | 2018-11-22 | L1Proc-5.6 | GR-20-10-04-gr01 | 5.7 |
Run Number | Reason | Date | FSW | L1Proc | GR version | rePipe | L1Proc |
---|---|---|---|---|---|---|---|
237911263 | silent NFS read error | 2008-07-16 | B1-0-8 | L1Proc-1.63 | Version-v15r39 | ||
237916725 | silent NFS read error | 2008-07-16 | B1-0-8 | L1Proc-1.63 | Version-v15r39 | ||
238008393 | silent NFS read error | 2008-07-17 | B1-0-8 | L1Proc-1.63 | Version-v15r39 | ||
238014123 | silent NFS read error | 2008-07-17 | B1-0-8 | L1Proc-1.61 | Version-v15r24 | ||
238207772 | silent NFS read error | 2008-07-20 | B1-0-8 | L1Proc-1.61 | Version-v15r24 | ||
238759073 | silent NFS read error | 2008-07-26 | B1-0-8 | L1Proc-1.61 | Version-v15r24 | ||
238856333 | silent NFS read error | 2008-07-26 | B1-0-8 | L1Proc-1.61 | Version-v15r24 | ||
239125611 | silent NFS read error | 2008-07-30 | B1-0-8 | L1Proc-1.61 | Version-v15r24 | ||
239129222 | silent NFS read error | 2008-07-30 | B1-0-8 | L1Proc-1.61 | Version-v15r24 | ||
241125159 | 1 missing Datagram | 2008-08-22 | B1-1-0 | L1Proc-1.63 | Version-v15r39 | ||
241491796 | missing chunk in in gcr | 2008-08-27 | B1-1-0 | L1Proc-1.63 | Version-v15r39 | ||
241501554 | 1 missing Datagram | 2008-08-27 | B1-1-0 | L1Proc-1.63 | Version-v15r39 | ||
243170470 | afs cache corruption? | 2008-09-15 | B1-1-0 | L1Proc-1.65 | Version-v15r40 | ||
243197713 | afs cache corruption? | 2008-09-15 | B1-1-0 | L1Proc-1.65 | Version-v15r40 | ||
243307762 | 2 missing Datagrams | 2008-09-17 | B1-1-0 | L1Proc-1.65 | Version-v15r40 | ||
243313738 | 2 missing Datagrams | 2008-09-17 | B1-1-0 | L1Proc-1.65 | Version-v15r40 | ||
243336617 | afs cache corruption? | 2008-09-17 | B1-1-0 | L1Proc-1.65 | Version-v15r40 | ||
243491490 | 4 missing Datagrams | 2008-09-19 | B1-1-0 | L1Proc-1.65 | Version-v15r40 | ||
243873727 | afs cache corruption? | 2008-09-23 | B1-1-0 | L1Proc-1.65 | Version-v15r40 | ||
243926731 | afs cache corruption? | 2008-09-24 | B1-1-0 | L1Proc-1.65 | Version-v15r40 | ||
244143826 | afs cache corruption? | 2008-09-26 | B1-1-0 | L1Proc-1.65 | Version-v15r40 | ||
244167563 | afs cache corruption? | 2008-09-27 | B1-1-0 | L1Proc-1.65 | Version-v15r40 | ||
245667862 | irretrievable packets missing from two datagrams | 2008-10-14 | B1-1-3 | L1Proc-1.67 | Version-v15r47p1 | ||
245673843 | This one was complete, but a retransmission changed its status | 2008-10-14 | B1-1-3 | L1Proc-1.67 | Version-v15r47p1 | ||
245685781 | all packets available; repiping will produce complete data-set | 2008-10-14 | B1-1-3 | L1Proc-1.69 | Version-v15r47p1 | ||
245691461 | all packets available; repiping will produce complete data-set | 2008-10-14 | B1-1-3 | L1Proc-1.67 | Version-v15r47p1 | ||
245697061 | This one was already complete | 2008-10-14 | B1-1-3 | L1Proc-1.67 | Version-v15r47p1 | ||
245702790 | irretrievable packet missing from one datagram | 2008-10-14 | B1-1-3 | L1Proc-1.67 | Version-v15r47p1 | ||
246390295 | Merging problems | 2008-10-22 | B1-1-3 | L1Proc-1.68 | Version-v15r47p1 | ||
246405636 | Merging problems | 2008-10-22 | B1-1-3 | L1Proc-1.68 | Version-v15r47p1 | ||
246447791 | Merging problems | 2008-10-23 | B1-1-3 | L1Proc-1.68 | Version-v15r47p1 | ||
253539991 | Delivery problems ? | 2009-01-13 | B1-1-3 | L1Proc-1.70 | Version-v15r47p1 | ||
260478011 | 1 Missing datagram ??? | 2009-04-03 | B1-1-3 | L1Proc-1.72 | Version-v15r47p7 | ||
261148032 | Insane number of chunks | 2009-04-11 | B1-1-3 | L1Proc-1.72 | Version-v15r47p7 | ||
261154012 | Insane number of chunks | 2009-04-11 | B1-1-3 | L1Proc-1.72 | Version-v15r47p7 | ||
261406015 | 1 Missing datagram ??? | 2009-04-11 | B1-1-3 | L1Proc-1.72 | Version-v15r47p7 | ||
269048825 | Silent staging failures | 2009-07-12 | B1-1-3 | L1Proc-1.73 | Version-v15r47p7 | ||
269054554 | Silent staging failures | 2009-07-12 | B1-1-3 | L1Proc-1.73 | Version-v15r47p7 | ||
269060283 | Silent staging failures | 2009-07-12 | B1-1-3 | L1Proc-1.73 | Version-v15r47p7 | ||
269066012 | Silent staging failures | 2009-07-12 | B1-1-3 | L1Proc-1.73 | Version-v15r47p7 | ||
269071741 | Silent staging failures | 2009-07-12 | B1-1-3 | L1Proc-1.73 | Version-v15r47p7 | ||
269075743 | Silent staging failures | 2009-07-12 | B1-1-3 | L1Proc-1.73 | Version-v15r47p7 | ||
269081879 | Silent staging failures | 2009-07-12 | B1-1-3 | L1Proc-1.73 | Version-v15r47p7 | ||
269087937 | Silent staging failures | 2009-07-12 | B1-1-3 | L1Proc-1.73 | Version-v15r47p7 | ||
269093942 | Silent staging failures | 2009-07-12 | B1-1-3 | L1Proc-1.73 | Version-v15r47p7 | ||
269099929 | Silent staging failures | 2009-07-12 | B1-1-3 | L1Proc-1.73 | Version-v15r47p7 | ||
272627642 | 1 bad event (seg fault) | 2009-08-22 | B1-1-3 | L1Proc-1.75 | Version-v15r47p12 |