-
Notifications
You must be signed in to change notification settings - Fork 17
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
Add some PREVAH functionalities to H-Land #67
Comments
I cannot find any hints in the literature, how PREVAH represents water bodies. For now, I assume they are "internal lakes", which are strongly connected to groundwater (as in HBV96). Hence, I add their precipitation to and remove their evaporation from the slow response groundwater reservoir. Thereby, I assume that the same areal fraction (1/9 vs 8/9) holds. Regarding negative groundwater stages due to intense evaporation, I tend to allow it similarly like in H-Land Version 1. |
HBV96 and PREVAH both differentiate a subbasin into hydrological response units. However, HBV96 does this only for the interception and the soil module. The upper and the lower soil storage are scalar values that apply to the whole subbasin. The reasoning is that we can assume one homogeneous groundwater aquifer for a whole subbasin (more precisely: one aquifer for the upper and one for the lower groundwater). On the other hand, PREVAH applies the HRU concept also "below" the soil. For now, I tend to the following compromise: I define the upper zone reservoir and the fast response reservoir on the HRU level but both slow response reservoirs on the subbasin level. In this way, we can keep the differences in the nonlinear soil water dynamics intended by PREVAH. And we have one connected deep groundwater aquifer (or actually two of them), allowing for the HBV96-like representation of internal lakes (discussed above). I think defining subbasin-wide slow response reservoirs does not imply great differences to PREVAH because they are implemented as simple linear storages. However, I am still not familiar with all details, so maybe I miss something. |
If I understand correctly, PREVAH always uses "1h" as its internal simulation time step. HBV96 instead has a more variable time step mechanism, but this only concerns the upper zone storage and not, for example, the interception storage. For now, I ignore this issue and assume all PREVAH equations also work well for other time steps. We should discuss this later. |
The PREVAH documentation says that surface flow and interflow calculate as follows:
But then, updating
Possible solutions:
Solution 4 seems to be the most elegant one. For complete safety, we could combine it with solution 2. |
Regarding groundwater storage and the generation of base flow, the text and the equations of the PREVAH documentation seem to be not in sync (section 4.5.2). I think the equations are more up-to-date, so I prefer to follow them. Also, the documentation states that "SG1Max is not exceeded (by SG1) during the time step". However, the given equation does not strictly ensure this (for unrealistically low values of
Possible solutions:
I go with a combination of solution 1 and 3. The smoother solution 2 would only be reasonable when addressing an expected model behaviour. |
The suspect PREVAH does not use the groundwater discharge differential equations mentioned in its documentation directly (e.g. |
HBV96 allows for a capillary rise from the upper groundwater ( |
…epts from HB96 and PREVAH (closes #67). (work in progress) We still need to: * write the documentation of the application model * add a figure This commit also tidies up the general documentation on `hland`, trying to keep everything consistent.
…epts from HB96 and PREVAH (closes #67). (work in progress) We still need to: * write the documentation of the application model * add a figure This commit also tidies up the general documentation on `hland`, trying to keep everything consistent.
…epts from HB96 and PREVAH (closes #67). (work in progress) We still need to: * write the documentation of the application model * add a figure This commit also tidies up the general documentation on `hland`, trying to keep everything consistent.
…epts from HB96 and PREVAH (closes #67). (work in progress) We still need to: * write the documentation of the application model * add a figure This commit also tidies up the general documentation on `hland`, trying to keep everything consistent.
…epts from HB96 and PREVAH (closes #67). (work in progress) We still need to: * write the documentation of the application model * add a figure This commit also tidies up the general documentation on `hland`, trying to keep everything consistent.
…epts from HB96 and PREVAH (closes #67). (work in progress) We still need to: * write the documentation of the application model * add a figure This commit also tidies up the general documentation on `hland`, trying to keep everything consistent.
…epts from HB96 and PREVAH (closes #67). (work in progress) We still need to: * write the documentation of the application model * add a figure This commit also tidies up the general documentation on `hland`, trying to keep everything consistent.
So far (HydPy-Version 4.0), we derived only a single application model from the H-Land model family. H-Land Version 1 is a very close emulation of the HBV96 model. We now start to implement some additional application models, which rely on concepts of other HBV clones.
We first focus on PREVAH. Our goal is to implement a new application model that mostly works like H-Land Version 1 but replaces the HBV96-like upper and the lower zone layer with the corresponding PREVAH concepts.
This issue serves as a notebook to record our design decisions and open questions.
The text was updated successfully, but these errors were encountered: