Add verification of session connections consistency in configuration
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 5
- Avg merge
- 12h 53m
- Merged PRs (30d)
- 7
Description
All DAQ applications network endpoints in DAQ systems are supposed to have one or more endpoints to establish connections. The presence of unmatched network endpoints in a system configuration could lead to warnings, error or, if not properly handled, to crashes and non-deterministic behaviour.
Unmatched or dangling endpoints can be detected with the following steps
- Loop over applications in a session
- Gather the input and output network endpoints for all modules
- if the application is a
SmartDaqApplication, generate the list of modules, and then gather
- if the application is a
- Match inputs and outputs across applications
- List non-connected endpoints
- Raise warning/errors appropriately
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
No files, tests, or entry points are named. Start by tracing how session applications and SmartDaqApplication modules are represented, then follow the existing configuration validation path. Done means unmatched input and output network endpoints are identified and appropriate warnings or errors are raised without leaving dangling connections.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100