Write a check_config.py with basic config assertions
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 615
- Forks
- 459
- Avg merge
- 4d 14h
- Merged PRs (30d)
- 6
Description
After tackling some issues with the spatial and temporal cutout bounds, it seemed sensible to add a dedicated script which reviews the config and basic ressources created during the work flow.
To start with: we should add an assertion for the following for
- all snapshots of the base.nc being in the cutout time selection
- the whole spatial area is covered be the cutout.bounds
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
Create check_config.py to review the configuration and basic workflow resources. Start by locating the config, base.nc snapshots, cutout time selection, and cutout.bounds; define completion as assertions that every base.nc snapshot is within the selected time range and that the cutout bounds cover the whole spatial area.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100