Versions Compared

Old Version 113

changes.mady.by.user Maria Elena Monzani

Saved on

compared with

New Version 114

changes.mady.by.user Michael Kuss

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Run Number

Reason

Date

L1Proc

GR version

rePipe

L1Proc

564602913

Botched attempt at a repipe -> Do not rePipe! Pre-P305 format!!!2018-11-22L1Proc-5.6

GlastRelease-20-10-04-gr01

(tick)(tick)
565721985Botched attempt at a repipe, repiped and marked as Complete2018-12-05L1Proc-5.7

GlastRelease-20-10-04-gr02

(tick)
565942990stuck "in progress", repiped and marked as Complete2018-12-08L1Proc-5.7

GlastRelease-20-10-04-gr02

TS - two errors listed for verifyErrorAlarm 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.
566022500HP "in progress", repiped and marked as Complete2018-12-09L1Proc-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.
566235626HP "in progress", repiped and marked as Complete2018-12-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.
567301141stuck "in progress", repiped and marked as Complete2018-12-23L1Proc-5.7

GlastRelease-20-10-04-gr02

567598970

Missing Data - Delivery 181227007 couldn't be dispatched - Marked as Incomplete and finalized.

2018-12-27L1Proc-5.7

GlastRelease-20-10-04-gr02

(error)
567581889

Missing Data - Delivery 181227007 couldn't be dispatched - Marked as Incomplete and finalized.

2018-12-27L1Proc-5.7

GlastRelease-20-10-04-gr02

(error)
569069307in 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-15L1Proc-5.7

GlastRelease-20-10-04-gr02

572617673HP "in progress", repiped and marked as Complete2019-02-23L1Proc-5.7

GlastRelease-20-10-04-gr02

572853518stuck "in progress". Leftover chunkToken. Fixed.2019-02-26L1Proc-5.7

GlastRelease-20-10-04-gr02

574781844"in progress", incomplete data, missing datagrams2019-03-20L1Proc-5.7

GlastRelease-20-10-04-gr02

575044322"in progress", incomplete data, missing datagrams2019-03-23L1Proc-5.7

GlastRelease-20-10-04-gr02

575762229"in progress", incomplete data, missing datagrams2019-03-31L1Proc-5.7

GlastRelease-20-10-04-gr02

TS - looks like it was redone but not marked complete.Image Added
576305031Run was terminated by the "LAT configuration corruption" event. Marked as Incomplete and finalized.2019-04-07L1Proc-5.7

GlastRelease-20-10-04-gr02

(error)
576658880"in progress", incomplete data2019-04-11L1Proc-5.7

GlastRelease-20-10-04-gr02

578530168

corrupted data in monitoring2019-05-02L1Proc-5.7

GlastRelease-20-10-04-gr02

580907445in progress, mergeIndices reports 5 missing datagrams2019-05-30L1Proc-5.7

GlastRelease-20-10-04-gr02

582073028in progress, mergeIndices reports missing datagrams2019-06/13L1Proc-5.7

GlastRelease-20-10-04-gr02

(tick)(tick)

...