start:hype_model_description:hype_routing
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
start:hype_model_description:hype_routing [2018/06/12 10:05] cpers [Bifurcations] |
start:hype_model_description:hype_routing [2018/08/10 15:49] cpers [Common rivers processes] |
||
|---|---|---|---|
| Line 66: | Line 66: | ||
| The delay in the watercourse (//transtime//) in days is determined by the length of the watercourse (//rivlen//) and the water’s maximum velocity (//rivvel//). The maximum velocity is a general parameter with unit //m/s//. The delay in the local river is dependent on subbasin size, as stream length calculated from its area. The delay is a pure translation. The delay is divided into whole days (//ttday//) and parts of the day (//ttpart//). | The delay in the watercourse (//transtime//) in days is determined by the length of the watercourse (//rivlen//) and the water’s maximum velocity (//rivvel//). The maximum velocity is a general parameter with unit //m/s//. The delay in the local river is dependent on subbasin size, as stream length calculated from its area. The delay is a pure translation. The delay is divided into whole days (//ttday//) and parts of the day (//ttpart//). | ||
| - | <m> transtime = rivlen/{rivvel~8.64~10^4} </m> | + | <m> transtime = rivlen/{rivvel*8.64*10^4} </m> |
| <m> ttday = INT(transtime) </m> | <m> ttday = INT(transtime) </m> | ||
| Line 523: | Line 523: | ||
| ===== Bifurcations ===== | ===== Bifurcations ===== | ||
| - | Outflow from a subbasin may flow in one or two directions. The main flow follows the main channel, which is the downstream subbasin described by the path given in [[start:hype_file_reference:geodata.txt|GeoData.txt]]. If there is a bifurcation, the branch flow goes to another downstream subbasin. Any of the flows may go outside the model set-ups area, they are then no longer a concern of the model. There are three ways to determine the flow in the different channels. 1) The division of the total outflow is determined in BranchData.txt. 2) The outflow is calculated for two outlets separately and then divided into the channels. For the second alternative see [[start:hype_model_description:hype_routing#outlet_lake_with_two_outlets|Outlet lake with two outlets]] section above. 3. The demanded flow in the branch is prescibed. If the total flow is not enough to fulfil the need, less water goes into the branch. The main channel gets the rest of the total flow. For the first method the flow division into two channels by BranchData.txt is described by four parameters; //mainpart//, //maxQ<sub>main</sub>//, //minQ<sub>main</sub>// and //maxQ<sub>branch</sub>//, which is set in [[start:hype_file_reference:branchdata.txt|BranchData.txt]]. Zero values of the parameters mean they are not used. The main flow (//mainflow//) is calculated from the totalflow (//q//) as: | + | Outflow from a subbasin may flow in one or two directions. The main flow follows the main channel, which is the downstream subbasin described by the path given in [[start:hype_file_reference:geodata.txt|GeoData.txt]]. If there is a bifurcation, the branch flow goes to another downstream subbasin. Any of the flows may go outside the model set-ups area, they are then no longer a concern of the model. There are three ways to determine the flow in the different channels. 1) The division of the total outflow is determined in BranchData.txt. 2) The outflow is calculated for two outlets separately and then divided into the channels. For the second alternative see [[start:hype_model_description:hype_routing#outlet_lake_with_two_outlets|Outlet lake with two outlets]] section above. 3) The demanded flow in the branch is prescibed. If the total flow is not enough to fulfil the need, less water goes into the branch. The main channel gets the rest of the total flow. For the first method the flow division into two channels by BranchData.txt is described by four parameters; //mainpart//, //maxQ<sub>main</sub>//, //minQ<sub>main</sub>// and //maxQ<sub>branch</sub>//, which is set in [[start:hype_file_reference:branchdata.txt|BranchData.txt]]. Zero values of the parameters mean they are not used. The main flow (//mainflow//) is calculated from the totalflow (//q//) as: |
| <m> mainflow = delim{lbrace}{matrix{4}{2}{q {q<=minQ_main} {mainpart×(q-minQ_main)+minQ_main} {minQ_main<q<=q_thresh} {maxQ_main} {q>q_thresh \,\ q_thresh={{maxQ_main-minQ_main}/{mainpart}}+minQ_main} {q-maxQ_branch} {q>q_thresh\ ,\ q_thresh={{maxQ_branch}/{1-mainpart}}+minQ_main}}}{} </m> | <m> mainflow = delim{lbrace}{matrix{4}{2}{q {q<=minQ_main} {mainpart×(q-minQ_main)+minQ_main} {minQ_main<q<=q_thresh} {maxQ_main} {q>q_thresh \,\ q_thresh={{maxQ_main-minQ_main}/{mainpart}}+minQ_main} {q-maxQ_branch} {q>q_thresh\ ,\ q_thresh={{maxQ_branch}/{1-mainpart}}+minQ_main}}}{} </m> | ||
start/hype_model_description/hype_routing.txt · Last modified: 2024/01/25 11:37 (external edit)
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
