DUNE-DAQ / DUNE-DAQ/daqsystemtest
[Enhancement]: extend the new configuration-validation script to support more than just the example configs
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 9
Description
Description
Eric recently created a script to check that configuration sessions are complete and self-consistent. (DUNE-DAQ/daqsystemtest#267 and DUNE-DAQ/daqsystemtest#285)
He and I recognized that this script can be extended to accept user-supplied top-level configuration file(s) and probably used on ehn1-daqconfigs. This Issue is a placeholder to look into that.
Potential impact radius
Small/Isolated
Reason for change
Expand the range of this script so that its usefulness will have wider impact.
Suggested implementations
User-supplied top-level configuration files seems like it might be a useful option.
Testing suggestions
It would be great to demonstrate the running of the enhanced script on ehn1-daqconfigs as well as example configs.
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 configuration-validation script and the example configurations introduced in DUNE-DAQ/daqsystemtest#267 and #285. Trace how top-level configuration files are selected, then define and implement support for user-supplied files; done means the script validates both example configs and ehn1-daqconfigs as requested.
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
- Needs clarification
- Newbie friendliness
- 35/100