[Feature]: Required changes once daphne v2 is discontinued
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 0
- Forks
- 1
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 7
Description
Description
The current DaphneApplication supports both v2 and mezzanine boards. This makes the schema a bit fragile: for example
- a DaphenApplication without hermes configuraiton is valid
- There are plenty of objects that refer to v2
The code and the schema should be clean up when the v2 line is discontinued.
Potential impact radius
Medium
Reason for change
We know that eventually Daphne v2 will be discontinued.
Suggested implementations
This list is not comprehensive at the time of writing and it will grow over time.
- Allow only Network Detector to Daq connections in the DaphneApplications
- Require one Hermes configuration at least
- Clean up the configuration object names from v2
Testing suggestions
Running correctly with Daphne v3.
Anything else?
No response
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 locating the DaphneApplication schema and configuration definitions, then identify the objects that still refer to v2 and the validation paths used for Daphne v3. Done means the schema permits only Network Detector to DAQ connections, requires at least one Hermes configuration, and removes obsolete v2 configuration names while running successfully with Daphne v3.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100