Skip to content

EventLoaderEUDAQ2: Do Not Drop UNKNOWN Events

Simon Spannagel requested to merge eudaq2_unkown into master

Events with UNKNOWN position should not be dropped, otherwise we just run through the file without ever matching. This will be taken care of by the next iteration, marking it as BEFORE.

Example 1

  • Event holds trigger with ID 0 and 3.
  • Detector has trigger with ID 2, position is UNKNOWN


  • We drop detector data with trigger ID 2 and read the next

What we should do:

  • Look at next event, which has trigger IDs 4 and 5.
  • Detector has trigger ID 2, tagged as BEFORE and discarded.

Example 2

The difference comes for events with no trigger ID at all, here we would just discard the event but the subsequent one may actually hold ID2.

  • Event holds no trigger
  • Detector holds trigger 1, position UNKNOWN
  • We drop detector data, go to next event, which has trigger 1
  • ...

what we should do:

  • Do not drop event, check next one
  • We have a match!
Edited by Simon Spannagel

Merge request reports