ICARUSTriggerV3: add error message for timeout#200
Merged
gennadiy-fnal merged 1 commit intorelease/v2_01_00from Mar 27, 2026
Merged
ICARUSTriggerV3: add error message for timeout#200gennadiy-fnal merged 1 commit intorelease/v2_01_00from
gennadiy-fnal merged 1 commit intorelease/v2_01_00from
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR adds an error message in the
ICARUSTriggerV3boardreader if no data is received after a given timeout.A new FHiCL parameter is introduced to set the timeout in seconds (
data_timeout_s, default:60).Depending on the trigger requirements, it's normal to find several empty polls between triggers. These "no data" warnings are regularly logged at
DEBUGlevel. This PR introduces a timer which starts at the first "no data" instance: if no data is received for longer thandata_timeout_sseconds continuously, anERROR-level message is logged. The timer is reset whenever data is received again.Testing details