Project

General

Profile

Feature #5958

Add the ability to flag various conditions in a RawEvent

Added by Kurt Biery over 5 years ago. Updated over 1 year ago.

Status:
New
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.

History

#1 Updated by Kurt Biery over 5 years ago

This is related to Issues #3186 and #3187.

#2 Updated by Kurt Biery about 4 years ago

  • Target version changed from 576 to v1_12_10

#3 Updated by Kurt Biery about 4 years ago

  • Target version changed from v1_12_10 to v1_12_11

#4 Updated by Kurt Biery almost 4 years ago

  • Target version changed from v1_12_11 to v1_12_13

#5 Updated by Kurt Biery almost 4 years ago

  • Target version changed from v1_12_13 to 576

#6 Updated by Eric Flumerfelt over 2 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 over 1 year ago

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



Also available in: Atom PDF