Continue config validation iteration
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 13
- Forks
- 3
- Avg merge
- 19h 43m
- Merged PRs (30d)
- 1
Description
Description
DynODE configuration will continue to require model verification systems to assert that everything within the base configuration classes matches up. However, as DynODE continues to become more specific (COVID / Flu / RSV) etc. Certain aspects of configuration may only apply to these fields.
- Continue to add further verification of the model across base components
- Research and decide on pattern to verify custom config components built for disease-specific dynode implementations.
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 base configuration classes and existing model-verification logic, then review the disease-specific DynODE configuration components. Research a validation pattern for custom components and extend verification across the relevant configurations; done means base and disease-specific settings are consistently checked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100