Impact Based Diagnostics
- Dominant language
- Python
- Stars
- 33
- Forks
- 19
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 30
Description
To make the model evaluations useful for users we should consider a range of impact-based diagnostics for factors that are important to users/customers. This is the super-ticket which monitors the progress.
For anyone contributing to diagnostics for these issues please ensure that @daflack is included as a reviewer.
All impact-based diagnostics should be added to the relevant section in the `Derived Diagnostics` section of CSET (indicated in their respective issues). Furthermore, in the descriptor for the GUI please ensure to start with `IMPACT-BASED DIAGNOSTIC` to make it clear to users that this is an impact-based diagnostic.
Please feel free to add further impact-based diagnostics to this issue as sub-issues.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the proposed sub-issues and the `Derived Diagnostics` section of CSET. Each diagnostic should address an identified user or customer impact, appear in the relevant section, and have a GUI descriptor beginning with `IMPACT-BASED DIAGNOSTIC`; include @daflack as a reviewer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- analytics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100