Differences

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

--- start:hype_model_description:hype_human_water [2018/06/28 14:22]
cpers [Wetland nutrient processes]
+++ start:hype_model_description:hype_human_water [2024/02/21 09:14] (current)
cpers [Irrigation water demand]
@@ Line 1: / Line 1: @@
 ====== Water management ======
-===== Constructed wetlands =====
+===== Constructed wetlands for nutrient retention =====
-For an overview of basic assumptions and explanation of variables see the [[http://www.smhi.net/hype/wiki/doku.php?id=start:hype_model_description:hype_routing&#basic_assumptions| Basic assumptions section]] in the Rivers and lakes chapter.
+For an overview of basic assumptions and explanation of variables see the [[start:hype_model_description:hype_routing&#basic_assumptions| Basic assumptions section]] in the Rivers and lakes chapter.
-The wetlands that are simulated are small artificial ponds. They have an area and depth, but their area is not taken into account in terms of precipitation and evaporation. The water flow passes through the wetlands without being affected, so it's just as nutrient traps that the wetland model is significant.
+The wetlands that are simulated are small artificial ponds. They have an area and depth (//dep//), but their area is not taken into account in terms of precipitation and evaporation. The water flow passes through the wetlands without being affected, so it's just as nutrient traps that the wetland model is significant.
-There are two types of wetlands, just as for the rivers and lakes. They are situated before the river in the calculation scheme. The local wetland (//lrwet//) receives a share of the local runoff the rest passes by unaffected. Wetlands in main rivers (//mrwet//) receive a portion of the flow in the main river and the rest passes unaffected.
+There are two types of wetlands, just as for the rivers and lakes. They are situated before the river in the calculation scheme. The local wetland (//lrwet//) receives a share of the local runoff (//part//) the rest passes by unaffected. Wetlands in main rivers (//mrwet//) receive a portion of the flow in the main river and the rest passes unaffected.
 ==== Wetland nutrient processes ====
-In wetlands, retention of inorganic nitrogen is modelled (denitrification). For total phosphorus retention (sedimentation) and production (or release from sediments) of TP are modelled. The rates of these processes are constant coefficients (//teta//=1.2, //tkoeff//=20, //inpar//=2.3, //sedpar//= 0.09, and //uptpar=//0.1). The retention is limited to 99.9% of the substance in the wetland. The retention (//retIN, retTP, g/d//) depends on the rate parameter, the concentration in the wetland, wetland area, and for inorganic nitrogen also on 5-day-mean temperature. The production (//prodTP, g/d//) depends on a rate parameter, the concentration of the inflow to the wetland, wetland area, and a temperature function (30-day-mean temperature).
+In wetlands, retention of inorganic nitrogen is modelled (denitrification). For total phosphorus retention (sedimentation) and production (or release from sediments) of TP are modelled. The rates of these processes are constant coefficients (//teta//=1.2, //tkoeff//=20, //inpar//=2.3, //sedpar//= 0.09, and //uptpar=//0.1). The retention is limited to 99.9% of the substance in the wetland. The retention (//retIN, retTP, g/d//) depends on the rate parameter, the concentration in the wetland, wetland area, and for inorganic nitrogen also on 5-day-mean air temperature (//T5//). The production (//prodTP, g/d//) depends on a rate parameter, the concentration of the inflow to the wetland, wetland area, and a temperature function (30-day-mean air temperature, //T30//). The change in TP are divided equally between SP and PP.
-<m> retIN = inpar * INconc * temp5 * area / 1000. </m>
+<m> retIN = inpar * INconc * T5 * area / 1000. </m>
 \\
 <m> retTP = sedpar * TPconc * area </m>
 \\
-<m> prodTP = uptpar * TPin * area * teta^(temp30-tcoeff) </m>
+<m> prodTP = uptpar * TPin * area * teta^(T30-tcoeff) </m>
 \\
+==== Links to file reference ====
+^Parameter/Data	^File ^
+|//lrwet_area, lrwet_dep, lrwet_part, mrwet_area, mrwet_dep, mrwet_part//|[[start:hype_file_reference:geodata.txt|GeoData.txt]]|
 ==== Links to relevant modules in the code ====
@@ Line 25: / Line 33: @@
 ^Modules (file)	^Procedures ^
 |[[http://hype.sourceforge.net/doxy-html/namespacenpc__surfacewater__processes.html|npc_surfacewater_processes (npc_sw_proc.f90)]]	|calculate_river_wetland |
-|:::|calculate_wetland_np|
+|:::|calculate_riverwetland_np|
 ==== References ====
@@ Line 32: / Line 40: @@
 Tonderski, K.S., Arhemier, B. and Pers B.C., 2005. Modelling the Impact of Potential Wetlands on Phosphorus Retention in a Swedish Catchment, Ambio, 34(7): 544-551.
+===== Constructed wetlands with water regulation capability =====
+The wetlands are water classes, but simulated as a land class with special functions. If the soil is over saturated the standing water is the water volume of the wetland (//vol//, m3). If the soil is not over saturated, the wetland is dried out. The wetlands area (//area//, m2) is defined by the class area, and the depth (//w//) varies with flow. A threshold (//w0//) for the wetland outflow above the soil surface keep water in the wetland. The wetland outflow is determined by a rating curve above this threshold (see also [[start:hype_model_description:hype_routing#common_lake_processes | lake outflow]]). The thresholds can be set by parameters or if parameters are not set it is equal to minus the streamdepth (from GeoClass).
+<m> outflow = k*(w-w0) ^ p </m>
+There are two types of wetlands; internal wetlands (//iwet//) and wetlands at the outlet of the subbasin (//owet//). Internal wetlands recieve a fraction (//ifraction//) of the runoff from other land classes (Figure 1). Outlet wetlands cannot be present in the same subbasin as an outlet lake. They recieve the flow from the main river of the subbasin (Figure 2).
+|{{:start:hype_model_description:HYPE_box_picture_v3_iwet.png?400|}}|
+|Figure 1 Water flows of internal wetland (iwet).|
+|{{:start:hype_model_description:HYPE_box_picture_v3_owet.png?400|}}|
+|Figure 2 Water flows of outlet wetland (owet).|
+==== Wetland nutrient processes ====
+The concentration of the wetland (//conc//) is the concentration of soil water in soil layer 1. While calculating wetland nutrient processes only the nutrients in the water volume of the wetland in considered though. After that the nutrient concentration of the upper soil layer is updated.
+Denitrification of inorganic nitrogen in the wetland is modelled as [[start:hype_model_description:hype_np_soil#denitrification | denitrification in the soil water]]. Sedimentation of organic nitrogen, particulate phosphorus and suspended sediments are simulated (//sed//, g/d). Uptake of inorganic nutrients (IN and SP) are modelled as macrophyte uptake. The macrophytes are assumed to cover a part of the wetland area (//fracarea//). The covered fraction is calculated as the part that is shallower than a production depth (//proddep//) assuming the wetland area is decreasing linear with depth until twice the average depth of the wetland. The macrophytes are assumed to give residuals of equal amount of nutrient back to the sediment (i.e. immobile organic nutrient pools of soillayer one). The macrophyte uptake process (//upt//, g/d) depends on a rate parameter (//uptpar//), macrophyte fraction of wetland area, temperature (//tmpfcn//) and total phosphorus concentration (//TPfunc//). The temperature and TP functions are similar to the ones used by [[start:hype_model_description:hype_np_riv_lake#primary_production_and_mineralization | primary production in lakes]]). The temperature function use 5- and 30-day mean air temperature (//T5, T30//). The half saturation concentration of TP is 0.05 mg/L (//hsatTP//). The sedimentation is limited to 99.9% of the substance in the wetland water, while macrophytes are limited to 50% of the dissolved inorganic nutrients.
+<m> sed = velpar * area * conc </m>
+<m> upt = uptpar * tmpfcn * TPfcn * fracarea </m>
+<m> tmpfcn = (T5 / 20.)^tmppar * {(T5 - T30) / 5.} </m>
+<m> TPfcn = {TPconc} / {TPconc + hsatTP} </m>
+<m> fracarea = {proddep / (2*vol/area)} * area </m>
+==== Links to file reference ====
+^Symbol^Parameter/Data	^File ^
+|//ifraction//|calculated from //iwetcatch//|[[start:hype_file_reference:geodata.txt|GeoData.txt]]|
+|//w0//|streamdepth or //iwet0,owet0//|[[start:hype_file_reference:geoclass.txt|GeoClass.txt]] or  [[start:hype_file_reference:par.txt|par.txt]]|
+|//k//|calculated from catchment area parameters //wetrate, grata//|[[start:hype_file_reference:par.txt|par.txt]]|
+|//p//|//wetexp//|:::|
+|//velpar//|//wlsed//|:::|
+|//uptpar//|//wlmphuptin,wlmphuptsp//|:::|
+|//proddep//|//wlproddep//|:::|
+|//tmppar//|//wltmpexp//|:::|
+==== Links to relevant modules in the code ====
+^Modules (file)	^Procedures ^
+|[[http://hype.sourceforge.net/doxy-html/namespacenpc__surfacewater__processes.html|npc_surfacewater_processes (npc_sw_proc.f90)]]	|wetland_substance_processes |
+|[[http://hype.sourceforge.net/doxy-html/namespacesurfacewater__processes.html|surfacewater_processes (sw_proc.f90)]]	|wetland_watermodel |
+|:::|T2_processes_in_wetland|
+|:::|get_wetland_threshold|
 ===== Irrigation =====
@@ Line 39: / Line 100: @@
 Irrigation constitutes a key water management activity in many parts of the world. Therefore, the HYPE model has a routine to simulate irrigation. The representation of irrigation in the model is based on a set of principles. Firstly, the irrigation water demand is assessed. Subsequently, the demanded water is withdrawn from the defined irrigation water sources. HYPE can either withdraw water from defined sub-basins in the model domain (subject to availability), or from unlimited sources outside the domain. Finally, the withdrawn water is applied onto the classes from which the demand originated. In addition, water losses between demand, withdrawal, and application are taken into account (for withdrawals within the model domain).
-A class is irrigated if the crop type associated with it is irrigated (defined in GeoClass.txt). A crop is irrigated if the irrigation input variables in the CropData.txt file are defined and non-zero (//plantday, lengthini, kcbini, lengthdev, lengthmid, kcbmid, lengthlate, kcbend, dlref//). Irrigation also requires appropriate values in the MgmtData.txt file (//gw_part, regsrcid, irrdam, region_eff, local_eff, demandtype//) and the par.txt file (//pirrs, pirrg, sswcorr// etc.). See the FileDescription document for more details on each file and each parameter.
+A class is irrigated if the crop type associated with it is irrigated (defined in GeoClass.txt). A crop is irrigated if the irrigation input variables in the CropData.txt file are defined and non-zero (//plantday, lengthini, kcbini, lengthdev, lengthmid, kcbmid, lengthlate, kcbend, dlref//). Irrigation also requires appropriate values in the MgmtData.txt file (//gw_part, regsrcid, irrdam, region_eff, local_eff, demandtype//) and the par.txt file (//pirrs, pirrg, sswcorr// etc.). See the [[start:hype_file_reference|File Reference]] for more details on each file and each parameter.
 ==== Irrigation water demand ====
@@ Line 49: / Line 110: @@
 For non-submerged crops, the calculations are based on the FAO-56 crop coefficient methods (Allen et al., 1998). The dual crop coefficient method is used because it is more specific than the single crop coefficient method, and more suitable for daily water balance models. Since transpiration is of primary interest in estimating crop water demand, the irrigation routine focuses on estimating potential transpiration (<m>T_P</m>) with the basal crop coefficient (<m>K_{CB}</m>) and the reference potential crop evapotranspiration (<m>ET_0</m>):
-<m> T_P=K_{CB}×ET_0 </m>
+<m> T_P=K_{CB}*ET_0 </m>
-ET0 follows the dynamics described above (<m>ET_0 = epot</m> here following Wisser et al. (2008)). KCB depends on crop type and phenological stage, which is defined in CropData.txt. KCB is constant during the initial development stage, then increases linearly during the development stage until it reaches the mid-season stage during which it is again constant. Finally, <m>K_{CB}</m> decreases linearly from the end of the mid-season stage until the end of the season. The dynamics of <m>ET_0</m> and <m>K_{CB}</m> produces a dynamic <m>T_P</m> profile (Figure 1). Allen et al. (1998) provide indicative values for <m>K_{CB}</m> (cf. their Table 17).
+ET0 follows the dynamics described above (<m>ET_0 = epot</m> here following Wisser et al. (2008)). KCB depends on crop type and phenological stage, which is defined in CropData.txt. KCB is constant during the initial development stage, then increases linearly during the development stage until it reaches the mid-season stage during which it is again constant. Finally, <m>K_{CB}</m> decreases linearly from the end of the mid-season stage until the end of the season. The dynamics of <m>ET_0</m> and <m>K_{CB}</m> produces a dynamic <m>T_P</m> profile (Figure 3). Allen et al. (1998) provide indicative values for <m>K_{CB}</m> (cf. their Table 17).
+The growth season (and irrigation period) start on the plant day (//planting//). The growth start is determined by a constant (//plantday//) or depending on climate similar to the options for [[start:hype_model_description:hype_np_soil#potential_vegetation_uptake_of_nitrogen|nutrient uptake]]. If it is dynamically determined by the degree-day method it is set to the first day of the year which has a degreeday sum (//GDD//) above a threshold (//gsgddsow//).
+The degreeday sum (//GDD//) is calculated as
+<m> GDD(d+1)=GDD(d)+MAX(0,T-gsbasetemp) </m>
+where //d// is day of year, //T// is air temperature (degree Celsius), //gsbasetemp// is a temperature threshold. The GDD is accumulated for each day after //gsfirstday// with day length larger than //gsdaylen//. The GDD is reset to zero at //gsfirstday//.
+Another alternative is for it to be dynamically determined by the temperature threshold method. It is then set to the first day after a given earliest day (//gsfirstday//) which has consecutive number of days (//gsaccdays//) with daily mean air temperature above a threshold (//gsdaytemp//).
 |{{:start:hype_model_description:graphirrigation.png?500|}}|
-|Figure 1 Illustration of <m>ET_0, T_P, K_CB</m>, and <m>SSW</m> for a typical maize crop on a medium coarse soil in southern Europe. Key input variables to define the <m>K_CB</m> profile are shown in blue.|
+|Figure 3 Illustration of <m>ET_0, T_P, K_CB</m>, and <m>SSW</m> for a typical maize crop on a medium coarse soil in southern Europe. Key input variables to define the <m>K_CB</m> profile are shown in blue.|
 On any given day, the model first calculates whether irrigation is needed, and then the amount required. The irrigation need is assessed by comparing the current soil water content (//H//) with a dynamic irrigation threshold (<m>S_{SW}</m>, the soil water stress threshold):
-<m> if H <(S_{SW}×P_{SSWCORR}×AWC) right irrigate </m>
+<m> if H <(S_{SW}*P_{SSWCORR}*AWC) right irrigate </m>
-H is the plant-available soil moisture (i.e. soil water above //wcwp1// and //wcwp2// in soil layers 1 and 2 respectively). //AWC// is the maximum plant-available water content in soil layers 1 and 2 (i.e. the sum of //fc1// and //fc2//). <m>S_{SW}</m> is a fraction of //AWC// (defined upwards from //wcwp//). Below <m>S_{SW}</m> the crop experiences water stress, creating a need for irrigation. <m>S_{SW}</m> varies from day to day and depends on the crop type and //TP//:
+H is the plant-available soil moisture (i.e. soil water above //wcwp1// and //wcwp2// in soil layers 1 and 2 respectively). //AWC// is the maximum plant-available water content in soil layers 1 and 2 (i.e. the sum of //fc1// and //fc2//). <m>S_{SW}</m> is a fraction of //AWC// (defined upwards from //wcwp//). Below <m>S_{SW}</m> the crop experiences water stress, creating a need for irrigation. <m>S_{SW}</m> varies from day to day and depends on the crop type and <m>T_P</m>:
-<m> S_{SW}=1-(DL_{ref}+0.04×(5-{{T_P}/0.95})) </m>
+<m> S_{SW}=1-(DL_{ref}+0.04*(5-{{T_P}/0.95})) </m>
-<m>DL_{ref}</m> is a crop-type specific reference depletion level (essentially the fraction of //AWC// that can be depleted before stress occurs, defined downwards from //wcfc//). Allen et al. (1998) provide indicative values for <m>DL_{ref}</m> (cf. their Table 22). The <m>S_{SW}</m> equation is a slightly modified form of the original FAO-56 equation to account for the fact that only TP is used here. A typical <m>S_{SW}</m> profile is shown in Figure 3.1. By default, <m>S_{SW}</m> is limited to the range 0.2 – 0.9, but it can be further refined with the parameter <m>P_{SSWCORR}</m> (//sswcorr// in par.txt) to maximum 1.
+<m>DL_{ref}</m> is a crop-type specific reference depletion level (essentially the fraction of //AWC// that can be depleted before stress occurs, defined downwards from //wcfc//). Allen et al. (1998) provide indicative values for <m>DL_{ref}</m> (cf. their Table 22). The <m>S_{SW}</m> equation is a slightly modified form of the original FAO-56 equation to account for the fact that only <m>T_P</m> is used here. A typical <m>S_{SW}</m> profile is shown in Figure 3. By default, <m>S_{SW}</m> is limited to the range 0.2 – 0.9, but it can be further refined with the parameter <m>P_{SSWCORR}</m> (//sswcorr// in par.txt) to maximum 1.
 If irrigation is needed, the required irrigation amount (<m>W_{I,D,j}</m>) can be calculated with three alternative methods in HYPE (chosen by the demandtype variable in MgmtData.txt):
@@ Line 75: / Line 146: @@
 (3) Up to a defined fraction of <m>S_{SW}</m> (<m>P_{iwdfrac}</m>, //iwdfrac// in par.txt):
-<m>W_{I,D,j}=min[(S_{SW}×P_{SSWCORR}×AWC-H)×P_{iwdfrac},(AWC-H)]</m>
+<m>W_{I,D,j}=min[(S_{SW}*P_{SSWCORR}*AWC-H)*P_{iwdfrac},(AWC-H)]</m>
 The fraction can be larger than 1. For example, to irrigate to a level 10% above <m>S_{SW}</m>, <m>P_{iwdfrac}</m> =1.1. <m>W_{I,D,j}</m> is, however, limited to <m>AWC</m>.
@@ Line 97: / Line 168: @@
 ==== Irrigation water withdrawal ====
-Irrigation water can be abstracted from a set of water sources (Figure 2). Within a given sub-basin, water can be abstracted from the olake, the ilake, the main river, and from groundwater in a deep aquifer. In addition, water can be withdrawn from the olake and the main river of another sub-basin. These sources can be used on their own or in combination. Alternatively, HYPE can withdraw water from an unlimited source outside the model domain. This is specified with the ''irrunlimited'' code word in info.txt, and applies to all irrigated sub-basins.
+Irrigation water can be abstracted from a set of water sources (Figure 4). Within a given sub-basin, water can be abstracted from the olake, the ilake, the main river, and from groundwater in a deep aquifer. In addition, water can be withdrawn from the olake and the main river of another sub-basin. These sources can be used on their own or in combination. Alternatively, HYPE can withdraw water from an unlimited source outside the model domain. This is specified with the ''irrunlimited'' code word in info.txt, and applies to all irrigated sub-basins.
-Withdrawals are calculated just after the local discharge and the upstream discharge combine to flow into the main river of a given sub-basin.
+Withdrawals are calculated directly after the local discharge and the upstream discharge has been combined to flow into the main river of a given sub-basin.
 |{{:start:hype_model_description:irrigationschematic.png?500}}|
-|Figure 2: Schematic illustration of the available irrigation sources in HYPE. Irrigation water can be withdrawn from: (i) dams in the sub-basin (olake and ilake), (ii) the main river in the sub-basin, (iii) groundwater in a deep aquifer, and (iv) dams (olake) and main rivers in other sub-basins.|
+|Figure 4: Schematic illustration of the available irrigation sources in HYPE. Irrigation water can be withdrawn from: (i) dams in the sub-basin (olake and ilake), (ii) the main river in the sub-basin, (iii) groundwater in a deep aquifer, and (iv) dams (olake) and main rivers in other sub-basins.|
 === Irrigation inefficiencies within the sub-basin ===
@@ Line 118: / Line 189: @@
 If any surface water demand exists, the model sequentially attempts to withdraw water from the olake, the ilake, and the main river. However, water withdrawal from olakes and ilakes is only calculated if the variable //irrdam// in MgmtData.txt is set to 1 for the sub-basin. Water withdrawals from the main river occur both from the inflow to the river reach and from the volume stored in the reach.
-If the <m>W_{L,D,s}</m> volume is available at the source, the demanded water is withdrawn. Otherwise, only the available volume (<m>V_s</m>) is withdrawn. The withdrawal can also be scaled with the user-defined parameter <m>P_{I,S}</m> (//pirrs// in par.txt):
+If the <m>W_{L,D,s}</m> volume is available at the source, the demanded water is withdrawn. Otherwise, only the available volume (<m>V_s</m>) is withdrawn. The withdrawal is scaled with the user-defined parameter <m>P_{I,S}</m> (//pirrs// in par.txt):
-<m> W_{L,A,s(1)}=min(W_{L,D,s},V_{s1})×P_{I,S} </m>
+<m> W_{L,A,s(1)}=min(W_{L,D,s},V_{s1})*P_{I,S} </m>
 <m> W_{L,D,s2}=W_{L,D,s}-{W_{L,A,s(1)}}/{P_{I,S}} </m>
@@ Line 126: / Line 197: @@
 where <m>W_{L,A,s(1)}</m> is the abstracted water from the first surface water source in the sub-basin, and <m>W_{L,D,s2}</m> is the residual surface water demand. The residual demands (<m>W_{L,D,s2}</m> and below <m>W_{L,D,s,1}</m>, <m>W_{L,D,1}</m> and <m>W_{R,D2}</m>) are calculated without the <m>P_{I,S}</m> scaling in order to prevent erroneous source compensation due to scaling. If any demand remains, the next surface water source is probed in the same manner:
-<m> W_{L,A,s(2)}=min(W_{L,D,s2},V_{s2} )×P_{I,S} </m>
+<m> W_{L,A,s(2)}=min(W_{L,D,s2},V_{s2} )*P_{I,S} </m>
 The total surface water withdrawal within the sub-basin (<m>W_{L,A,s}</m>), and the remaining surface water demand (<m>W_{L,D,s,1}</m>) is calculated accordingly, based on the abstractions from each source (k):
@@ Line 134: / Line 205: @@
 <m> W_{L,D,s,l}= W_{L,D,s}-{W_{L,A,s}}/{P_{I,S}} </m>
-If any groundwater demand exists, the model withdraws a user-specified fraction of <m>W_{L,D,g}</m> from an unlimited source outside the model domain or if an aquifer is simulated connected to the subbasin from this aquifer. The first case conceptually represents a large deep aquifer source, which is currently outside of the model domain. <m>W_{L,a,g}</m> is the abstracted groundwater and <m>P_{I,G}</m> (//pirrg// in par.txt) is the groundwater withdrawal fraction:
+If any groundwater demand exists, the model withdraws a user-specified fraction of <m>W_{L,D,g}</m> from an unlimited source outside the model domain or if an aquifer is simulated connected to the subbasin from this aquifer. The first case conceptually represents a large deep aquifer source, which is currently outside of the model domain. <m>W_{L,a,g}</m> is the abstracted groundwater and <m>P_{I,G}</m> (//pirrg// in par.txt) is the groundwater withdrawal scaling:
-<m> W_{L,A,g}=W_{L,D,g}×P_{I,G} </m>
+<m> W_{L,A,g}=W_{L,D,g}*P_{I,G} </m>
 To simulate a more dynamic conjunctive use of groundwater and surface water sources, the model allows for compensation of remaining surface water demands from the groundwater source. This compensation is only allowed if both groundwater and surface water sources are used (//0<gw_part<1//), and if the //irrcomp// parameter is >0. The //irrcomp// parameter defines the degree of compensation allowed, i.e. the fraction of the residual surface water demand which can be met through source compensation. The compensation algorithm is as follows: if any surface water demand remains (<m>W_{L,D,s,1}</m> > 0) and the groundwater is not depleted, the groundwater withdrawal cycle is calculated once more using the scaled residual surface water demand. Finally, after possible source compensation, the remaining (surface) water demand at the sub-basin scale (<m>W_{L,D,1}</m>) is calculated.
@@ Line 147: / Line 218: @@
 <m> W_{R,D,i}={W_{L,D,l,i}}/{E_{R,i}} </m>
-The regional efficiency (<m>E_{R,i}</m>, //region_eff// in MgmtData.txt) represents the fraction of the withdrawn water at the regional source that reaches the connected sub-basin. E_{R,i} refers to the connected sub-basin. The regional scaling accounts for often significant water conveyance losses in large irrigation networks (in canals and dams etc.).
+The regional efficiency (<m>E_{R,i}</m>, //region_eff// in MgmtData.txt) represents the fraction of the withdrawn water at the regional source that reaches the connected sub-basin. <m>E_{R,i}</m> refers to the connected sub-basin. The regional scaling accounts for often significant water conveyance losses in large irrigation networks (in canals and dams etc.).
 The total water demand from the regional source (<m>W_{R,D}</m>) is then calculated as the sum of the demand from each connected sub-basin, scaled by a parameter controlling the strength of the regional connection (<m>P_regirr</m>, //regirr// in par.txt):
-<m> W_{R,D}= (sum{i=1}{N}{W_{R,D,i}} )×P_{regirr} </m>
+<m> W_{R,D}= (sum{i=1}{N}{W_{R,D,i}} )*P_{regirr} </m>
 The regional demand can be met from two sources in sub-basin <m>D_R</m>: the olake and the main river. If the regional source sub-basin has an olake, and if the //irrdam// input variable is set to 1 for that sub-basin, the model attempts to withdraw <m>W_{R,D}</m> first from the olake and then the residual from the main river. If not, the model only attempts to withdraw <m>W_{R,D}</m> from the main river. The regional abstraction (<m>W_{R,a}</m>) is limited by the volume available at the source (<m>V_r</m>) and the scaling parameter <m>P_{I,S}</m>:
-<m> W_{R,A1}=min(W_{R,D},V_{r1} )×P_{I,S} </m>
+<m> W_{R,A1}=min(W_{R,D},V_{r1} )*P_{I,S} </m>
 <m> W_{R,D2}=W_{R,D}-{W_{R,A1}}/{P_{I,S}} </m>
-<m> W_{R,A2}=min(W_{R,D2},V_{r2} )×P_{I,S} </m>
+<m> W_{R,A2}=min(W_{R,D2},V_{r2} )*P_{I,S} </m>
 <m> W_{R,A}=W_{R,A1}+ W_{R,A2} </m>
@@ Line 169: / Line 240: @@
 The concentrations of the withdrawn water are the same as that of the irrigation water source. If the water originates from several sources, the volume-weighted concentration is calculated. If desired, the model can simulate sedimentation tanks, in which a defined fraction of the particulate phosphorous (//pp//) and organic nitrogen (//on//) settles:
-<m> C_{a,pp}=C_{src,pp}×(1-P_{cirrsink} ) </m>
+<m> C_{a,pp}=C_{src,pp}*(1-P_{cirrsink} ) </m>
-<m> C_{a,on}=C_{src,on}×(1-P_{cirrsink} ) </m>
+<m> C_{a,on}=C_{src,on}*(1-P_{cirrsink} ) </m>
 where <m>C_{,a}</m> is the concentration of the abstracted water after settling, <m>C_{src}</m> is the concentration of the source, and <m>P_{cirrsink}</m> is the concentration reduction fraction (//cirrsink// parameter in par.txt). To use sedimentation tanks in a region, the concentration reduction fraction needs to be set in par.txt (//0<cirrsink≤1//).
+If the model withdraw water from an unlimited source outside the model domain, the concentration of the water applied is assumed the same as the concentration of the recieving soil layer. Thus the concentration is assumed not to be affected by the irrigation.
 ==== Irrigation water application ====
@@ Line 181: / Line 254: @@
 The regionally abstracted water (<m>W_{R,A}</m>) is first distributed to each connected sub-basin (i) according to their proportional demand, and then scaled to the local scale using the respective regional efficiency:
-<m> W_{R,A,i}=W_{R,A}× {W_{R,D,i}×P_{regirr}}/{W_{R,D}}×E_{R,i} </m>
+<m> W_{R,A,i}=W_{R,A}* {W_{R,D,i}*P_{regirr}}/{W_{R,D}}*E_{R,i} </m>
 For a given sub-basin, the total amount of abstracted water available at the local scale (<m>W_{L,A,i,tot}</m>) is calculated and then scaled, using the local efficiency, to represent the water applied to the soil (<m>W_{I,A,i}</m>):
@@ Line 187: / Line 260: @@
 <m> W_{L,A,i,tot}=W_{L,A,i}+W_{R,A,i} </m>
-<m> W_{I,A,i}=W_{L,A,i,tot}×E_{L,i} </m>
+<m> W_{I,A,i}=W_{L,A,i,tot}*E_{L,i} </m>
 <m>W_{I,A,i}</m> is then distributed onto each irrigated class in proportion to its water demand:
-<m> W_{I,A,j}=W_{I,A,i}×{W_{I,D,j}}/{W_{I,D}} </m>
+<m> W_{I,A,j}=W_{I,A,i}*{W_{I,D,j}}/{W_{I,D}} </m>
-<m>W_{I,A,j}</m> is added to the soil water of class j as additional infiltration. <m>W_{I,A,j}</m> is divided between the top two soil layers according to the epotdist function, beginning with the second layer. For unlimited irrigation: <m>W_{I,A,j} =  W_{I,D,j}</m> , <m>P_{I,S} =1</m> and <m>P_{I,G} = 1</m>.
+<m>W_{I,A,j}</m> is added to the soil water of class j as additional infiltration. <m>W_{I,A,j}</m> is added to the top soil layer. The soil layer may then hold more water than the pore volume of the soil layer. This will percolate into lower soil layers together with rain if the water is above field capacity. For unlimited irrigation: <m>W_{I,A,j} =  W_{I,D,j}</m> , <m>P_{I,S} =1</m> and <m>P_{I,G} = 1</m>.
 The water withdrawn from a regional source that does not reach connected sub-basins (<m>W_{R,L}</m>) evaporates at the regional source (<m>D_R</m>):
@@ Line 205: / Line 278: @@
 Evaporation due to regional and local inefficiencies proportionally concentrates substances in the withdrawn water. The substance concentrations in the irrigation water applications are hence higher than at the points of withdrawal (the mass remains the same while the volumes are reduced). However, if unlimited irrigation is simulated, the concentrations of the applied water are the same as in the layers to which water is added (i.e. causing no change in concentration).
+==== Links to file reference ====
+^Section	^Symbol ^Parameter/Data ^File ^
+| | |//cropid, reg//|[[start:hype_file_reference:cropdata.txt|CropData.txt]]|
+| | |//mgmttype//=1, //subid//|[[start:hype_file_reference:mgmtdata.txt|MgmtData.txt]]|
+|Irrigation water demand| |//imm_start, imm_end//|[[start:hype_file_reference:cropdata.txt|CropData.txt]]|
+|Non-submerged crops| |//demandtype//|[[start:hype_file_reference:mgmtdata.txt|MgmtData.txt]]|
+|:::|//planting// set or calculated from:| //plantday, gsdaylen, gsgddsow, gsbasetemp, gsdaytemp, gsaccdays//|[[start:hype_file_reference:cropdata.txt|CropData.txt]]|
+|:::|<m>K_{CB}</m> calculated from:|//planting, lengthini, kcbini, lengthdev, lengthmid, kcbmid, lengthlate, kcbend//|:::|
+|:::|<m>DL_{ref}</m>|//dlref//|:::|
+|:::|<m>P_{SSWCORR}</m>|//sswcorr//|[[start:hype_file_reference:par.txt|par.txt]]|
+|:::|<m>P_{iwdfrac}</m>|//iwdfrac//|:::|
+|:::|//AWC//|//wcfc1+wcfc2//|:::|
+|Submerged crops|<m>WP_1, FC_1, EP_1</m> |//wcwp1, wcfc1, wcep1//|[[start:hype_file_reference:par.txt|par.txt]]|
+|:::|<m>P_{immdepth}</m>|//immdepth//|:::|
+|Irrigation water withdrawal|  |//irrunlimited//|[[start:hype_file_reference:info.txt|info.txt]]|
+|Irrigation inefficiencies within the sub-basin|<m>E_{L}</m>, <m>E_{L,i}</m>|//local_eff//|[[start:hype_file_reference:mgmtdata.txt|MgmtData.txt]]|
+|Withdrawal from sources within the sub-basin| |//irrdam, gw_part//|[[start:hype_file_reference:mgmtdata.txt|MgmtData.txt]]|
+|:::|  |//irrcomp//|[[start:hype_file_reference:par.txt|par.txt]]|
+|:::|<m>P_{I,S}</m>, <m>P_{I,G}</m>|//pirrs//, //pirrg//|:::|
+|Withdrawal from another sub-basin|<m>D_{R}</m>|//regsrcid//|[[start:hype_file_reference:mgmtdata.txt|MgmtData.txt]]|
+|:::|<m>E_{R,i}</m>|//region_eff//|:::|
+|:::|<m>P_{regirr}</m>|//regirr//|[[start:hype_file_reference:par.txt|par.txt]]|
+|Substance concentrations of irrigation water withdrawals|<m>P_{cirrsink}</m>|//cirrsink//|[[start:hype_file_reference:par.txt|par.txt]]|
 ==== Links to relevant procedures in the code ====
@@ Line 226: / Line 326: @@
 ===== Point sources =====
-Information on point sources is located in the file [[start:hype_file_reference:pointsourcedata.txt|PointSourceData.txt]].
+Information on point sources is located in the file [[start:hype_file_reference:pointsourcedata.txt|PointSourceData.txt]]. Point sources can be added to the model in different ways. They can be added as a constant source each time step, or with a constant that is changing some times during the simulation. They can also be added as time series of flow and concentration. For the first case all information of the point sources is found in the PointSourceData.txt file. For the second case the time series are given separate, and the file holds information on where the point sources are located. Simulated substances not having an concentration given in the file(s), will have concentration zero (default). This may be inappropriate for T2, water temperature.
-==== Nutrient point sources ====
+==== Constant or periodical point sources ====
+=== Nutrient ===
 The model can handle up to three different types of point sources. They can used to simulate e.g. treatment plants, stormwater outlets, and industrial sources as separate types. All point sources have a constant flow, concentrations of total nitrogen and phosphorus, and fractions of IN and SP for a period of time. The time may be the whole simulation period, or different sources may be active during different parts of the simulation period. Point sources are added to the water in the main river.
+=== Sediment  ===
-==== Tracer T2 (water temperature) point sources ====
+Sediment point sources are handled similar to nutrient point sources. A point sources has a constant flow, concentration of total suspended sediment (TS), and fraction of suspended sediments (SS). The point source may be active the whole simulation period, or different sources may be active during different parts of the simulation period. Point sources are added to the water in the main river.
+=== Tracer T2 (water temperature)  ===
-Water temperature may be added to the flow of nutrient point sources if T2 is simulated together with N and P. Water temperature point source may also be added on its own in the same way as nutrient point sources.
+Water temperature may be added to the flow of nutrient and sediment point sources if T2 is simulated together with N and P. Water temperature point source may also be added on its own in the same way as tracer T1 in different locations of the river network.
-==== Tracer T1 point sources ====
+=== Tracer T1 ===
-Tracer T1 point source may be added in the same way as nutrient point sources. In addition, point sources of tracer T1 can be added to the local stream, the local lake, the main river or the outlet lake.
+Tracer T1 point source may be added in the same way as nutrient and sediment point sources. In addition, point sources of tracer T1 can be added to the local stream, the local lake, the main river or the outlet lake.
+==== Time series of point sources ====
+Time series of point sources can be given in special file. In this case the PointSourceData.txt holds only information on which point sources exist in the model and where they can be found.
+=== Nutrient and sediment  ===
+The model can handle up to three different types of point sources. They can used to simulate e.g. treatment plants, stormwater outlets, and industrial sources as separate types. The point sources are given as either daily, monthly or yearly time series. They are given a flow and a concentration for each nutrient species simulated, i.e. IN, ON, SP, PP, AE or SS. Point sources are added to the water in the main river.
+=== Tracer T2 (water temperature)  ===
+Water temperature may be added to the point source flow the same way as concentration.
+=== Tracer T1  ===
+Tracer T1 point source may be added to the point source flow the same way as other concentrations.
+==== Negative point source  ====
+A point source with "negative flow" denotes an abstraction of water. The abstraction of water can be made from four different locations. The default is to remove it from the main river volume (including the queue) after all river processes have been calculated except outflow from the river. Alternatives are to abstract the water from the outlet lake volume, from an aquifer or from the main river inflow from upstream and from the river volume (and queue) proportionally. In the latter case the removal is done before any inflow to the main river is added (e.g. from upstream, point sources, or precipitation). The water is removed from the source, while the concentration is kept.
+Negative point sources can be constant or periodically constant abstractions by giving a negative flow (a negative value). Alternatively they can also be given as time series. In the latter case the flow time series is positive but it is defined as a negative point source in PointSoureData.txt.
+==== Links to file reference ====
+^Section ^Parameter/Data ^File ^
+|Constant or periodical point sources - Nutrient|//subid, ps_vol, ps_type, ps_tpconc, ps_tnconc, ps_infrac, ps_spfrac, fromdate, todate//|[[start:hype_file_reference:pointsourcedata.txt|PointSourceData.txt]]|
+|Constant or periodical point sources - Sediment |//subid, ps_vol, ps_type, ps_tsconc, ps_ssfrac, fromdate, todate//|:::|
+|Constant or periodical point sources - Tracer T2 |//subid, ps_vol, ps_type, ps_t2, fromdate, todate//|:::|
+|:::|//subid, ps_vol, ps_type=0, ps_t2, fromdate, todate, ps_source//|:::|
+|Constant or periodical point sources - Tracer T1 |//subid, ps_vol, ps_type, ps_t1, fromdate, todate//|:::|
+|:::|//subid, ps_vol, ps_type=0, ps_t1, fromdate, todate, ps_source//|:::|
+|Time series point sources|//psid, subid, ps_type, ps_source//|[[start:hype_file_reference:pointsourcedata.txt|PointSourceData.txt]] and [[start:hype_file_reference:pstimeseries.txt|PSTIMESeries.txt]]|
+|Negative point source|//subid, ps_vol, fromdate, todate, ps_source//|[[start:hype_file_reference:pointsourcedata.txt|PointSourceData.txt]]|
+|:::|//psid, subid, ps_source//|[[start:hype_file_reference:pointsourcedata.txt|PointSourceData.txt]] and [[start:hype_file_reference:pstimeseries.txt|PSTIMESeries.txt]]|
-==== Negative point source ====
-A point source with negative flow denotes an abstraction of water. The abstraction of water can be made from three different points in the river network. The default is to remove it from the main river volume (including the queue) after all river processes have been calculated except outflow from the river. Alternatives are to abstract the water from the outlet lake volume or from the main river inflow from upstream and from the river volume (and queue) proportionally. In the latter case the removal is done before any inflow to the main river is added (e.g. from upstream, point sources, or precipitation). The water is removed from the source, while the concentration is kept.
 ==== Links to relevant procedures in the code ====
@@ Line 255: / Line 391: @@
 |[[http://hype.sourceforge.net/doxy-html/namespacesurfacewater__processes.html|surfacewater_processes (sw_proc.f90)]]|point_abstraction_from_main_river|
 |:::|point_abstraction_from_outlet_lake |
-|[[http://hype.sourceforge.net/doxy-html/classtracer__processes.html|tracer_processes (t_proc.f90)]]|add_tracer_point_source_to_river|
+|[[http://hype.sourceforge.net/doxy-html/namespacetracer__processes.html|tracer_processes (t_proc.f90)]]|add_tracer_point_source_to_river|
 | ::: |add_tracer_point_source_to_lake|
-=====Water transfer=====
+=====Water abstraction and transfer=====
-Water transfer can be simulated by HYPE in different ways. One way is to represent abstraction by defining [[start:hype_model_description:hype_human_water#negative_point_source | negative point source]] discharge. Another method is to use the [[start:hype_model_description:hype_routing#bifurcations | bifurcation functionality]] that defines a branch through which the water is transferred to a downstream receiving subbasin. A third way is to define water transfer through water management (abstracting from subbasins with outlet lakes and transferring to any other subbasin). The negative point source method has the disadvantage that the water transfer is constant and with fixed concentrations specified by the user (although you can let it be constant at different values for different periods), but the abstraction can be located at different points throughout the catchment. The bifurcation method has the limitation that the receiving subbasin must be downstream. The management method can only take water from an outlet lake, and the water transfer will be delayed one time step. In all methods, the amount of water available on any given day will limit the amount that can be withdrawn or transferred.
+Water transfer can be simulated by HYPE in different ways. One way is to represent abstraction by defining [[start:hype_model_description:hype_human_water#negative_point_source | negative point source]] discharge. Another method is to use the [[start:hype_model_description:hype_routing#bifurcations | bifurcation functionality]] that defines a branch through which the water is transferred to a downstream receiving subbasin. A third way is to define water transfer through water management (abstracting from subbasins with outlet lakes and transferring to any other subbasin). The negative point source method has the disadvantage as a water transfer that the concentration of the water is specified by the user and not the concentrations of the water abstracted, but the abstraction can be located at different points throughout the catchment. The bifurcation method has the limitation that the receiving subbasin must be downstream. The management method can only take water from an outlet lake, and the water transfer will be delayed one time step. In all methods, the amount of water available on any given day will limit the amount that can be withdrawn or transferred.
@@ Line 268: / Line 404: @@
 ====Water transfer through negative point source====
-Abstraction of water can be defined as a [[start:hype_model_description:hype_human_water#negative_point_source | negative point sources]]. The abstracted water is constant (although it can be constant at different values for different periods), and thus the same amount of water is removed from the model every time step. The abstraction can be made from different points in the river network within the subbasin. The water is removed while the concentration is kept in the water remaining in the river. To simulate water transfer within the model domain, the same amount of water need to be added as a (positive) point source in another subbasin. This subbasin do not have to be downstream, since its (constant) flow and concentrations is defined in the file beforehand. However, there is no direct connection between the subbasins in which water is abstracted and released, respectively. In order to preserve the water balance, the user must define equally large flows abstracted and added. Since the concentration of the negative point source is defined in the file beforehand, the connection to the quality of the water abstracted water is not automatically preserved.
+Abstraction of water can be defined as a [[start:hype_model_description:hype_human_water#negative_point_source | negative point sources]]. The abstracted water may be constant (or constant at different values for different periods), and thus the same amount of water is removed from the model every time step or given as a time series. The abstraction can be made from different points in the river network within the subbasin. The water is removed while the concentration is kept in the water remaining in the river. To simulate water transfer within the model domain, the same amount of water need to be added as a (positive) point source in another subbasin. This subbasin do not have to be downstream, since its (constant) flow and concentrations is defined in the file beforehand. However, there is no direct connection between the subbasins in which water is abstracted and released, respectively. In order to preserve the water balance, the user must define equally large flows abstracted and added. Since the concentration of the negative point source is defined in the file beforehand, the connection to the quality of the water abstracted water is not automatically preserved.
@@ Line 276: / Line 412: @@
 Alternatively a demanded flow time series from Xobs can be used instead of a constant flow. In this case only one water transfer can be specified for each source lake.
+==== Links to file reference ====
+^Section ^Parameter/Data ^File ^
+|Water transfer through bifurcation|//ALL//|[[start:hype_file_reference:branchdata.txt|BranchData.txt]]|
+|:::|//ldtype=5 and 6//|[[start:hype_file_reference:lakedata.txt|LakeData.txt]]|
+|:::|//lakeid, rate, exp, deltaw0, qprod1, qprod2, datum1,datum2, qamp, qpha, regvol, maxQprod, minflow, obsflow//|:::|
+|:::|//dwtr//|[[start:hype_file_reference:xobs.txt|Xobs.txt]]|
+|Water transfer through negative point source|//ps_vol, fromdate, todate, ps_source//|[[start:hype_file_reference:pointsourcedata.txt|PointSourceData.txt]]|
+|:::|//psid, subid, ps_type, ps_source//|[[start:hype_file_reference:pointsourcedata.txt|PointSourceData.txt]] and [[start:hype_file_reference:pstimeseries.txt|PSTIMESeries.txt]]|
+|Water transfer through water management|//mgmttype=2//|[[start:hype_file_reference:mgmtdata.txt|MgmtData.txt]]|
+|:::|//subid, receiver, flow//|:::|
+|:::|//dwtr//|[[start:hype_file_reference:xobs.txt|Xobs.txt]]|
 ==== Links to relevant procedures in the code ====
@@ Line 290: / Line 440: @@
 |:::|water_transfer_from_outlet_lake| ::: |
+===== Dams =====
+Regulation of flow through dams is described in the Chapter about [[start:hype_model_description:hype_routing| Rivers and lakes]]. Dams of different purposes and regulation management can be simulated. See details in the sections on [[start:hype_model_description:hype_routing#simple_outlet_lake_or_dam_olake| Simple outlet lake or dam]] and the special case of an [[start:hype_model_description:hype_routing#outlet_lake_with_two_outlets| Outlet lake with two outlets]].

HYPE Model Documentation

User Tools

Site Tools

Differences

Page Tools