Evaluate the shared memory interplay between "broadcast," "reliable," "overwrite" and "drop" design/functionality (and corresponding fcl config) - Githubissues

art-daq / artdaq

Other

0 stars 3 forks source link

Evaluate the shared memory interplay between "broadcast," "reliable," "overwrite" and "drop" design/functionality (and corresponding fcl config) #71

Closed eflumerf closed 2 years ago

eflumerf commented 2 years ago

This issue has been migrated from https://cdcvs.fnal.gov/redmine/issues/20442 (FNAL account required) Originally created by @ron003 on 2018-07-25 19:07:33

It seems the subrun message is currently broadcast - unreliable - overwrite and it clobbers a previous reliable data fragment.

Related issues:

https://cdcvs.fnal.gov/redmine/issues/20403 (FNAL account required)
https://github.com/art-daq/artdaq/issues/48

Related issues:

https://cdcvs.fnal.gov/redmine/issues/20403 (FNAL account required)
https://github.com/art-daq/artdaq/issues/48

eflumerf commented 2 years ago

Comment by @eflumerf on 2018-09-19 18:12:38

The fix for this was to change broadcasts to use the reliable channel. This change was on artdaq's develop branch.