Project

General

Profile

Feature #3188

Support the routing of corrupt RawEvents to different disk files

Added by Kurt Biery over 6 years ago. Updated over 6 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
User Code
Target version:
-
Start date:
12/18/2012
Due date:
% Done:

0%

Estimated time:
Scope:
Internal
Experiment:
-
SSI Package:
Duration:

Description

In artdaq, there is the possibility that events may be have some sort of data corruption, but we would still want to save these events to disk, probably in a separate stream. Examples of data corruption include missing fragments and fragments with duplicate or invalid fragment IDs.

At the moment, the artdaq RawEvent class does not include flags to indicate the presence of data corruption, and those will need to be added first. However, once those are available, it would be great to have the ability to route those events to different streams in art.

Of course, it would be good to discuss the right way to indicate data corruption in the RawEvent class as part of this feature request so that everything works together smoothly.

History

#1 Updated by Christopher Green over 6 years ago

  • Category set to User Code
  • Status changed from New to Rejected

This is already something you can do without a change to art: assuming the RawEvent is changed to offer some way of telling the input source that the data are corrupt, then the DS50 input source can place a product in the event that can be detected by a CorruptionFilter downstream: the output configuration can therefore have a selection on events that pass the CorruptionFilter flag.

Please let us know if you have any trouble seeing how to implement this functionality in the DS50 code.



Also available in: Atom PDF