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 [2019/08/28 13:37]
cpers [Outlet lake with two outlets]
start:hype_model_description:hype_routing [2020/04/30 09:03] (current)
cpers [Links to relevant modules in the code]
Line 11: Line 11:
 The two lake types are separate classes. The lake classes have characteristics such as land use and soil type, which are defined together with the other classes'​ characteristics (in GeoClass.txt). Precipitation,​ atmospheric deposition and evaporation of rivers and lakes are calculated first, while river flow and inflow, transformation processes and the outflow of the lakes is calculated thereafter. Lakes and rivers are calculated in the model’s routing part after all classes are calculated for the subbasin. ​ The two lake types are separate classes. The lake classes have characteristics such as land use and soil type, which are defined together with the other classes'​ characteristics (in GeoClass.txt). Precipitation,​ atmospheric deposition and evaporation of rivers and lakes are calculated first, while river flow and inflow, transformation processes and the outflow of the lakes is calculated thereafter. Lakes and rivers are calculated in the model’s routing part after all classes are calculated for the subbasin. ​
  
-An outlet lake can be part of a larger lake. It is then called a lake basin. Lake basins are olakes in nearby subbasins. Outlet lakes that are not lake basins are referred to below as simple outlet lakes+An outlet lake can be part of a larger lake. It is then called a lake basin. Lake basins are olakes in nearby subbasins. ​
  
-A simple outlet lake has a threshold. The outflow ends if the water level drops below the threshold. Lake mean depth below the threshold is specified in GeoData.txt or LakeData.txt as //​lake_depth//​ in meters. Lake depth can also be set by parameters, i.e general parameter //gldepo// or olake region parameter //​olldepth//​. The threshold is also the the water level of the lake at the start of a simulation. The current water level is denoted as //wlm// in Fig. 2. For printing, the outlet lake water level (output variable //wcom//) is calculated in meters and you can set a reference level (//w0ref//) in LakeData.txt to get the same height system as any observations of the lake's water level. The lake’s //w0ref// is added to the water level above the threshold. HYPE assumes the lake has vertical sides in the calculations,​ thus the observed variation may be larger than the simulated variation. It is therefore possible to adjust the output //wcom// for the actual amplitude of the regulation volume (//wamp//). This will make the simulated and recorded water stage comparable below the threshold for a regulated lake. +A simple outlet lake has a threshold. The outflow ends if the water level drops below the threshold. Lake mean depth below the threshold is specified in GeoData.txt or LakeData.txt as //​lake_depth//​ in meters. Lake depth can also be set by parameters, i.e general parameter //gldepo// or olake region parameter //​olldepth//​. The threshold is also the the water level of the lake at the start of a simulation. The current water level is denoted as //wlm// in Fig. 2. For printing, the outlet lake water level (output variable //wcom//) is calculated in meters and you can set a reference level (//w0ref//) in LakeData.txt to get the same height system as any observations of the lake's water level. The lake’s //w0ref// is added to the water level above the threshold. A regulated lake (dam) has two thresholds. One, same as for a simple lake, is used for spill, and one lower threshold were outflow ends completely. The distance between the thresholds are determined by the regulation volume. HYPE assumes the lake/dam has vertical sides in the calculations,​ thus the observed variation ​in water level may be larger than the simulated variation. It is therefore possible to adjust the output //​wcom// ​(and //​wcav//​) ​for the actual amplitude of the regulation volume (//wamp//). This will make the simulated and recorded water stage comparable below the threshold for a regulated lake. 
  
 |{{:​start:​hype_model_description:​outletlakewithvariables2.png?​400|}}| |{{:​start:​hype_model_description:​outletlakewithvariables2.png?​400|}}|
Line 19: Line 19:
  
 A local lake also has a threshold depth that is used as start value. The depth is given by general parameter //gldepi// and is then the same for all the local lakes, or by ilake region parameter //​illdepth//​. It is measured in meters. A percentage of flow from the local stream flows into the local lake. The rest of the local flow runs directly to main river watercourse. ​ A local lake also has a threshold depth that is used as start value. The depth is given by general parameter //gldepi// and is then the same for all the local lakes, or by ilake region parameter //​illdepth//​. It is measured in meters. A percentage of flow from the local stream flows into the local lake. The rest of the local flow runs directly to main river watercourse. ​
- 
-Using parameters, you can divide the lake into two parts, one with faster flows (FLP) and one with slower flows (SLP) (Figure 3). This function is used for the simulation of nutrients to simulate stratification,​ strangulation or other phenomena that may limit the mixing of a lake. With this feature, the flows through the lake follow the schedule below. The split is determined by the parameter //​deeplake//,​ which is the fraction of the lake's initial volume SLP, the remaining (varying) volume in the lake is the FLP. The parameter //​fastlake//​ determines where the outflow will be coming from. Default is that outflow is taken from the slow lake part. Increasing //​fastlake//​ will let the FLP contribute to outflow. //​Fastlake//​ equal to one gives the maximum contribution of FLP, and the outflow will be taken proportionally from the two lake parts according to their volume. 
- 
-|{{:​start:​hype_model_description:​division_of_lake.png?​400|}}| 
-|Figure 3: Division of a lake in two parts and water flows regarding lake.| 
  
 The streams may have a delay and an attenuation of the flow. The former shifts the peaks, but leaves them otherwise untouched, while the attenuation both delays and smooths out peaks. The streams have a dead volume in which the residence time of solutes is increased relative to the water and the concentration smoothed out further over time. The streams may have a delay and an attenuation of the flow. The former shifts the peaks, but leaves them otherwise untouched, while the attenuation both delays and smooths out peaks. The streams have a dead volume in which the residence time of solutes is increased relative to the water and the concentration smoothed out further over time.
Line 36: Line 31:
 |//gldepo, olldepth, gldepi, illdepth//​|[[start:​hype_file_reference:​par.txt|par.txt]]| |//gldepo, olldepth, gldepi, illdepth//​|[[start:​hype_file_reference:​par.txt|par.txt]]|
 |//w0ref, wamp//​|[[start:​hype_file_reference:​lakedata.txt|LakeData.txt]] or [[start:​hype_file_reference:​damdata.txt|DamData.txt]]| |//w0ref, wamp//​|[[start:​hype_file_reference:​lakedata.txt|LakeData.txt]] or [[start:​hype_file_reference:​damdata.txt|DamData.txt]]|
-|//​deeplake,​ fastlake//​|[[start:​hype_file_reference:​par.txt|par.txt]]|+
 ==== Links to relevant modules in the code ==== ==== Links to relevant modules in the code ====
  
Line 42: Line 37:
 | [[http://​hype.sourceforge.net/​doxy-html/​namespacemodelmodule.html|modelmodule (model_hype.f90)]]|initiate_model_state| | [[http://​hype.sourceforge.net/​doxy-html/​namespacemodelmodule.html|modelmodule (model_hype.f90)]]|initiate_model_state|
 | ::: |initiate_model | | ::: |initiate_model |
-| [[http://​hype.sourceforge.net/​doxy-html/​namespacesurfacewater__processes.html|surfacewater_processes (sw_proc.f90)]]|calculate_landarea_riverlength+| ::: |calculate_flow_from_undivided_lake| 
-| ::: |calculate_outflow_from_outlet_lake|+| ::: |calculate_flow_for_lakebasin_lake | 
 +| [[http://​hype.sourceforge.net/​doxy-html/​namespacesurfacewater__processes.html|surfacewater_processes (sw_proc.f90)]]| ​calculate_riverlength| 
 +| ::: | calculate_ilake_outflow ​
 +| ::: | calculate_outflow_from_outlet_lake ​
 +| ::: | calculate_outflow_from_lakebasin_lake ​|
 | ::: |remove_outflow_from_lake| | ::: |remove_outflow_from_lake|
-| ::: |calculate_flow_within_lake| 
 | ::: |calculate_branched_flow| | ::: |calculate_branched_flow|
-|[[http://​hype.sourceforge.net/​doxy-html/​namespacenpc__surfacewater__processes.html|npc_surfacewater_processes (npc_sw_proc.f90)]]|set_lake_slowwater_maxvolume |+
  
  
Line 73: Line 71:
 === Pure delay === === Pure delay ===
  
-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 river is dependent on subbasin land area if the default river length is used. 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 river is dependent on subbasin land area if the default river length is used. The delay is a pure translation. The delay is divided into whole days (//ttday//) and parts of the day (//ttpart//) (if the time step is daily, other wise the division is made into whole and fractions of that time step). In the following description daily time step is assumed.
  
 <m> transtime = rivlen/​{rivvel*8.64*10^4} </m> <m> transtime = rivlen/​{rivvel*8.64*10^4} </m>
Line 182: Line 180:
  
  
-Bank-full flow is used for erosion of particulate phosphorus in rivers (see Sedimentation). It is approximated by the second highest daily flow during the last year.+Bank-full flow is used for erosion of particulate phosphorus in rivers (see [[start:​hype_model_description:​hype_np_riv_lake#​sedimentation_resuspension|Sedimentation/​Resuspension]]). It is approximated by the second highest daily flow during the last year.
  
  
Line 198: Line 196:
 The flow in the main river is delayed and attenuated as described above. ​ The flow in the main river is delayed and attenuated as described above. ​
 The resulting effluent from the river flows to the outlet lake or to the next subbasin if there is no outlet lake.  The resulting effluent from the river flows to the outlet lake or to the next subbasin if there is no outlet lake. 
 +
 +If the main river length is zero, the inflows to the main river is added to form the main river outflow.
  
 === Inflow from upstream subbasins === === Inflow from upstream subbasins ===
  
-In input files it is given to which subbasin(s) the outflow from each subbasin flows. The upstream flow enters the main river of the downstream subbasin. Inflow into the main river of a subbasin is calculated by adding outflows from upstream areas. Concentrations are flow-weighted by their relative share. ​+In input files it is given to which subbasin(s) the outflow from each subbasin flows. The upstream flow enters the main river of the downstream subbasin. Inflow into the main river of a subbasin is calculated by adding outflows from upstream areas. Concentrations are flow-weighted by their relative share. The upstream flow enters the main river, except if the upstream subbasin has a lakebasin that is part of the downstream subbasin'​s lake. In this case the upstream lakebasin outflow goes directly into the downstream lakebasin.  
 + 
 +=== Hydraulic geometry and river rating curve === 
 + 
 +River diagnostic variables can be calculated for the main river. A river water depth (//d//) and river velocity (//u//) can be calculated from hydraulic geometry for the main river. The equation coefficients are general (//​c,​f,​k,​m//​). 
 + 
 +<m> d=c*q^f </​m>​ 
 + 
 +<m> u=k*q^m </​m>​ 
 + 
 +where //c,f,k// and //m// are given by general parameters.  
 + 
 +With a given rating curve for main river flow, the water level of the river (//wr//) can be calculated by the inverse of the rating curve. Basin dependent values for reference level (//w0//) and the rating curve coefficients are input. Two rating curves may be given for each  main river, one for general and ice free condition and one for use with ice on the river. The rating curve for ice conditions are only used if one is given for no ice conditions. 
 + 
 +<m> wr = wl + w0 </​m>​ 
 + 
 +<m> q=k*(wl-w0)^p </​m>​ 
 + 
 +give coefficients //c// and //f// for the inverse equation: 
 + 
 +<m> c={1/​k}^{1/​p} ​ f=1/p </​m>​ 
 + 
 +<m> wr = c*q^f+w0 </m>.
  
  
Line 214: Line 236:
 |Main river| |//​maindown//​|[[start:​hype_file_reference:​geodata.txt|GeoData.txt]]| |Main river| |//​maindown//​|[[start:​hype_file_reference:​geodata.txt|GeoData.txt]]|
 |:::| |//​branchid//​|[[start:​hype_file_reference:​branchdata.txt|BranchData.txt]]| |:::| |//​branchid//​|[[start:​hype_file_reference:​branchdata.txt|BranchData.txt]]|
 +|:::|//c, f, k, m// |//hygeomc, hygeomf, hygeomk, hygeomm//​|[[start:​hype_file_reference:​par.txt|par.txt]]|
 +|:::|//k, p, w0// |//​mrrivck_noi,​ mrrivck_ice,​ mrrivcp_noi,​ mrrivcp_ice,​ mrrivcw0//​|[[start:​hype_file_reference:​geodata.txt|GeoData.txt]]|
  
 ==== Links to relevant modules in the code ==== ==== Links to relevant modules in the code ====
Line 227: Line 251:
 |:::​|calc_qbank|bank-full flow| |:::​|calc_qbank|bank-full flow|
 |:::​|update_qbank |:::| |:::​|update_qbank |:::|
 +|:::​|river_water_level |main river| 
 +|:::​|ice_on_river|:::​|
  
  
Line 236: Line 261:
 === Precipitation === === Precipitation ===
  
-Daily precipitation is added to the lake and a new concentration is calculated. Lakes are assumed to be completely mixed if the parameter //​deeplake//​ is not set to a value greater than zero.+Daily precipitation is added to the lake and a new concentration is calculated. Lakes are assumed to be completely mixed.
  
 === Evaporation === === Evaporation ===
  
-The lake is assumed to evaporate and a new concentration calculated.+The lake is assumed to evaporate ​at potential evaporation rate (see [[start:​hype_model_description:​processes_above_ground#​evaporation|Processes above ground - Evaporation]]) ​and a new concentration calculated. The actual evaporating area is reduced if the lake is (partly) ice covered. Ice is calculated in case water temperature (substance T2) is simulated.
  
 === Outflow with rating curve ==== === Outflow with rating curve ====
Line 253: Line 278:
 The local lake has an initial volume which is determined by its area and threshold depth. The lake depth is determined by model parameters (//gldepi// or //​illdepth//​)). ​ The local lake has an initial volume which is determined by its area and threshold depth. The lake depth is determined by model parameters (//gldepi// or //​illdepth//​)). ​
  
-The inflow to the lake is a percentage of the flow in the local stream (//​icatch//​). The percentage is determined by the percentage of the subbasin area that drain to the lake. This percentage can be given as a fraction in GeoData.txt for each subbasin with an internal lake, or be given by a regional parameter //​ilicatch//,​ or be given by a general parameter //​gicatch//​. If not set at all the default value is 1, i.e. the local river runs through the local lake. The flow from the local river is added to the lake. The lake water is assumed completely mixed if //deeplake = 0//+The inflow to the lake is a percentage of the flow in the local stream (//​icatch//​). The percentage is determined by the percentage of the subbasin area that drain to the lake. This percentage can be given as a fraction in GeoData.txt for each subbasin with an internal lake, or be given by a regional parameter //​ilicatch//,​ or be given by a general parameter //​gicatch//​. If not set at all the default value is 1, i.e. the local river runs through the local lake. The flow from the local river is added to the lake. The lake water is assumed completely mixed. ​
  
 Water outflow is calculated with the universal rating curve using general or region specific model parameters. Water outflow is calculated with the universal rating curve using general or region specific model parameters.
Line 287: Line 312:
  
 |{{:​start:​hype_model_description:​illustraion_of_regulation_flow.png?​400|}}| |{{:​start:​hype_model_description:​illustraion_of_regulation_flow.png?​400|}}|
-|Figure ​4: Illustration of regulation flow and variables.|+|Figure ​3: Illustration of regulation flow and variables.|
  
 For water levels above the threshold, the flow is calculated with a rating curve (typically flow through spillways) or all the water is discharged, but it is at least equal to the production flow (//​qprod//​). Compiled together as one equation, the outflow from a regulated lake is: For water levels above the threshold, the flow is calculated with a rating curve (typically flow through spillways) or all the water is discharged, but it is at least equal to the production flow (//​qprod//​). Compiled together as one equation, the outflow from a regulated lake is:
Line 365: Line 390:
 ==== Outlet lake with two outlets ==== ==== Outlet lake with two outlets ====
  
-An outlet lake that is not part of a lake composed of lakebasins, may have two defined outlets in [[start:​hype_file_reference:​lakedata.txt|LakeData.txt]]. The outlets can be divided into different outlet types depending on method for determining the outflow. HYPE will define an outlet'​s type based on variables present in [[start:​hype_file_reference:​lakedata.txt|LakeData.txt]]. Below the defining (necessary) variables are given for each outlet type.+An outlet lake that is not part of a lake composed of lakebasins, may have two defined outlets in [[start:​hype_file_reference:​lakedata.txt|LakeData.txt]]. The outlets can be divided into different outlet types depending on method for determining the outflow. HYPE will define an outlet'​s type based on variables present in [[start:​hype_file_reference:​lakedata.txt|LakeData.txt]]. Below the defining (necessary) variables are given for each outlet type. Note: The threshold (w0ref) is given for first outlet. For the second outlet this variable instead is given relative to the threshold of outlet 1 (i.e usually zero)
  
 === Outlet types === === Outlet types ===
Line 426: Line 451:
  
  
-==== Outlet lake (olake) ​as a lake basin ====+==== Outlet lake as a multi-basin lake composed of lake basins ​====
  
-An olake can be part of a larger lake. It is then called a lake basin of the larger lake. Lake basins ​are treated differently if they are located within the lake or if they are the last onei.e. the one with the lake outflow+An olake can be part of a larger lake. It is then called a lake basin of the larger ​multi-basin ​lake. A multi-basin lake is assumed to have equal water level in all lake basins. The lake basins can have different depths below the outflow thresholdand they all use the same threshold when the water level output is calculated (same reference).
  
 === Inflow === === Inflow ===
  
-A lake basin can get local inflow from upstream areas and from the regional groundwater. Inflow works in the same way as for a simple olake (see above).+A lake basin can get local inflow, ​inflow from upstream areas (that are not in the same multi-basin lake) and from the regional groundwater. Inflow works in the same way as for a simple olake (see above).
  
 === Flow between lake basins === === Flow between lake basins ===
  
-Flow through a lake divided into lake basins occurs ​only in one direction according to the //maindown// (and possibly ​//branchdown//), no two-way exchange between lake basins is implementedFor upstream ​lake basins ​that run into another ​lake basin, all the water above the threshold is drained. The threshold ​of the lake (same as last lake basin) ​is used, not any internal threshold ​between lake basins. If the lake water level (//​wlm//​) ​is higher than the threshold ​(//w0// or //wmin//) outflow is obtained.+Flow through a lake divided into lake basins ​can occurs in both direction according to the maindown (and possibly branchdown). ​The implementation prioritize flow from nearby ​lake basins ​and flow in the downstream direction when calculation the flow betweeen ​lake basins to reach the equal water level. No internal ​threshold ​between lake basins ​is considered when the flows are calculated 
 + 
 +The flow out of a lakebasin is determined in several steps: 
 +  - First the net outflow of each lakebasin ​is calculated. It is calculated as the difference ​between ​the current water level of the lakebasin and the water level of the whole lake after outflow from the lake. Thus the average ​water level of the lake is calculated and from this the outflow(sof the lake. Considering these outflows leaving the lake, a new average water level is calculated that the lake will have after all flows between lakebasins have been moved.  
 +  - The flow out of a lakebasin is the netflow plus all inflows from other lakebasins. The inflows are outflows of other lakebasins. Starting upstream in the lake the inflows are added to the outflow ​to give the flow out of every lakebasin. Note that these can be negative.  
 +  - The last step is to actually move the water. Preferably we want water to move from one lakebasin to the next, without mixing with water incoming from lakebasins further upstream. This we want so that substances do not travel all the way to the lake outlet on one time step. Therefore we try to remove all outflows from the lakebasins before we add the removed water into the downstream lakebasins. This might not be possible so we keep track of how much we can't move and repeat the third step if necessary 
  
 === Outflow of lake composed of lake basins === === Outflow of lake composed of lake basins ===
  
  
-For the last lake basin outflow is estimated by a rating curve, either a specific equation or with the general equation, or by regulation routine. ​Since all the water (above threshold) in the lake (from all lake basins) accumulates in the last lake basin the water level cannot be used directly, but it is recalculated to calculate the outflow from the lake. The last lake basin water level (//wlm//) is scaled by the subbasin lake area (//area//) to the whole lake area (//​lakearea//​). If the calculated lake water level (//wlake//) is higher than the threshold (//​wthresh//​) the outflow is estimated by the rating curve. +The main outflow of the lake is assumed to be located in the last lake basin. Here outflow is estimated by a rating curve, either a specific equation or with the general equation, or by regulation routine. The threshold may be changing over the year as described in Section Two rating curves above. If the water level is below the threshold then the outflow is zero or if the production flow regulation is used there is production flow. See Section Production flow above. ​In addition the lake can have branched outflows out of the multi-basin lake from other lakebasins. The branched outflows ​is specified in LakeData and can be a rating curve or a production flow that uses the same thresholds as the main outlet
- +
-  wlake = (wlm – wthresh) * area / lakearea + wthresh +
-  outflow = rate * (wlake – wthresh)**exp +
- +
-The threshold may be changing over the year as described in Section Two rating curves above. If the water level is below the threshold then the outflow is zero or if the production flow regulation is used there is production flow. See Section Production flow above. ​Production flow is also applied on the recalculated water stage.+
  
 ==== Initalisation of lake volume ==== ==== Initalisation of lake volume ====
  
-Unless a starting state is given from a file, the lakes start the simulation filled with water to their outflow threshold. That means for ilakes and simple olakes ​a water level equal to //​lake_depth//​. Dams are filled to the dam's maximum elevation (equal to //​lake_depth//​),​ except for flood control dams which are initializied with an empty regulation volume. ​+Unless a starting state is given from a file, the lakes start the simulation filled with water to their outflow threshold. That means for most lakes a water level equal to //​lake_depth//​. Dams are filled to the dam's maximum elevation (equal to //​lake_depth//​),​ except for flood control dams which are initializied with an empty regulation volume. ​
  
 For lakes with outflow determined by a rating curve, the water level of the lake will be higher than the outflow threshold level. The equilibrium level will depend on the size of the inflow and the outflow rating curve parameters. Depending on the residence time of water in the lake it may take time for this level to be established,​ and until then the outflow of the lake will be simulated lower than it should be. Thus a spin-up time is needed for a model simulation. For lakes with outflow determined by a rating curve, the water level of the lake will be higher than the outflow threshold level. The equilibrium level will depend on the size of the inflow and the outflow rating curve parameters. Depending on the residence time of water in the lake it may take time for this level to be established,​ and until then the outflow of the lake will be simulated lower than it should be. Thus a spin-up time is needed for a model simulation.
Line 458: Line 483:
  
 ^Section ^Symbol ^Parameter/​Data ^File ^ ^Section ^Symbol ^Parameter/​Data ^File ^
-|Common lake processes| |//​deeplake//​|[[start:​hype_file_reference:​par.txt|par.txt]]| 
 |Local lake (ilake)| |//gldepi, illdepth, gratk, gratp, grata, ilratk, ilratp//​|[[start:​hype_file_reference:​par.txt|par.txt]]| |Local lake (ilake)| |//gldepi, illdepth, gratk, gratp, grata, ilratk, ilratp//​|[[start:​hype_file_reference:​par.txt|par.txt]]|
 |:::​|//​icatch//​|//​icatch//​|[[start:​hype_file_reference:​geodata.txt|GeoData.txt]]| |:::​|//​icatch//​|//​icatch//​|[[start:​hype_file_reference:​geodata.txt|GeoData.txt]]|
Line 474: Line 498:
 |Outlet lake with two outlets| |//​ldtype//​=5 or 6|[[start:​hype_file_reference:​lakedata.txt|LakeData.txt]]| |Outlet lake with two outlets| |//​ldtype//​=5 or 6|[[start:​hype_file_reference:​lakedata.txt|LakeData.txt]]|
 |:::| |//w0ref, maxQprod, minflow, obsflow//​|:::​| |:::| |//w0ref, maxQprod, minflow, obsflow//​|:::​|
-|Outlet lake (olake) as a lake basin| |//​ldtype//​=2,​ 3 or 4|[[start:​hype_file_reference:​lakedata.txt|LakeData.txt]]| +
-|:::​|//​lakearea//​|//​area//​|:::​|+
  
 ==== Links to relevant modules in the code ==== ==== Links to relevant modules in the code ====
Line 484: Line 507:
 |::: |average_flow_rating_curve|ouflow with rating curve| |::: |average_flow_rating_curve|ouflow with rating curve|
 |::: |calculate_ilake_outflow|local lake| |::: |calculate_ilake_outflow|local lake|
-|::: |calculate_outflow_from_outlet_lake|simple outlet lake| 
-|::: |:::|outlet lake as a lakebasin| 
-|:::​|:::​|outlet lake with two outlets| 
 |:::​|set_general_rating_k|simple outlet lake| |:::​|set_general_rating_k|simple outlet lake|
-|:::|calculate_olake_waterstage|outlet lake as a lakebasin+|::: |calculate_outflow_from_outlet_lake calculate_branched_flow|simple ​outlet lake| 
-|:::|calculate_branched_flow|outlet lake with two outlets| +|:::|:::|outlet lake with two outlets| 
-|:::|calculate_branched_flow_new|:::|+|:::|calculate_lake_outlet_outflow|outlet lake with two outlets| 
 +|:::​|calculate_lakebasin_average_waterstage|outlet lake as multi-basin lake| 
 +|:::​|calculate_outflow_from_lakebasin_lake|:::​| 
 +|:::​|calculate_branched_flow|:::|
 |[[http://​hype.sourceforge.net/​doxy-html/​namespacemodelmodule.html|modelmodule (model_hype.f90)]] |initiate_model | local lake | |[[http://​hype.sourceforge.net/​doxy-html/​namespacemodelmodule.html|modelmodule (model_hype.f90)]] |initiate_model | local lake |
 +|::: |calculate_flow_from_undivided_lake|simple outlet lake|
 +|:::​|:::​|outlet lake with two outlets|
 +|::: |calculate_flow_for_lakebasin_lake|outlet lake as multi-basin lake|
  
 ==== References ==== ==== References ====
Line 501: Line 527:
  
 |{{:​start:​hype_model_description:​FloodScenarios.png?​400|}}| |{{:​start:​hype_model_description:​FloodScenarios.png?​400|}}|
-| Figure ​7: Five possible scenarios of flooding.|+| Figure ​4: Five possible scenarios of flooding.|
  
 ==== Common floodplain processes ==== ==== Common floodplain processes ====
Line 514: Line 540:
 <m> a_max = fpf * classarea ​ </m> <m> a_max = fpf * classarea ​ </m>
  
-|{{:​start:​hype_model_description:​FloodVarFlow.png?​400|}}| +| {{:​start:​hype_model_description:​FloodVarFlow.png?​400}} ​    ​
-| Figure ​8: Illustration of floodplain variables of a lake.|+| Figure ​5: Illustration of floodplain variables of a lake.  |
  
 The exchange of water between lake (or river) and floodplain is determined by the respective water levels (//​wl<​sub>​body</​sub>//​ and //​wl<​sub>​plain</​sub>//​),​ the equilibrium water level (//​wl<​sub>​equil</​sub>//​) and the thresholds between the water bodies (//​fl<​sub>​body</​sub>/​fl<​sub>​plain</​sub>//​). ​ The exchange of water between lake (or river) and floodplain is determined by the respective water levels (//​wl<​sub>​body</​sub>//​ and //​wl<​sub>​plain</​sub>//​),​ the equilibrium water level (//​wl<​sub>​equil</​sub>//​) and the thresholds between the water bodies (//​fl<​sub>​body</​sub>/​fl<​sub>​plain</​sub>//​). ​
Line 538: Line 564:
  
 |{{:​start:​hype_model_description:​FloodVar2.png?​400|}}| |{{:​start:​hype_model_description:​FloodVar2.png?​400|}}|
-| Figure ​9: Illustration of floodplain soil flows.|+| Figure ​6: Illustration of floodplain soil flows.|
  
 ==== Connected floodplains ==== ==== Connected floodplains ====
Line 599: Line 625:
  
 |{{:​start:​hype_model_description:​mainflow.png?​400|}}| |{{:​start:​hype_model_description:​mainflow.png?​400|}}|
-| Figure ​5: Main flow in relation to total flow for four different parameter combinations.|+| Figure ​7: Main flow in relation to total flow for four different parameter combinations.|
  
 |{{:​start:​hype_model_description:​branchflow.png?​400|}}| |{{:​start:​hype_model_description:​branchflow.png?​400|}}|
-| Figure ​6: Branch flow in relation to total flow for four different parameter combinations.|+| Figure ​8: Branch flow in relation to total flow for four different parameter combinations.|
  
  
start/hype_model_description/hype_routing.1566992246.txt.gz · Last modified: 2019/08/28 13:37 by cpers