MetOffice / MetOffice/CSET

Aggregation for impact-based diagnostics

Open
#1,592 0 comments 0 reactions 0 assignees View on GitHub
enhancement question
Dominant language
Python
Stars
33
Forks
19
Avg merge
1d 22h
Merged PRs (30d)
30

Description

### What problem does your feature request solve?

Some of the impact-based diagnostics will require aggregation, whereas others will make less sense if they are aggregated. This issue is raised to aggregate the diagnostics once they have been created to help determine which ones ones (and how) they should be aggregated.

### Describe the solution you'd like

A range of recipes added to the GUI to allow for specific diagnostics listed in this issue to be aggregated in a physically sensible way.

### Describe alternatives you've considered

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue names no files, tests, or specific diagnostics. Start by locating the GUI recipe system and the code that creates impact-based diagnostics, then identify which diagnostics need aggregation and how their aggregation should be defined. Done means the selected diagnostics can be aggregated through the GUI using physically sensible recipes.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.