# HYPE Model Documentation

### Site Tools

start:hype_file_reference:branchdata.txt

# Differences

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

 start:hype_file_reference:branchdata.txt [2017/09/29 09:49]cpers start:hype_file_reference:branchdata.txt [2021/06/15 15:26] (current)cpers Both sides previous revision Previous revision 2021/06/15 15:26 cpers 2019/03/07 09:48 cpers [Table] 2017/11/08 16:35 cpers 2017/11/08 16:32 cpers 2017/09/29 09:49 cpers 2016/10/28 10:54 cpers 2015/07/15 08:51 cpers 2015/03/26 14:56 rcapell 2015/03/26 13:52 rcapell created Next revision Previous revision 2021/06/15 15:26 cpers 2019/03/07 09:48 cpers [Table] 2017/11/08 16:35 cpers 2017/11/08 16:32 cpers 2017/09/29 09:49 cpers 2016/10/28 10:54 cpers 2015/07/15 08:51 cpers 2015/03/26 14:56 rcapell 2015/03/26 13:52 rcapell created Line 1: Line 1: ====== BranchData.txt ====== ====== BranchData.txt ====== - This file contains all bifurcations within a HYPE model domain. Bifurcations are stream splits in downstream direction. They can occur naturally, but are often used in HYPE to describe inter-catchment water transfers for e.g. hydropower production. HYPE allows to split water flows by fixed fractions (''​mainpart''​) and optionally to define minimum and maximum flow limits. Another way to determine branch flow is through lakes with two outlets defined in [[start:​hype_file_reference:​lakedata.txt|LakeData.txt]]. Then only the path of the branch is necessary to give in BranchData.txt,​ but ''​mainpart''​ can also be given. It is used to calculate the upstream area of the subbasin, which in turn is used for calculating initial volume of main river, general rating curve parameters, upstream-area-output variables etc. + This file contains all bifurcations within a HYPE model domain. Bifurcations are stream splits in downstream direction. They can occur naturally, but are often used in HYPE to describe inter-catchment water transfers for e.g. hydropower production. HYPE allows to split water flows by fixed fractions (''​mainpart''​) and optionally to define minimum and maximum flow limits. Another way to determine branch flow is through lakes with two outlets defined in [[start:​hype_file_reference:​lakedata.txt|LakeData.txt]]. Then only the path of the branch is necessary to give in BranchData.txt,​ but ''​mainpart''​ can also be given. It is used to calculate the upstream area of the subbasin, which in turn is used for calculating initial volume of main river, general rating curve parameters, upstream-area-output variables etc. A third way to define branch flow is by prescribing a constant or a time series of the wanted flow. Line 26: Line 26: <​sortable>​ <​sortable>​ - ^ Variable ID ^ Unit ^ Description ^ + ^ Variable ID     ​^ Unit                 ​^ Description ​                                                                                                                                                                                       ^ - |''​sourceid''​|//​-//​|SUBID of sub-basin with bifurcation,​ i.e. with two downstream sub-basins| + | ''​sourceid'' ​   | //-//                | SUBID of sub-basin with bifurcation,​ i.e. with two downstream sub-basins ​                                                                                                                          ​| - |''​branchid''​|//​-//​|SUBID of sub-basin receiving the second branch flow, must be located in a row below the sub-basin with bifurcation in [[start:​hype_file_reference:​geodata.txt|GeoData.txt]]| + | ''​branchid'' ​   | //-//                | SUBID of sub-basin receiving the second branch flow, must be located in a row below the sub-basin with bifurcation in [[start:​hype_file_reference:​geodata.txt|GeoData.txt]] ​                       | - |''​mainpart''​|//​-//​|fraction of flow from subbasin sourceid that flows in the main branch (as given in column //​maindown//​ in [[start:​hype_file_reference:​geodata.txt|GeoData.txt]]) (between 0 and 1). Default is 1.| + | ''​mainpart'' ​   | //-//                | fraction of flow from subbasin sourceid that flows in the main branch (as given in column //​maindown//​ in [[start:​hype_file_reference:​geodata.txt|GeoData.txt]]) (between 0 and 1). Default is 1.  | - |''​maxQmain''​|//​m<​sup>​3/​s//​|maximum flow that is allowed in the main branch. Use 0 for no limitation or exclude column completely.| + | ''​maxQmain'' ​   | //​m<​sup>​3/​s// ​ | maximum flow that is allowed in the main branch. Use 0 for no limitation or exclude column completely. ​                                                                                            ​| - |''​minQmain''​|//​m<​sup>​3/​s//​|minimum flow that is required in the main branch before water is routed into branch. Use 0 for no limitation or exclude column completely.| + | ''​minQmain'' ​   | //​m<​sup>​3/​s// ​ | minimum flow that is required in the main branch before water is routed into branch. Use 0 for no limitation or exclude column completely. ​                                                        ​| - |''​maxQbranch''​|//​m<​sup>​3/​s//​|maximum flow that is allowed in the branch. Use 0 for no limitation or exclude column completely.| + | ''​maxQbranch'' ​ | //​m<​sup>​3/​s// ​ | maximum flow that is allowed in the branch. Use 0 for no limitation or exclude column completely. ​                                                                                                 | + | ''​Qbranch'' ​    | //-//                | the flow of the branch is prescribed; 0 (default) not use, 1 read flow from Xobs.txt (''​dwtr''​) ​                                                                                                       ​|
start/hype_file_reference/branchdata.txt.1506671386.txt.gz · Last modified: 2017/09/29 09:49 by cpers