Replace extract in `monsoon` assessment area with `standardise_model_data`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5
- Forks
- 3
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 8
Description
By updating the `monsoon` assessment area scripts to use the output from CDDS would more easily enable the conversion of the script to ESMValTool.
Ensure a single `variables.txt` is used for each dataset/runid and *not* per area assessment. This is currently being done in ESMValTool recipes and should stick with this approach going forward.
Contributor guide
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 monsoon assessment area scripts and the existing extract usage, then compare their inputs with the CDDS output and the standardise_model_data approach. Check how ESMValTool recipes create variables.txt, and consider the work done when each dataset/runid uses one variables.txt rather than one per assessment area.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100