Allow Data Duplication
We should allow for data which are not from the event-defining detector to be duplicated.
Imagine the (very real) situation in which we have a very short frame with a high rate produced by the DUT to define out event. Now we would like to add M26 data to it with its very long frame length. This works fine for the first event, but the subsequent DUT frames will not have any data assigned to them because the M26 reader already went to the next frame and evaluates this as position
If we retain the event even if classified as
DURING and re-evaluate the next time, in the case above it would again return
DURING and we would re-assign it.
In the more "normal" case where we really moved on, we will simply evaluate it as
BEFORE and move on to the next event.
Is there a flaw in this logic or does this make sense?