Project

General

Profile

Feature #3186

Add fragment ID checking to some combination of RawEvent, EventStore, and builder.cc.

Added by Kurt Biery almost 7 years ago. Updated 5 months ago.

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

0%

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

Description

I believe that we should have the ability to see a MessageFacility warning or error message for each event that has duplicate fragment IDs or fragment IDs out of range, and I don't think that we want the program to stop when this happens. I suspect that this will require changes to the RawEvent and EventStore classes, and possibly to builder.cc. (It's not clear to me at the moment where the MF message should be created - in the library or the application code.)

Also, there should probably be some flag in RawEvent that we can use downstream to see that such an event has this data corruption.

History

#1 Updated by Kurt Biery over 5 years ago

  • Target version set to 576

#2 Updated by Kurt Biery over 5 years ago

  • Estimated time set to 32.00 h

The generation of the message probably won't take too long (say 4 hrs). Adding a flag to the data to indicate the problem would be noticeably more work if the infrastructure to flag events needs to be added (say 32 hours)

#3 Updated by Kurt Biery over 5 years ago

  • Estimated time changed from 32.00 h to 8.00 h

Related to Issue #5958.

#4 Updated by Eric Flumerfelt over 2 years ago

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

#5 Updated by Eric Flumerfelt 5 months ago

  • Status changed from New to Work in progress

I've started implementing this feature on artdaq:feature/3186_SMEM_FragmentIDChecking.



Also available in: Atom PDF