User Tools

Site Tools


start:hype_file_reference:branchdata.txt

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
start:hype_file_reference:branchdata.txt [2017/11/08 16:35]
cpers
start:hype_file_reference:branchdata.txt [2019/03/07 09:48] (current)
cpers [Table]
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</​sup>/​s//​|maximum flow that is allowed in the main branch. Use 0 for no limitation or exclude column completely.| +| ''​maxQmain'' ​   | //​m<​sup>​3</​sup>/​s// ​ | maximum flow that is allowed in the main branch. Use 0 for no limitation or exclude column completely. ​                                                                                            ​
-|''​minQmain''​|//​m<​sup>​3</​sup>/​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</​sup>/​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</​sup>/​s//​|maximum flow that is allowed in the branch. Use 0 for no limitation or exclude column completely.| +| ''​maxQbranch'' ​ | //​m<​sup>​3</​sup>/​s// ​ | maximum flow that is allowed in the branch. Use 0 for no limitation or exclude column completely. ​                                                                                                 
-|''​Qbranch''​|//​m<​sup>​3</​sup>/​s//​|the ​prescribed ​flow is taken from the outflow ​of the subbasin; 0 (default) not used>0 = wanted constant water flow in the branch, -read from [[start:​hype_file_reference:​xobs.txt|Xobs.txt]] (''​dwtr''​) |+| ''​Qbranch'' ​    ​| //-//                | the flow of the branch is prescribed; 0 (default) not use, 1 read flow from Xobs.txt (dwtr) ​                                                                                                       |
 </​sortable>​ </​sortable>​
start/hype_file_reference/branchdata.txt.txt · Last modified: 2019/03/07 09:48 by cpers