Skip to content

Add verbose error#416

Merged
mroda88 merged 1 commit into
patch/fddaq-v5.3.xfrom
mroda/dropped_fragments
Jun 9, 2025
Merged

Add verbose error#416
mroda88 merged 1 commit into
patch/fddaq-v5.3.xfrom
mroda/dropped_fragments

Conversation

@mroda88
Copy link
Copy Markdown
Contributor

@mroda88 mroda88 commented Jun 5, 2025

When the fragment aggregator fails to send, the issue is reported as a warning which is not descriptive because we don't have any information about the what is lost. We only know what error was reported by the iomanager. This is the typical example of what is seen.

Screenshot From 2025-06-04 12-54-30

This PRs turns the warning into an error, as there is data loss and it also adds a dedicated ERS message to specify what was lost.
This is a screenshot of the message that we see after the PR.

image

@mroda88 mroda88 self-assigned this Jun 5, 2025
@mroda88 mroda88 added the enhancement New feature or request label Jun 5, 2025
@mroda88 mroda88 requested a review from bieryAtFnal June 9, 2025 13:44
Copy link
Copy Markdown
Collaborator

@bieryAtFnal bieryAtFnal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. I locally modified the FragAgg code to occasionally produce the updated error message in a fake-data-replay system, and it looked good. I also successfully ran the regression tests in the daqsystemtest repo.

@mroda88
Copy link
Copy Markdown
Contributor Author

mroda88 commented Jun 9, 2025

Great, I'll merge and add to the local build in EHN1

@mroda88 mroda88 merged commit 299ca1c into patch/fddaq-v5.3.x Jun 9, 2025
1 check passed
@mroda88 mroda88 deleted the mroda/dropped_fragments branch June 9, 2025 14:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants