User Tools

Site Tools


start:hype_model_description:hype_routing

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
start:hype_model_description:hype_routing [2023/11/16 14:28]
127.0.0.1 external edit
start:hype_model_description:hype_routing [2024/01/25 11:37] (current)
Line 705: Line 705:
 Outflow from a subbasin may flow in one or two directions. The main flow follows the main channel, which is the downstream subbasin given by the path in [[start:​hype_file_reference:​geodata.txt|GeoData.txt]]. If there is a bifurcation,​ the branch flow goes to another downstream subbasin (with subid //​branchid//​). Any of the flows may go outside the model set-ups area, they are then no longer a concern of the model. ​ Outflow from a subbasin may flow in one or two directions. The main flow follows the main channel, which is the downstream subbasin given by the path in [[start:​hype_file_reference:​geodata.txt|GeoData.txt]]. If there is a bifurcation,​ the branch flow goes to another downstream subbasin (with subid //​branchid//​). 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 prescribed (//​Qbranch//​). 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. +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 prescribed (//​Qbranch//​). The prescribed flow can be constant and set in BarnchData.txt or variable and given in Xobs.txt (''​dwtr''​). 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 total outflow has been calculated the ordinary way. The flows division into the two channels is the determined by four parameters; //​mainpart//,​ //​maxQ<​sub>​main</​sub>//,​ //​minQ<​sub>​main</​sub>//​ and //​maxQ<​sub>​branch</​sub>//,​ which are set in [[start:​hype_file_reference:​branchdata.txt|BranchData.txt]]. Zero values of the input data mean they are not used. The main flow (//​mainflow//​) is calculated from the totalflow (//q//) as:  For the first method the total outflow has been calculated the ordinary way. The flows division into the two channels is the determined by four parameters; //​mainpart//,​ //​maxQ<​sub>​main</​sub>//,​ //​minQ<​sub>​main</​sub>//​ and //​maxQ<​sub>​branch</​sub>//,​ which are set in [[start:​hype_file_reference:​branchdata.txt|BranchData.txt]]. Zero values of the input data mean they are not used. The main flow (//​mainflow//​) is calculated from the totalflow (//q//) as: 
start/hype_model_description/hype_routing.txt ยท Last modified: 2024/01/25 11:37 (external edit)