Strategy for handling cell_methods
- Dominant language
- Python
- Stars
- 33
- Forks
- 19
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 30
Description
### Something else
General approach to variables with `cell_methods` in CSET, i.e. time-mean quantities, or max-in-hour temperature.
Our standard approach is to filter these out in recipes and ignore them, looking for cell methods [].
Two problems that we will rapidly face;
- RAL4 and screen_temperature max/min in hour; which will need handling (including appropriate ways to specify in GUI names). We can probably relax the cellmethods constraint do some more clever filtering in read.py for wanted variables.
- FastNetUK, and general precipitation aggregation to 6 hourly or similar, as done in the RES, and for broader model/obs comparisons
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the recipe handling and read.py logic that filters for empty cell_methods, then inspect how variable names are exposed in the GUI. Work through the RAL4 and screen_temperature hourly extrema cases and the FastNetUK or broader precipitation aggregation case; done should define a clear strategy for selecting and naming these quantities.
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
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100