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/10/19 10:05] cpers [Links to file reference] |
start:hype_model_description:hype_routing [2020/02/05 10:22] cpers [Basic assumptions] |
||
|---|---|---|---|
| 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 182: | Line 182: | ||
| - | 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 365: | Line 365: | ||
| ==== 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 405: | Line 405: | ||
| - | Many other combinations can be used, but not all outlet types are natural to combine. The following are not allowed: | + | Many other combinations can be used, but not all outlet types are natural to combine. The following are **not allowed**: |
| ^ Outlet 1 ^ Outlet 2 ^ | ^ Outlet 1 ^ Outlet 2 ^ | ||
| Line 450: | Line 450: | ||
| ==== 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 543: | Line 543: | ||
| It is possible for flooded floodplains to limit the water flow from upstream rivers and lakes. This is determined based on the water levels in the floodplains, a higher water level of a downstream floodplain compared to a upstream floodplain may reduced the flow from the upstream compartment (main river or outlet lake) to the downstream compartment (main river or outlet lake). The damming flow is calculated as the flow to reach equilibrium water level between the two floodplains. The relative level of the two floodplains location is determined based om the classes average elevation and thresholds or given as indata separately. The function of connecting floodplains works within a subbasin or between connected subbasins. This floodplain features may be used together with the **Floodplain model with soil routines**. | It is possible for flooded floodplains to limit the water flow from upstream rivers and lakes. This is determined based on the water levels in the floodplains, a higher water level of a downstream floodplain compared to a upstream floodplain may reduced the flow from the upstream compartment (main river or outlet lake) to the downstream compartment (main river or outlet lake). The damming flow is calculated as the flow to reach equilibrium water level between the two floodplains. The relative level of the two floodplains location is determined based om the classes average elevation and thresholds or given as indata separately. The function of connecting floodplains works within a subbasin or between connected subbasins. This floodplain features may be used together with the **Floodplain model with soil routines**. | ||
| + | |||
| + | |||
| + | ==== Links to file reference ==== | ||
| + | |||
| + | ^Section ^Symbol ^Parameter/Data ^File ^ | ||
| + | | |//fpf//|//fpfol, fpfmr//|[[start:hype_file_reference:flooddata.txt|FloodData.txt]]| | ||
| + | |Common floodplain processes|//classarea//|//slc_nn, area//|[[start:hype_file_reference:geodata.txt|GeoData.txt]]| | ||
| + | |:::|//fym//|//fymol, fymmr//|[[start:hype_file_reference:flooddata.txt|FloodData.txt]]| | ||
| + | |:::|//rc<sub>bodyToPlain</sub>//|//rclfp, rcrfp//|:::| | ||
| + | |:::|//rc<sub>plainToBody</sub>//|//rcfpl, rcfpr//|:::| | ||
| + | |:::|//fl<sub>body</sub>//|//floll, flmrr//|:::| | ||
| + | |:::|//fl<sub>plain</sub>//|//flolp, flmrp//|:::| | ||
| + | |Connected floodplains| |//hrefl, hrefr//|:::| | ||
| ==== Links to relevant modules in the code ==== | ==== Links to relevant modules in the code ==== | ||
| Line 596: | Line 609: | ||
| ^Symbol ^Parameter/Data ^File ^ | ^Symbol ^Parameter/Data ^File ^ | ||
| - | |//branchid, Qbranch, mainpart//|//branchid, Qbranch, mainpart//|[[start:hype_file_reference:flooddata.txt|FloodData.txt]]| | + | |//branchid, Qbranch, mainpart//|//branchid, Qbranch, mainpart//|[[start:hype_file_reference:branchdata.txt|BranchData.txt]]| |
| |//maxQ<sub>main</sub>, minQ<sub>main</sub>, maxQ<sub>branch</sub>//|//maxQmain, minQmain, maxQbranch//|:::| | |//maxQ<sub>main</sub>, minQ<sub>main</sub>, maxQ<sub>branch</sub>//|//maxQmain, minQmain, maxQbranch//|:::| | ||
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
