Difference between revisions of "Process representation across tools"
Line 402: | Line 402: | ||
| style="background: #FFF5FA; vertical-align: top" | | | style="background: #FFF5FA; vertical-align: top" | | ||
<br/> | <br/> | ||
− | '' | + | ''riparian area only'' |
* A-Pan evaporation | * A-Pan evaporation | ||
* Riparian area | * Riparian area | ||
Line 413: | Line 413: | ||
| style="background: #FFF7F5; vertical-align: top" | | | style="background: #FFF7F5; vertical-align: top" | | ||
<br/> | <br/> | ||
− | '' | + | ''riparian area only'' |
* Remaining ET demand (PET - ET from soil) | * Remaining ET demand (PET - ET from soil) | ||
* Riparian area | * Riparian area | ||
Line 425: | Line 425: | ||
| style="background: #F5FFF5; vertical-align: top" ; rowspan= "3" | | | style="background: #F5FFF5; vertical-align: top" ; rowspan= "3" | | ||
<br/> | <br/> | ||
− | '' | + | ''riparian area only'' |
</br></br>'''Indirect representation:''' | </br></br>'''Indirect representation:''' | ||
</br>''Specified riparian zone HRU can receive a user-specified fraction of the aquifer outflow from connected upslope HRUs. This water is added to riparian HRU soil in the B-horizon, where it can be accessed for ET and can recharge GW.'' | </br>''Specified riparian zone HRU can receive a user-specified fraction of the aquifer outflow from connected upslope HRUs. This water is added to riparian HRU soil in the B-horizon, where it can be accessed for ET and can recharge GW.'' | ||
Line 443: | Line 443: | ||
| style="background: #F5FCFF; vertical-align: top" | | | style="background: #F5FCFF; vertical-align: top" | | ||
<br/> | <br/> | ||
− | '' | + | ''riparian area only'' |
''represented through capillary rise into the soil driven by ET demand'' | ''represented through capillary rise into the soil driven by ET demand'' | ||
* Remaining ET demand (PET - Canopy evap. - Ponded evap. - ET from soil) | * Remaining ET demand (PET - Canopy evap. - Ponded evap. - ET from soil) |
Revision as of 15:07, 26 November 2023
PAGE IN PROGRESS - MORE COMING SOON!
building process representation overview tables + links to more specific pages about individual processes
Canopy interception and evaporation (vs throughfall)
Algorithm description |
WRSM-Pitman | SPATSIM-Pitman | ACRU4 | SWAT2012 | MIKE-SHE, semi-distributed & fully distributed |
---|---|---|---|---|---|
Algorithm inputs (input data, parameters, model-calculated states/storages) |
|
|
|
|
|
Function type |
exponential & threshold | exponential & threshold | threshold | threshold | |
Thresholds |
yes:
|
yes:
|
yes:
|
yes:
|
Infiltration into soil moisture (vs surface runoff or surface ponding)
Note: This excludes the case of a modelling unit (HRU, grid cell, area within a subcatchment, etc.) is designated as impervious. In this case, rain inputs would become surface runoff, potentially with a portion staying behind as surface storage/ponding if the area has attenuation specified (to represent roughness and flatness).
Algorithm description |
WRSM-Pitman | SPATSIM-Pitman | ACRU4 | SWAT2012 | MIKE-SHE, semi-distributed, more conceptual |
MIKE-SHE, fully-distributed, more physical |
---|---|---|---|---|---|---|
Algorithm inputs (input data, parameters, model-calculated states/storages) |
|
|
|
|
|
|
Function type |
non-linear & threshold | non-linear & threshold | power & threshold | power & threshold | linear (rate) & threshold | non-linear & threshold |
Thresholds |
yes:
|
yes:
|
yes:
|
yes:
|
yes:
|
yes:
|
Surface runoff to channel network
Note on surface runoff vs ponding and surface storage: Water reaching the land surface which does not infiltrate into soil in a timestep, will either become surface runoff or remain as surface ponding/surface storage. In some models (e.g. Pitman models) all water that does not infiltrate becomes surface runoff. This makes sense when the timestep is long (e.g. a month). If the model represents surface storage, then in subsequent model timesteps this water can evaporate, infiltrate, and/or become surface runoff in the next timestep. Some models have relatively short timesteps (subdaily, daily) compared to the rate at which water would move across a modelled land unit (which could be large, rough, and/or flat, slowing the flow rate), explaining why some water will be considered 'surface storage' in one timestep and then 'surface runoff' in the next timestep in the model. MIKE-SHE can also consider that land surfaces can be very rough, or have dips that trap water, and so some amount surface water will not be able to runoff at all, regardless of a time delay. This water will both evaporate and infiltrate over time.
Algorithm description |
WRSM-Pitman | SPATSIM-Pitman | ACRU4 | SWAT2012 | MIKE-SHE, semi-distributed, more conceptual |
MIKE-SHE, fully-distributed, more physical |
---|---|---|---|---|---|---|
Algorithm inputs (input data, parameters, model-calculated states/storages) |
*Month timestep: all water not infiltrating becomes runoff
|
*Month timestep: all water not infiltrating becomes runoff
|
*Lag coefficient separates "quickflow"~surface runoff from "delayed-flow"~interflow. Quickflow portion reaches the channel on the same day generated (rain day). The rest is lagged over subsequent days |
|
|
|
Function type |
(no transformation) | (no transformation) | (no transformation) | non-linear | non-linear & threshold | non-linear & threshold |
Thresholds |
no*
|
no*
|
no*
|
no*
|
yes:
|
yes:
|
Evapotranspiration (ET) from soil moisture (SM)
Note: More coverage of evapotranspiration related terminology and inputs across different tools can be found here
Algorithm description |
WRSM-Pitman | SPATSIM-Pitman | ACRU4 | SWAT2012 | MIKE-SHE, semi-distributed, more conceptual |
MIKE-SHE, fully-distributed, more physical |
---|---|---|---|---|---|---|
Algorithm inputs (input data, parameters, model-calculated states/storages) |
*determines linear decline of ET with soil moisture decline
|
*determines linear decline of ET with soil moisture decline
|
*ET assumed to also decline if soil gets close to saturation, waterlogging, unless wetland plants
|
|
|
|
Function type |
linear & threshold | linear & threshold | multi-part linear & threshold | non-linear & threshold | multi-part linear & threshold | non-linear & threshold |
Thresholds |
yes:
|
yes:
|
yes:
|
yes:
yes:
|
yes:
|
yes:
|
Evapotranspiration (ET) from groundwater (GW)
Note: More coverage of evapotranspiration related terminology and inputs across different tools can be found here
Algorithm description |
WRSM-Pitman (Sami GW) |
SPATSIM-Pitman (Hughes GW) |
ACRU4 | SWAT2012 | MIKE-SHE, semi-distributed, more conceptual |
MIKE-SHE, fully-distributed, more physical |
---|---|---|---|---|---|---|
Algorithm inputs (input data, parameters, model-calculated states/storages) |
|
|
|
+ all inputs for ET from soil
|
+ all inputs for ET from soil
|
+ vegetation property inputs for ET from soil
|
Function type |
non-linear & threshold | non-linear & threshold | non-linear & threshold | non-linear & threshold | non-linear & threshold | |
Thresholds |
yes:
|
yes:
|
yes:
|
yes:
|
yes:
|