-
Notifications
You must be signed in to change notification settings - Fork 18
Description
At the moment, no application model based on HydPy-Dam considers water losses due to evaporation or withdrawal. Instead, other model instances (in our current projects, usually of HydPy-L-Land) connected to the HydPy-Dam instances need to perform this task. We borrowed this strategy from LARSIM, but in HydPy, it complicates the coupling of different model types.
Regarding evaporation, we could either let HydPy-Dam calculate everything on its own or let other models like HydPy-Evap provide potential evaporation and let HydPy-Dam just adjust it.
Regarding water withdrawal, there are the options to either demand full time-series of requested withdrawal or to let the user define seasonally varying requested withdrawal via a parameter derived from class SeasonalParameter.