Project

General

Profile

Feature #5958

Add the ability to flag various conditions in a RawEvent

Added by Kurt Biery over 5 years ago. Updated 28 days ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Needed Enhancements
Target version:
-
Start date:
12/18/2012
Due date:
% Done:

0%

Estimated time:
40.00 h
Experiment:
Co-Assignees:
Duration:

Description

When an event times out in the event store, has duplicate fragment IDs, or has some other exceptional condition, we should be able to flag it, and possibly route it to a different disk file (stream).

This issue requests the addition of functionality in RawEvent (and whatever other classes may need to be changed) to support the indication of exceptional conditions.

We should also provide a sample art module (or whatever the correct mechanism is) to demonstrate the routing of events with issues to different disk files.


Related issues

Related to artdaq - Feature #3186: Add fragment ID checking to some combination of RawEvent, EventStore, and builder.cc.Work in progress12/18/2012

Related to artdaq - Idea #20815: Include RawEventHeader as art productReviewed09/12/2018

Related to artdaq - Feature #23131: Add reporting of fragment IDs for missing fragments to the FragmentWatcher moduleAssigned08/15/2019

History

#1 Updated by Kurt Biery over 5 years ago

This is related to Issues #3186 and #3187.

#2 Updated by Kurt Biery over 4 years ago

  • Target version changed from 576 to v1_12_10

#3 Updated by Kurt Biery over 4 years ago

  • Target version changed from v1_12_10 to v1_12_11

#4 Updated by Kurt Biery over 4 years ago

  • Target version changed from v1_12_11 to v1_12_13

#5 Updated by Kurt Biery about 4 years ago

  • Target version changed from v1_12_13 to 576

#6 Updated by Eric Flumerfelt almost 3 years ago

  • Category set to Needed Enhancements
  • Target version deleted (576)

This could be interesting, especially where it interacts with the Dispatcher and Online Monitor modules.

#7 Updated by Eric Flumerfelt almost 2 years ago

artdaq v3 requires RawEvent to be fixed-size, so this must be a consideration in adding error flags.

#8 Updated by Eric Flumerfelt 28 days ago

  • Status changed from New to Closed

This functionality is mostly already present. RawEventHeader includes the "is_complete" flag (though RawEventHeader is not currently stored in art events, see #20815). MissingDataCheck_module fulfills the rest of the requirements, though "has duplicate fragment IDs" would have to be handled in feature/3186_SMEM_FragmentIDChecking.

#9 Updated by Eric Flumerfelt 28 days ago

  • Related to Feature #3186: Add fragment ID checking to some combination of RawEvent, EventStore, and builder.cc. added

#10 Updated by Eric Flumerfelt 28 days ago

  • Related to Idea #20815: Include RawEventHeader as art product added

#11 Updated by Eric Flumerfelt 28 days ago

  • Related to Feature #23131: Add reporting of fragment IDs for missing fragments to the FragmentWatcher module added


Also available in: Atom PDF