-
Notifications
You must be signed in to change notification settings - Fork 10
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
single set of cascades for HRUs and GWRs #18
Comments
Should this always be done? Is there any model where we wouldn't want them to be the same? |
Also, does this mean we can exclude all gw cascade parameters in the param file (i.e. gw_down_id, gw_pct_up, gw_strmseg_down_id, gw_up_id) and the n |
Yes, as long as there are no swales!
… On Oct 17, 2018, at 3:34 PM, Charles Morton ***@***.***> wrote:
Also, does this mean we can exclude all gw cascade parameters in the param file (i.e. gw_down_id, gw_pct_up, gw_strmseg_down_id, gw_up_id) and the n
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
I think that in almost all cases we can have the cascades be the same. There may be that special case but they can always run CRT outside of the scripts for this.
… On Oct 17, 2018, at 3:34 PM, Charles Morton ***@***.***> wrote:
Also, does this mean we can exclude all gw cascade parameters in the param file (i.e. gw_down_id, gw_pct_up, gw_strmseg_down_id, gw_up_id) and the n
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In order to specify a single set of cascade parameters for both HRUs and GWRs simply set cascadegw_flag=2. Then only cascades parameters for HRUs are required..
The text was updated successfully, but these errors were encountered: