DUNE-DAQ / DUNE-DAQ/fdreadoutlibs
Investigate different ways of handling late-arriving TPs at tp_datalinkhandlers
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 0
- Forks
- 3
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 5
Description
As mentioned in PR 150, we have implemented one way of warning users when TPs arrive "too late" at the tp_datalinkhandler, and therefore are not sent downstream to the Trigger.
However, as discussed at the 06-Dec-2023 Core Software meeting, it would be great to investigate ways to handle the situation differently. For example, maybe there is a way to never send out TPSets until all expected TPs arrive.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading PR 150 and the discussion from the 06-Dec-2023 Core Software meeting, then inspect the tp_datalinkhandler behavior described there. Compare ways to handle late-arriving TPs, including waiting for expected TPs before sending TPSets, and document a concrete recommended approach and its effects on downstream Trigger delivery.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100