eWaterCycle / eWaterCycle/ewatercycle

Premade forcings in a configured directory

Open
#248 2 comments 0 reactions 0 assignees View on GitHub
forcing
Dominant language
Python
Stars
41
Forks
6
Avg merge
8d 23h
Merged PRs (30d)
2

Description

We have prepared several forcings for use in example notebooks. It would be nice if we could have a central location where those forcing could be read from. Similar to parameter set it would be nice if I could do

```python
import ewatercycle.forcing
ewatercycle.forcing.available_forcings()
[
'marrmot-m01_example_1989-1992_buffalo-river',
'marrmot-m01_ERA5_1990-2001_savannah',
'wflow_ERA5_1990-2001_merrimack'
]
forcing = ewatercycle.forcing.load('marrmot-m01_ERA5_1990-2001_savannah')
model = MarrmotM01('2020.11', forcing)
```

I expect `ewatercycle.forcing.load()` method when given a relative path to look in current working directory and if not there also check in `CFG['forcing_root_dir']`

The ewatercycle.yaml could have following key/value:
```yaml
forcing_root_dir: /mnt/data/forcing
```

It could be nice to have multiple `forcing_root_dir` directories to organize things better.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.