Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce dummy basins #72

Open
TillF opened this issue Jan 3, 2019 · 1 comment
Open

Introduce dummy basins #72

TillF opened this issue Jan 3, 2019 · 1 comment

Comments

@TillF
Copy link
Owner

TillF commented Jan 3, 2019

Is your feature request related to a problem? Please describe.
Virtual / dummy basins can help to establish check-points (e.g. up and downstream of reservoirs). We can have them already, but internally they need meteo data and geo-parameterization, thus, CPU time and storage.

Describe the solution you'd like
Subbasins specified in routing.dat, but without any LUs do not need climate series (or vice versa).

TillF added a commit that referenced this issue Jan 4, 2019
ENH:
- skip soilwater calculations for subbasins with area=0 (may be useful when specifying dummy basins, see #72)
- update docu
@MelwinQ
Copy link

MelwinQ commented Aug 20, 2020

Currently, dummy-basins can be realized by pre-specifying outflow in subbasin_out.dat. In this case, they don't require climate input, nor parameters in response.dat. However, they still need to be listed in soil_vegetation.dat. This should be eliminated.
Potentially flagging a dummy basin (e.g. in hymo.dat?) could also eliminate the need for pre-specifying outflow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants