User Tools

Site Tools


start:hype_model_description:hype_human_water

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_human_water [2019/09/30 10:30]
cpers [Sediment point source]
start:hype_model_description:hype_human_water [2024/02/21 09:14] (current)
cpers [Irrigation water demand]
Line 33: Line 33:
 ^Modules (file) ^Procedures ^ ^Modules (file) ^Procedures ^
 |[[http://​hype.sourceforge.net/​doxy-html/​namespacenpc__surfacewater__processes.html|npc_surfacewater_processes (npc_sw_proc.f90)]] |calculate_river_wetland | |[[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 ==== ==== References ====
Line 44: Line 44:
 ===== Constructed wetlands with water regulation capability ===== ===== Constructed wetlands with water regulation capability =====
  
-The wetlands are 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 definced ​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).+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> <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. Outlet wetlands cannot be present in the same subbasin as an outlet lake. They recieve the flow from the main river of the subbasin.+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 ==== ==== Wetland nutrient processes ====
Line 54: Line 60:
 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. ​ 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//​) that is shallower than a production depth (//​proddep//​) assuming the wetland area is decreaseing ​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 ​orgnaic ​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. ​+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. ​
  
  
Line 83: Line 89:
  
 ^Modules (file) ^Procedures ^ ^Modules (file) ^Procedures ^
-|[[http://​hype.sourceforge.net/​doxy-html/​namespacenpc__surfacewater__processes.html|npc_surfacewater_processes (npc_sw_proc.f90)]] |calculate_wetland_processes ​|+|[[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 | |[[http://​hype.sourceforge.net/​doxy-html/​namespacesurfacewater__processes.html|surfacewater_processes (sw_proc.f90)]] |wetland_watermodel |
 |:::​|T2_processes_in_wetland| |:::​|T2_processes_in_wetland|
Line 106: Line 112:
 <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|}}| |{{:​start:​hype_model_description:​graphirrigation.png?​500|}}|
-|Figure ​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 ​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): 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):
Line 120: Line 136:
 <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 <​m>​T_P</​m>​ 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):​ 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 152: Line 168:
 ==== Irrigation water withdrawal ==== ==== 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 directly after the local discharge and the upstream discharge has been combined 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}}| |{{:​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 === === Irrigation inefficiencies within the sub-basin ===
Line 173: 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 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>
Line 181: 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: 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):  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 189: Line 205:
 <m> W_{L,​D,​s,​l}= W_{L,​D,​s}-{W_{L,​A,​s}}/​{P_{I,​S}} </m> <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>
Line 210: Line 226:
 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>:​ 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,​D2}=W_{R,​D}-{W_{R,​A1}}/​{P_{I,​S}} </​m> ​
Line 229: Line 245:
  
 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//​). 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 ==== ==== Irrigation water application ====
Line 248: Line 266:
 <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>​):​ 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 268: Line 286:
 |Irrigation water demand| |//​imm_start,​ imm_end//​|[[start:​hype_file_reference:​cropdata.txt|CropData.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]]| |Non-submerged crops| |//​demandtype//​|[[start:​hype_file_reference:​mgmtdata.txt|MgmtData.txt]]|
-|:::​|<​m>​K_{CB}</​m>​ calculated from:|//plantday, lengthini, kcbini, lengthdev, lengthmid, kcbmid, lengthlate, kcbend//|[[start:hype_file_reference:cropdata.txt|CropData.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>​DL_{ref}</​m>​|//​dlref//​|:::​|
 |:::​|<​m>​P_{SSWCORR}</​m>​|//​sswcorr//​|[[start:​hype_file_reference:​par.txt|par.txt]]| |:::​|<​m>​P_{SSWCORR}</​m>​|//​sswcorr//​|[[start:​hype_file_reference:​par.txt|par.txt]]|
Line 275: Line 294:
 |Submerged crops|<​m>​WP_1,​ FC_1, EP_1</​m>​ |//wcwp1, wcfc1, wcep1//​|[[start:​hype_file_reference:​par.txt|par.txt]]| |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//​|:::​| |:::​|<​m>​P_{immdepth}</​m>​|//​immdepth//​|:::​|
-|Irrigation water withdrawal| ​|//irrdam, gw_part//​|[[start:​hype_file_reference:​mgmtdata.txt|MgmtData.txt]]| +|Irrigation water withdrawal| ​ |//​irrunlimited//​|[[start:​hype_file_reference:​info.txt|info.txt]]|
-|:::| |//​irrunlimited//​|[[start:​hype_file_reference:​info.txt|info.txt]]| +
-|:::​|<​m>​P_{I,​S}</​m>​|//​pirrs//​|[[start:​hype_file_reference:​par.txt|par.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]]| |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| |//​irrcomp//​|[[start:​hype_file_reference:​par.txt|par.txt]]| +|Withdrawal from sources within the sub-basin| ​|//irrdam, gw_part//​|[[start:​hype_file_reference:​mgmtdata.txt|MgmtData.txt]]| 
-|:::​|<​m>​P_{I,​G}</​m>​|//​pirrg//​|:::​|+|:::​|  ​|//​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]]| |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>​E_{R,​i}</​m>​|//​region_eff//​|:::​|
Line 308: Line 326:
 ===== Point sources ===== ===== 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. 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 ​point source ====+=== Sediment ​ ===
  
 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. 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) ​point sources ====+=== 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 ​ ====
  
-==== Negative ​point source ​====+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.
  
-point source with negative flow denotes an abstraction of waterThe 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.+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 ==== ==== Links to file reference ====
  
 ^Section ^Parameter/​Data ^File ^ ^Section ^Parameter/​Data ^File ^
-|Nutrient ​point sources|//​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 ​- Nutrient|//subid, ps_vol, ps_type, ps_tpconc, ps_tnconc, ps_infrac, ps_spfrac, fromdate, todate//​|[[start:​hype_file_reference:​pointsourcedata.txt|PointSourceData.txt]]| 
-|Tracer T2 (water temperature) ​point sources|//​subid,​ ps_vol, ps_type, ​ps_t2, fromdate, todate//​|:::​| +|Constant or periodical ​point sources ​- Sediment ​|//subid, ps_vol, ps_type, ​ps_tsconc, ps_ssfrac, fromdate, todate//​|:::​| 
-|Tracer T1 point sources|//pstype=0//|:::| +|Constant or periodical ​point sources ​- Tracer T2 |//subid, ps_vol, ps_type, ps_t2, fromdate, todate//​|:::​| 
-|:::​|//​subid,​ ps_vol, ps_t1, fromdate, todate, ps_source//​|:::​| +|:::​|//​subid,​ ps_vol, ps_type=0, ps_t2, fromdate, todate, ps_source//​|:::​| 
-|Negative point source|//​subid,​ ps_vol, 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]]|
  
  
Line 350: Line 391:
 |[[http://​hype.sourceforge.net/​doxy-html/​namespacesurfacewater__processes.html|surfacewater_processes (sw_proc.f90)]]|point_abstraction_from_main_river| |[[http://​hype.sourceforge.net/​doxy-html/​namespacesurfacewater__processes.html|surfacewater_processes (sw_proc.f90)]]|point_abstraction_from_main_river|
 |:::​|point_abstraction_from_outlet_lake | |:::​|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| | ::: |add_tracer_point_source_to_lake|
  
 =====Water abstraction and 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 363: Line 404:
  
 ====Water transfer through negative point source==== ====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 381: Line 422:
 |:::​|//​dwtr//​|[[start:​hype_file_reference:​xobs.txt|Xobs.txt]]| |:::​|//​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]]| |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]]| |Water transfer through water management|//​mgmttype=2//​|[[start:​hype_file_reference:​mgmtdata.txt|MgmtData.txt]]|
 |:::​|//​subid,​ receiver, flow//|:::| |:::​|//​subid,​ receiver, flow//|:::|
start/hype_model_description/hype_human_water.1569832241.txt.gz · Last modified: 2023/11/16 14:28 (external edit)