Rhessys - User contributions [en]

Ksat vertical

2011-01-13T20:03:01Z

Dgroulx:

Value should be [0,1]. A value of 0 represents an impervious surface, 1 a fully permeable surface.

Climate data

2011-01-11T01:08:07Z

Dgroulx: /* Met Station Based Climate Data */

==Met Station Based Climate Data==

Climate data in this form is based on having a single file for each meteorological station available. Each base station is represented by
it's own base station file, and separate files for each climate variable as listed in the base station file. At the very least, daily time
series of tmin, tmax, and rain are required.

Climate inputs are linked to particular zones by the climate station ID affiliated with that zone. A single climate station (or base station) will typically serve multiple zones within the landscape. Each base station is described by a base station file.

Example Base Station File:
<pre>
101 base_station_id
100.0 x_coordinate
100.0 y_coordinate
22.9 z_coordinate
2.0 effective_lai
22.9 screen_height
clim\rbw_prime_annual annual_climate_prefix
0 number_non_critical_annual_sequences
clim\rbw_prime_monthly monthly_climate_prefix
0 number_non_critical_monthly_sequences
clim\rbw daily_climate_prefix
2
ndep_NO3
ndep_NH4
0
clim\rbw_prime_hourly hourly_climate_prefix
0 number_non_critical_hourly_sequences
</pre>

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Climate Input Sequence Name / File Extension'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Units'''
|-
| rain||precipitation (rain + snow)* required||meters
|-
| tmin||minimum daily temperature* required||°C
|-
| tmax||maximum daily temperature* required||°C
|-
| tavg||average daily temperature||°C
|-
| dayl||day length||seconds
|-
| daytime_rain_duration||duration of rainfall||hours
|-
| LAI_scalar||zone and seasonal scaling of LAI - only applied to stratum of non-zero height||Unitless
|-
| Ldown||incoming longwave radiation||KJ / (meters2)/day
|-
| Kdown_direct||incoming direct shortwave radiation||KJ / (meters2)/day
|-
| Kdown_diffuse||incoming diffuse shortwave radiation||KJ / (meters2)/day
|-
| ndep_NO3||nitrogen deposition as NO3||kg / (meters2)/day
|-
| ndep_NH4||nitrogen deposition as NH4||kg / (meters2) /day
|-
| PAR_direct||incoming direct PAR radiation||KJ / (meters2)/day
|-
| PAR_diffuse||incoming diffuse PAR radiation||KJ / (meters2)/day
|-
| relative_humidity||Relative Humidity||Range (0-1)
|-
| tday||Mean Daytime Temperature||°C
|-
| tnightmax||Night time temperature at sundown (used for soil heat flux)||°C
|-
| tsoil||Soil temperature||°C
|-
| vpd||Vapour pressure deficit||Pa
|-
| wind||Wind speed||meters/ sec.
|-
| CO2||Carbon Dioxide||parts per million/year
|-
| lapse_rate_tmin || minimum daily temperature lapse rate with elevation || °C/m
|-
| lapse_rate_tmax || maximum daily temperature lapse rate with elevation || °C/m

|}

All possible base station filenames must be listed in the worldfile header, as described in the discussion of grass2world below.

===Format for Time Series Input Files===
The first line of each input time series file must give the start date of the time series. The start date of the input must precede the start date listed in the worldfile. Following the start date, time series values are listed sequentially. For example:
example_simulation_daily.rain will contain the following

<pre>
1986 1 1 1
0.0028
0.000
0.0157
0.000
…
</pre>

==Gridded Climate Data==

Climate data in gridded form is not tied to any particular met station, but is a grid of climate data over the watershed such as an interpolation
between multiple climate stations, or downscaled data from a climate model. While it is possible to fake gridded climate data by representing each grid cell as a unique climate station, using gridded climate files is easier to work with.

Gridded climate data will have only a single base file, and a single file for each climate variable. The base file is identical to that of non-gridded climate data,
except that the first line that set the base station id is replaced with a line specifying the total number of grid cells. So if you had a gridded climate dataset
identical to the one specified above, but with 4 cells, your climate base file would be: 
<pre>
4 grid_cells
100.0 x_coordinate
100.0 y_coordinate
22.9 z_coordinate
2.0 effective_lai
22.9 screen_height
clim\rbw_prime_annual annual_climate_prefix
0 number_non_critical_annual_sequences
clim\rbw_prime_monthly monthly_climate_prefix
0 number_non_critical_monthly_sequences
clim\rbw daily_climate_prefix
2
ndep_NO3
ndep_NH4
0
clim\rbw_prime_hourly hourly_climate_prefix
0 number_non_critical_hourly_sequences
</pre>

The climate variable files will also look similar to those from the standard met station based climate input. The only major difference
is inserting a line after the first line starting date that specifies the grid cell index for each column of data. These numbers must match
up with the values of the GIS map specified as the base_station_ID variable in your template file. The following is a temperature climate
file with four grid cells with indices 0-3.

<pre>
1986 1 1 1
0 1 2 3
24 26 27 23
24 25 25 21
21 23 22 22
19 21 19 18
…
</pre>

===Running RHESSys with Gridded Climate Data===

# Edit your template file to refer to the climate base file.
# When running RHESSys, use the command line option '-asciigrid' and RHESSs will properly deal with your gridded climate data.
# There's no step 3.

Contacting RHESSys Developers

2010-10-27T19:21:30Z

Dgroulx: /* Bug Reports and Feature Requests */

==User Mailing List==
For questions involving the compiling and running of RHESSys simulations, please
join our user mailing list at http://lists.sourceforge.net/mailman/listinfo/rhessys-users

==Developer Mailing List==
For discussion about the actual RHESSys source code and direction of development, please
join our developer mailing list at http://lists.sourceforge.net/mailman/listinfo/rhessys-developer

==Bug Reports and Feature Requests==
If you wish to report a bug or request new RHESSys functionality, the best way is
to use the RHESSys trac page. Go to https://sourceforge.net/apps/trac/rhessys/,
then click on the New Ticket button on the top menu bar. Note that you will
have to create and login with a sourceforge account before you can create
a new ticket.

Contacting RHESSys Developers

2010-10-27T19:21:05Z

Dgroulx: /* User Mailing List */

Contacting RHESSys Developers

2010-10-27T19:20:17Z

Dgroulx: Created page with '==User Mailing List== For questions involving the compiling and running of RHESSys simulations, please join our user mailing list at https://lists.sourceforge.net/lists/listinfo/…'

==User Mailing List==
For questions involving the compiling and running of RHESSys simulations, please
join our user mailing list at https://lists.sourceforge.net/lists/listinfo/rhessys-users.

==Developer Mailing List==
For discussion about the actual RHESSys source code and direction of development, please
join our developer mailing list at http://lists.sourceforge.net/mailman/listinfo/rhessys-developer

==Bug Reports and Feature Requests==
If you wish to report a bug or request new RHESSys functionality, the best way is
to use the RHESSys trac page. Go to https://sourceforge.net/apps/trac/rhessys/,
then click on the New Ticket button on the top menu bar.

RHESSys

2010-10-27T19:13:45Z

Dgroulx: /* Using RHESSys */

== Using RHESSys ==

[[How to get RHESSys]]

[[Directory structure]]

[[Creating Patch Maps]]

[[Contacting RHESSys Developers]]

== Publications ==
[[Published Literature]]

== RHESSys Tutorial ==

[[Preparing input data sets]]

[[Generating RHESSys input files]]

[[Calibrating and running RHESSys]]

[[Visualizing Spatial Output]]

[[Command Line Options]]

[[Performing a Redefine World]]

==RHESSys File Formats==

[[Climate data]]

[[Default files]]

[[Worldfiles]]

[[Temporal Event Control files]]

[[Flow Table]]

[[Output Files]]

==GRASS GIS==

[[Developing custom GRASS programs]]

==Data Sources==

[http://wiki.icess.ucsb.edu/snow/index.php/STATSGO2-soil_data STATSGO2-soil data]

[[Incorporating LANDSAT data into GRASS]]

[[Climate data scaling with PRISM]]

== Getting started (wiki help) ==
Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.
* [http://www.mediawiki.org/wiki/Help:Configuration_settings Configuration settings list]
* [http://www.mediawiki.org/wiki/Help:FAQ MediaWiki FAQ]
* [http://mail.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]

Flow Table

2010-10-26T16:45:15Z

Dgroulx:

{| border="1" cellpadding="5" {{table}}
| ''Patch ID''
| ''Zone ID''
| ''Hill ID''
| ''Centroid -X''
| ''Centroid - Y''
| ''Centroid - Z''
| ''Accumulated-Area*''
| ''Land type''
| ''Total Gamma''
| ''Number of Adjacent Patches''
|-
| colspan="10" | Then for each adjacent patch
|-
| ''Patch ID''
| ''Zone ID''
| ''Hill ID''
| ''Local Gamma''
|-
| colspan="10" | And for road patches only - print ID of closest downslope stream patch
|-
| ''Patch ID''
| ''Zone ID''
| ''Hill ID''
| ''Road Width''
|}

RHESSys does not currently use accumulated area. For computational efficiency, accumulated area will not be calculated and output as 0.0 unless -s option is chosen.

Climate data

2010-10-13T21:19:28Z

Dgroulx: /* Running RHESSys with Gridded Climate Data */

==Met Station Based Climate Data==

Climate data in this form is based on having a single file for each meteorological station available. Each base station is represented by
it's own base station file, and separate files for each climate variable as listed in the base station file. At the very least, daily time
series of tmin, tmax, and rain are required.

Climate inputs are linked to particular zones by the climate station ID affiliated with that zone. A single climate station (or base station) will typically serve multiple zones within the landscape. Each base station is described by a base station file.

Example Base Station File:
<pre>
101 base_station_id
100.0 x_coordinate
100.0 y_coordinate
22.9 z_coordinate
2.0 effective_lai
22.9 screen_height
clim\rbw_prime_annual annual_climate_prefix
0 number_non_critical_annual_sequences
clim\rbw_prime_monthly monthly_climate_prefix
0 number_non_critical_monthly_sequences
clim\rbw daily_climate_prefix
2
ndep_NO3
ndep_NH4
0
clim\rbw_prime_hourly hourly_climate_prefix
0 number_non_critical_hourly_sequences
</pre>

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Climate Input Sequence Name / File Extension'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Units'''
|-
| rain||precipitation (rain + snow)* required||meters
|-
| tmin||minimum daily temperature* required||°C
|-
| tmax||maximum daily temperature* required||°C
|-
| dayl||day length||seconds
|-
| daytime_rain_duration||duration of rainfall||hours
|-
| LAI_scalar||zone and seasonal scaling of LAI - only applied to stratum of non-zero height||Unitless
|-
| Ldown||incoming longwave radiation||KJ / (meters2)/day
|-
| Kdown_direct||incoming direct shortwave radiation||KJ / (meters2)/day
|-
| Kdown_diffuse||incoming diffuse shortwave radiation||KJ / (meters2)/day
|-
| ndep_NO3||nitrogen deposition as NO3||kg / (meters2)/day
|-
| ndep_NH4||nitrogen deposition as NH4||kg / (meters2) /day
|-
| PAR_direct||incoming direct PAR radiation||KJ / (meters2)/day
|-
| PAR_diffuse||incoming diffuse PAR radiation||KJ / (meters2)/day
|-
| relative_humidity||Relative Humidity||Range (0-1)
|-
| tday||Mean Daytime Temperature||°C
|-
| tnightmax||Night time temperature at sundown (used for soil heat flux)||°C
|-
| tsoil||Soil temperature||°C
|-
| vpd||Vapour pressure deficit||Pa
|-
| wind||Wind speed||meters/ sec.
|-
| CO2||Carbon Dioxide||parts per million/year
|-
| lapse_rate_tmin || minimum daily temperature lapse rate with elevation || °C/m
|-
| lapse_rate_tmax || maximum daily temperature lapse rate with elevation || °C/m

|}

All possible base station filenames must be listed in the worldfile header, as described in the discussion of grass2world below.

===Format for Time Series Input Files===
The first line of each input time series file must give the start date of the time series. The start date of the input must precede the start date listed in the worldfile. Following the start date, time series values are listed sequentially. For example:
example_simulation_daily.rain will contain the following

<pre>
1986 1 1 1
0.0028
0.000
0.0157
0.000
…
</pre>

==Gridded Climate Data==

Climate data in gridded form is not tied to any particular met station, but is a grid of climate data over the watershed such as an interpolation
between multiple climate stations, or downscaled data from a climate model. While it is possible to fake gridded climate data by representing each grid cell as a unique climate station, using gridded climate files is easier to work with.

Gridded climate data will have only a single base file, and a single file for each climate variable. The base file is identical to that of non-gridded climate data,
except that the first line that set the base station id is replaced with a line specifying the total number of grid cells. So if you had a gridded climate dataset
identical to the one specified above, but with 4 cells, your climate base file would be: 
<pre>
4 grid_cells
100.0 x_coordinate
100.0 y_coordinate
22.9 z_coordinate
2.0 effective_lai
22.9 screen_height
clim\rbw_prime_annual annual_climate_prefix
0 number_non_critical_annual_sequences
clim\rbw_prime_monthly monthly_climate_prefix
0 number_non_critical_monthly_sequences
clim\rbw daily_climate_prefix
2
ndep_NO3
ndep_NH4
0
clim\rbw_prime_hourly hourly_climate_prefix
0 number_non_critical_hourly_sequences
</pre>

The climate variable files will also look similar to those from the standard met station based climate input. The only major difference
is inserting a line after the first line starting date that specifies the grid cell index for each column of data. These numbers must match
up with the values of the GIS map specified as the base_station_ID variable in your template file. The following is a temperature climate
file with four grid cells with indices 0-3.

<pre>
1986 1 1 1
0 1 2 3
24 26 27 23
24 25 25 21
21 23 22 22
19 21 19 18
…
</pre>

===Running RHESSys with Gridded Climate Data===

# Edit your template file to refer to the climate base file.
# When running RHESSys, use the command line option '-asciigrid' and RHESSs will properly deal with your gridded climate data.
# There's no step 3.

Command Line Options

2010-10-13T21:08:17Z

Dgroulx:

{| border="1"
| -w filename (required) || Name of the worldfile
|-
| -t filename (required)||Name of the tecfile
|-
| -r filename||Necessary for explicit routing - if "-r" not used then TOPMODEL routing will be used
|-
| -b optional ID||Necessary for basin output, the ID is used to specify individual basins, no ID implies all basins
|-
| -h optional ID||Necessary for hillslope output, the ID is used to specify individual hillslopes, no ID implies all hillslopes
|-
| -z optional ID||Necessary for zone output, the ID is used to specify individual zones, no ID implies all zones
|-
| -p optional ID||Necessary for patch output, the ID is used to specify individual patches, no ID implies all patches
|-
| -c optional ID||Necessary for stratum output, the ID is used to specify individual strata, no ID implies all strata
|-
| -g||"-g" specifies dynamic version of RHESSys, if "-g" not used, then RHESSys defaults to static mode.
|-
| -s value value <optional value>||Sensitivity parameters (-s must be followed by two values and a third optional value). Values specify three multipliers which are used to scale specific variables initialized in the worldfile. The first required value, (a sen1) designates m, the decay of hydraulic conductivity with depth, the second required value, (a sen2) designates K, hydraulic conductivity at the surface, and the third optional value, (a sen3) designates soil depth. In the current implementation, the m, K, and soil depth parameter values initialized for all patches in the worldfile are multiplied by 1) a sen1 2) a sen2 and 3) a sen3 respectively during a simulation. User must modify code to permit calibration based on other parameters.
|-
| -gw value value||Sensitivity parameters (-gw must be followed by two values) Specifies two multipliers which are used to scale specific variables. The first value is the multiplier of the sat_to_gw_coeff in the hillslope default file (representing the amount of water moving from the saturated store to the groundwater store). The second value is the multiplier of the gw_loss_coeff in the hillslope default file (representing the amount of water moving from the groundwater store to the stream).
|-
| -pre character string||Prefix to be used for output files
|-
| -st year month day||Start date (switch must be followed by the date), this overrides the start date used in the worldfile
|-
| -ed year month day||End date (switch must be followed by the date), this overrides the end date used in the worldfile
|-
| -snowdistb value||If this flag is used RHESSys will run snow redistribution for each patch. To use this option there must be an additional state variable at the patch level in the worldfile. An optional tolerance parameter can be included with the command line to limit change in the water balance associated with snow redistribution.
|-
| -th value value||The first value is the threshold value for saturation deficit (it allows output of the number of days patch saturation falls below the threshold (water stress days), which can be used an annual water stress index). The second value is the threshold value for streamflow (it allows output of the number of low flow days below some set threshold). The -th option is meant to be used with yearly output - which requires the print_yearly_on event in the tecfile.
|-
| -tmp value||Sensitivity analysis of soil N decay rate
|-
| -dor value||Sets DON loss rate as a specified proportion of total mineralization, with DOC rate set using appropriate DON/DOC ratios (e.g. -dor 0.03 sets the DON loss rate as 3% of total mineralization)
|-
| -old||Read a worldfile from the previous version of RHESSys and set any new world state variables to defaults (in this case Ksat_vertical to 1.0), note any world_state output will be a ver5.4 compatible worldfile
|-
| -vgsen value value value||Multipliers which alter vegetation specific parameters. The first value multiples specific leaf areas. The second value multiplies the ratio of shaded to sunlit leaf area. The third value is a multiplier used only with the Dickenson algorithm of carbon allocation (set at the epc.allocation_flag variable in the vegetation definition file). It changes the allocation of net photosynthate sensitivity based on the current LAI. If not using the Dickenson strategy of carbon allocation (i.e. using Waring or default Constant strategies), set third value to 1.0. (i.e. -vgsen 1.0 2.0 1.0)
|-
| -csv||Produce comma delimited output (this overrides previous use of output_csv_... in the tec file
|-
| -asciigrid||Read in gridded climate data. For information on these files, see [[Climate data#Gridded Climate Data|Gridded Climate Data]]
|}

Command Line Options

2010-10-13T21:07:56Z

Dgroulx:

Climate data

2010-10-13T21:05:33Z

Dgroulx: /* Gridded Climate Data */

==Met Station Based Climate Data==

Climate data in this form is based on having a single file for each meteorological station available. Each base station is represented by
it's own base station file, and separate files for each climate variable as listed in the base station file. At the very least, daily time
series of tmin, tmax, and rain are required.

Climate inputs are linked to particular zones by the climate station ID affiliated with that zone. A single climate station (or base station) will typically serve multiple zones within the landscape. Each base station is described by a base station file.

Example Base Station File:
<pre>
101 base_station_id
100.0 x_coordinate
100.0 y_coordinate
22.9 z_coordinate
2.0 effective_lai
22.9 screen_height
clim\rbw_prime_annual annual_climate_prefix
0 number_non_critical_annual_sequences
clim\rbw_prime_monthly monthly_climate_prefix
0 number_non_critical_monthly_sequences
clim\rbw daily_climate_prefix
2
ndep_NO3
ndep_NH4
0
clim\rbw_prime_hourly hourly_climate_prefix
0 number_non_critical_hourly_sequences
</pre>

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Climate Input Sequence Name / File Extension'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Units'''
|-
| rain||precipitation (rain + snow)* required||meters
|-
| tmin||minimum daily temperature* required||°C
|-
| tmax||maximum daily temperature* required||°C
|-
| dayl||day length||seconds
|-
| daytime_rain_duration||duration of rainfall||hours
|-
| LAI_scalar||zone and seasonal scaling of LAI - only applied to stratum of non-zero height||Unitless
|-
| Ldown||incoming longwave radiation||KJ / (meters2)/day
|-
| Kdown_direct||incoming direct shortwave radiation||KJ / (meters2)/day
|-
| Kdown_diffuse||incoming diffuse shortwave radiation||KJ / (meters2)/day
|-
| ndep_NO3||nitrogen deposition as NO3||kg / (meters2)/day
|-
| ndep_NH4||nitrogen deposition as NH4||kg / (meters2) /day
|-
| PAR_direct||incoming direct PAR radiation||KJ / (meters2)/day
|-
| PAR_diffuse||incoming diffuse PAR radiation||KJ / (meters2)/day
|-
| relative_humidity||Relative Humidity||Range (0-1)
|-
| tday||Mean Daytime Temperature||°C
|-
| tnightmax||Night time temperature at sundown (used for soil heat flux)||°C
|-
| tsoil||Soil temperature||°C
|-
| vpd||Vapour pressure deficit||Pa
|-
| wind||Wind speed||meters/ sec.
|-
| CO2||Carbon Dioxide||parts per million/year
|-
| lapse_rate_tmin || minimum daily temperature lapse rate with elevation || °C/m
|-
| lapse_rate_tmax || maximum daily temperature lapse rate with elevation || °C/m

|}

All possible base station filenames must be listed in the worldfile header, as described in the discussion of grass2world below.

===Format for Time Series Input Files===
The first line of each input time series file must give the start date of the time series. The start date of the input must precede the start date listed in the worldfile. Following the start date, time series values are listed sequentially. For example:
example_simulation_daily.rain will contain the following

<pre>
1986 1 1 1
0.0028
0.000
0.0157
0.000
…
</pre>

==Gridded Climate Data==

Climate data in gridded form is not tied to any particular met station, but is a grid of climate data over the watershed such as an interpolation
between multiple climate stations, or downscaled data from a climate model. While it is possible to fake gridded climate data by representing each grid cell as a unique climate station, using gridded climate files is easier to work with.

Gridded climate data will have only a single base file, and a single file for each climate variable. The base file is identical to that of non-gridded climate data,
except that the first line that set the base station id is replaced with a line specifying the total number of grid cells. So if you had a gridded climate dataset
identical to the one specified above, but with 4 cells, your climate base file would be: 
<pre>
4 grid_cells
100.0 x_coordinate
100.0 y_coordinate
22.9 z_coordinate
2.0 effective_lai
22.9 screen_height
clim\rbw_prime_annual annual_climate_prefix
0 number_non_critical_annual_sequences
clim\rbw_prime_monthly monthly_climate_prefix
0 number_non_critical_monthly_sequences
clim\rbw daily_climate_prefix
2
ndep_NO3
ndep_NH4
0
clim\rbw_prime_hourly hourly_climate_prefix
0 number_non_critical_hourly_sequences
</pre>

The climate variable files will also look similar to those from the standard met station based climate input. The only major difference
is inserting a line after the first line starting date that specifies the grid cell index for each column of data. These numbers must match
up with the values of the GIS map specified as the base_station_ID variable in your template file. The following is a temperature climate
file with four grid cells with indices 0-3.

<pre>
1986 1 1 1
0 1 2 3
24 26 27 23
24 25 25 21
21 23 22 22
19 21 19 18
…
</pre>

===Running RHESSys with Gridded Climate Data===

# Edit your template file to refer to the climate base file.
# When running RHESSys, use the command line option '--asciigrid' and RHESSs will properly deal with your gridded climate data.
# There's no step 3.

Climate data

2010-10-13T20:56:04Z

Dgroulx:

==Met Station Based Climate Data==

Climate data in this form is based on having a single file for each meteorological station available. Each base station is represented by
it's own base station file, and separate files for each climate variable as listed in the base station file. At the very least, daily time
series of tmin, tmax, and rain are required.

Climate inputs are linked to particular zones by the climate station ID affiliated with that zone. A single climate station (or base station) will typically serve multiple zones within the landscape. Each base station is described by a base station file.

Example Base Station File:
<pre>
101 base_station_id
100.0 x_coordinate
100.0 y_coordinate
22.9 z_coordinate
2.0 effective_lai
22.9 screen_height
clim\rbw_prime_annual annual_climate_prefix
0 number_non_critical_annual_sequences
clim\rbw_prime_monthly monthly_climate_prefix
0 number_non_critical_monthly_sequences
clim\rbw daily_climate_prefix
2
ndep_NO3
ndep_NH4
0
clim\rbw_prime_hourly hourly_climate_prefix
0 number_non_critical_hourly_sequences
</pre>

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Climate Input Sequence Name / File Extension'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Units'''
|-
| rain||precipitation (rain + snow)* required||meters
|-
| tmin||minimum daily temperature* required||°C
|-
| tmax||maximum daily temperature* required||°C
|-
| dayl||day length||seconds
|-
| daytime_rain_duration||duration of rainfall||hours
|-
| LAI_scalar||zone and seasonal scaling of LAI - only applied to stratum of non-zero height||Unitless
|-
| Ldown||incoming longwave radiation||KJ / (meters2)/day
|-
| Kdown_direct||incoming direct shortwave radiation||KJ / (meters2)/day
|-
| Kdown_diffuse||incoming diffuse shortwave radiation||KJ / (meters2)/day
|-
| ndep_NO3||nitrogen deposition as NO3||kg / (meters2)/day
|-
| ndep_NH4||nitrogen deposition as NH4||kg / (meters2) /day
|-
| PAR_direct||incoming direct PAR radiation||KJ / (meters2)/day
|-
| PAR_diffuse||incoming diffuse PAR radiation||KJ / (meters2)/day
|-
| relative_humidity||Relative Humidity||Range (0-1)
|-
| tday||Mean Daytime Temperature||°C
|-
| tnightmax||Night time temperature at sundown (used for soil heat flux)||°C
|-
| tsoil||Soil temperature||°C
|-
| vpd||Vapour pressure deficit||Pa
|-
| wind||Wind speed||meters/ sec.
|-
| CO2||Carbon Dioxide||parts per million/year
|-
| lapse_rate_tmin || minimum daily temperature lapse rate with elevation || °C/m
|-
| lapse_rate_tmax || maximum daily temperature lapse rate with elevation || °C/m

|}

All possible base station filenames must be listed in the worldfile header, as described in the discussion of grass2world below.

===Format for Time Series Input Files===
The first line of each input time series file must give the start date of the time series. The start date of the input must precede the start date listed in the worldfile. Following the start date, time series values are listed sequentially. For example:
example_simulation_daily.rain will contain the following

<pre>
1986 1 1 1
0.0028
0.000
0.0157
0.000
…
</pre>

==Gridded Climate Data==

Climate data in gridded form is not tied to any particular met station, but is a grid of climate data over the watershed such as an interpolation
between multiple climate stations, or downscaled data from a climate model. While it is possible to fake gridded climate data by representing each grid cell as a unique climate station, using gridded climate files is easier to work with.

Gridded climate data will have only a single base file, and a single file for each climate variable. The base file is identical to that of non-gridded climate data,
except that the first line that set the base station id is replaced with a line specifying the total number of grid cells. So if you had a gridded climate dataset
identical to the one specified above, but with 90 cells, your climate base file would be: 
<pre>
90 grid_cells
100.0 x_coordinate
100.0 y_coordinate
22.9 z_coordinate
2.0 effective_lai
22.9 screen_height
clim\rbw_prime_annual annual_climate_prefix
0 number_non_critical_annual_sequences
clim\rbw_prime_monthly monthly_climate_prefix
0 number_non_critical_monthly_sequences
clim\rbw daily_climate_prefix
2
ndep_NO3
ndep_NH4
0
clim\rbw_prime_hourly hourly_climate_prefix
0 number_non_critical_hourly_sequences
</pre>

The climate variable files will also look similar to those from the standard met station based climate input. The only major difference
is inserting a line after the first line starting date that specifies the grid cell index for each column of data. These numbers must match
up with the values of the GIS map specified as the base_station_ID variable in your template file. The following is a temperature climate
file with four grid cells with indices 0-3.

<pre>
1986 1 1 1
0 1 2 3
24 26 27 23
24 25 25 21
21 23 22 22
19 21 19 18
…
</pre>

===Running RHESSys with Gridded Climate Data===

# Edit your template file to refer to the climate base file.
# When running RHESSys, use the command line option '--asciigrid' and RHESSs will properly deal with your gridded climate data.
# There's no step 3.

Climate data

2010-10-13T20:17:09Z

Dgroulx:

==Met Station Based Climate Data==

Climate data in this form is based on having a single file for each meteorological station available. Each base station is represented by
it's own base station file, and separate files for each climate variable as listed in the base station file. At the very least, daily time
series of tmin, tmax, and rain are required.

Climate inputs are linked to particular zones by the climate station ID affiliated with that zone. A single climate station (or base station) will typically serve multiple zones within the landscape. Each base station is described by a base station file.

Example Base Station File:
<pre>
101 base_station_id
100.0 x_coordinate
100.0 y_coordinate
22.9 z_coordinate
2.0 effective_lai
22.9 screen_height
clim\rbw_prime_annual annual_climate_prefix
0 number_non_critical_annual_sequences
clim\rbw_prime_monthly monthly_climate_prefix
0 number_non_critical_monthly_sequences
clim\rbw daily_climate_prefix
2
ndep_NO3
ndep_NH4
0
clim\rbw_prime_hourly hourly_climate_prefix
0 number_non_critical_hourly_sequences
</pre>

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Climate Input Sequence Name / File Extension'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Units'''
|-
| rain||precipitation (rain + snow)* required||meters
|-
| tmin||minimum daily temperature* required||°C
|-
| tmax||maximum daily temperature* required||°C
|-
| dayl||day length||seconds
|-
| daytime_rain_duration||duration of rainfall||hours
|-
| LAI_scalar||zone and seasonal scaling of LAI - only applied to stratum of non-zero height||Unitless
|-
| Ldown||incoming longwave radiation||KJ / (meters2)/day
|-
| Kdown_direct||incoming direct shortwave radiation||KJ / (meters2)/day
|-
| Kdown_diffuse||incoming diffuse shortwave radiation||KJ / (meters2)/day
|-
| ndep_NO3||nitrogen deposition as NO3||kg / (meters2)/day
|-
| ndep_NH4||nitrogen deposition as NH4||kg / (meters2) /day
|-
| PAR_direct||incoming direct PAR radiation||KJ / (meters2)/day
|-
| PAR_diffuse||incoming diffuse PAR radiation||KJ / (meters2)/day
|-
| relative_humidity||Relative Humidity||Range (0-1)
|-
| tday||Mean Daytime Temperature||°C
|-
| tnightmax||Night time temperature at sundown (used for soil heat flux)||°C
|-
| tsoil||Soil temperature||°C
|-
| vpd||Vapour pressure deficit||Pa
|-
| wind||Wind speed||meters/ sec.
|-
| CO2||Carbon Dioxide||parts per million/year
|-
| lapse_rate_tmin || minimum daily temperature lapse rate with elevation || °C/m
|-
| lapse_rate_tmax || maximum daily temperature lapse rate with elevation || °C/m

|}

All possible base station filenames must be listed in the worldfile header, as described in the discussion of grass2world below.

===Format for Time Series Input Files===
The first line of each input time series file must give the start date of the time series. The start date of the input must precede the start date listed in the worldfile. Following the start date, time series values are listed sequentially. For example:
example_simulation_daily.rain will contain the following

<pre>
1986 1 1 1
0.0028
0.000
0.0157
0.000
…
</pre>

==Gridded Climate Data==

Climate data in gridded form is not tied to any particular met station, but is a grid of climate data over the watershed such as an interpolation
between multiple climate stations, or downscaled data from a climate model. While it is possible to fake gridded climate data by representing each grid cell as a unique climate station, using gridded climate files is easier to work with.

Gridded climate data will have only a single base file, and a single file for each climate variable. The base file is identical to that of non-gridded climate data,
except that the first line that set the base station id is replaced with a line specifying the total number of grid cells. So if you had a gridded climate dataset
identical to the one specified above, but with 90 cells, your climate base file would be: 
<pre>
90 grid_cells
100.0 x_coordinate
100.0 y_coordinate
22.9 z_coordinate
2.0 effective_lai
22.9 screen_height
clim\rbw_prime_annual annual_climate_prefix
0 number_non_critical_annual_sequences
clim\rbw_prime_monthly monthly_climate_prefix
0 number_non_critical_monthly_sequences
clim\rbw daily_climate_prefix
2
ndep_NO3
ndep_NH4
0
clim\rbw_prime_hourly hourly_climate_prefix
0 number_non_critical_hourly_sequences
</pre>

===Running RHESSys with Gridded Climate Data===

# Edit your template file to refer to the climate base file.
# When running RHESSys, use the command line option '--asciigrid' and RHESSs will properly deal with your gridded climate data.
# There's no step 3.

Climate data

2010-10-13T20:15:54Z

Dgroulx: /* Gridded Climate Data */

==Met Station Based Climate Data==

Climate data in this form is based on having a single file for each meteorological station available. Each base station is represented by
it's own base station file, and separate files for each climate variable as listed in the base station file. At the very least, daily time
series of tmin, tmax, and rain are required.

Climate inputs are linked to particular zones by the climate station ID affiliated with that zone. A single climate station (or base station) will typically serve multiple zones within the landscape. Each base station is described by a base station file.

Example Base Station File:
<pre>
101 base_station_id
100.0 x_coordinate
100.0 y_coordinate
22.9 z_coordinate
2.0 effective_lai
22.9 screen_height
clim\rbw_prime_annual annual_climate_prefix
0 number_non_critical_annual_sequences
clim\rbw_prime_monthly monthly_climate_prefix
0 number_non_critical_monthly_sequences
clim\rbw daily_climate_prefix
2
ndep_NO3
ndep_NH4
0
clim\rbw_prime_hourly hourly_climate_prefix
0 number_non_critical_hourly_sequences
</pre>

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Climate Input Sequence Name / File Extension'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Units'''
|-
| rain||precipitation (rain + snow)* required||meters
|-
| tmin||minimum daily temperature* required||°C
|-
| tmax||maximum daily temperature* required||°C
|-
| dayl||day length||seconds
|-
| daytime_rain_duration||duration of rainfall||hours
|-
| LAI_scalar||zone and seasonal scaling of LAI - only applied to stratum of non-zero height||Unitless
|-
| Ldown||incoming longwave radiation||KJ / (meters2)/day
|-
| Kdown_direct||incoming direct shortwave radiation||KJ / (meters2)/day
|-
| Kdown_diffuse||incoming diffuse shortwave radiation||KJ / (meters2)/day
|-
| ndep_NO3||nitrogen deposition as NO3||kg / (meters2)/day
|-
| ndep_NH4||nitrogen deposition as NH4||kg / (meters2) /day
|-
| PAR_direct||incoming direct PAR radiation||KJ / (meters2)/day
|-
| PAR_diffuse||incoming diffuse PAR radiation||KJ / (meters2)/day
|-
| relative_humidity||Relative Humidity||Range (0-1)
|-
| tday||Mean Daytime Temperature||°C
|-
| tnightmax||Night time temperature at sundown (used for soil heat flux)||°C
|-
| tsoil||Soil temperature||°C
|-
| vpd||Vapour pressure deficit||Pa
|-
| wind||Wind speed||meters/ sec.
|-
| CO2||Carbon Dioxide||parts per million/year
|-
| lapse_rate_tmin || minimum daily temperature lapse rate with elevation || °C/m
|-
| lapse_rate_tmax || maximum daily temperature lapse rate with elevation || °C/m

|}

All possible base station filenames must be listed in the worldfile header, as described in the discussion of grass2world below.

===Format for Time Series Input Files===
The first line of each input time series file must give the start date of the time series. The start date of the input must precede the start date listed in the worldfile. Following the start date, time series values are listed sequentially. For example:
example_simulation_daily.rain will contain the following

<pre>
1986 1 1 1
0.0028
0.000
0.0157
0.000
…
</pre>

==Gridded Climate Data==

Climate data in gridded form is not tied to any particular met station, but is a grid of climate data over the watershed such as an interpolation
between multiple climate stations, or downscaled data from a climate model. While it is possible to fake gridded climate data by representing each grid cell as a unique climate station, using gridded climate files is easier to work with.

Gridded climate data will have only a single base file, and a single file for each climate variable. The base file is identical to that of non-gridded climate data,
except that the first line that set the base station id is replaced with a line specifying the total number of grid cells. So if you had a gridded climate dataset
with 90 cells, the first line of your climate base file would be: 
'''90 grid_cells'''

===Running RHESSys with Gridded Climate Data===

# Edit your template file to refer to the climate base file.
# When running RHESSys, use the command line option '--asciigrid' and RHESSs will properly deal with your gridded climate data.
# There's no step 3.

Climate data

2010-10-13T20:15:42Z

Dgroulx: /* Gridded Climate Data */

==Met Station Based Climate Data==

Climate data in this form is based on having a single file for each meteorological station available. Each base station is represented by
it's own base station file, and separate files for each climate variable as listed in the base station file. At the very least, daily time
series of tmin, tmax, and rain are required.

Climate inputs are linked to particular zones by the climate station ID affiliated with that zone. A single climate station (or base station) will typically serve multiple zones within the landscape. Each base station is described by a base station file.

Example Base Station File:
<pre>
101 base_station_id
100.0 x_coordinate
100.0 y_coordinate
22.9 z_coordinate
2.0 effective_lai
22.9 screen_height
clim\rbw_prime_annual annual_climate_prefix
0 number_non_critical_annual_sequences
clim\rbw_prime_monthly monthly_climate_prefix
0 number_non_critical_monthly_sequences
clim\rbw daily_climate_prefix
2
ndep_NO3
ndep_NH4
0
clim\rbw_prime_hourly hourly_climate_prefix
0 number_non_critical_hourly_sequences
</pre>

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Climate Input Sequence Name / File Extension'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Units'''
|-
| rain||precipitation (rain + snow)* required||meters
|-
| tmin||minimum daily temperature* required||°C
|-
| tmax||maximum daily temperature* required||°C
|-
| dayl||day length||seconds
|-
| daytime_rain_duration||duration of rainfall||hours
|-
| LAI_scalar||zone and seasonal scaling of LAI - only applied to stratum of non-zero height||Unitless
|-
| Ldown||incoming longwave radiation||KJ / (meters2)/day
|-
| Kdown_direct||incoming direct shortwave radiation||KJ / (meters2)/day
|-
| Kdown_diffuse||incoming diffuse shortwave radiation||KJ / (meters2)/day
|-
| ndep_NO3||nitrogen deposition as NO3||kg / (meters2)/day
|-
| ndep_NH4||nitrogen deposition as NH4||kg / (meters2) /day
|-
| PAR_direct||incoming direct PAR radiation||KJ / (meters2)/day
|-
| PAR_diffuse||incoming diffuse PAR radiation||KJ / (meters2)/day
|-
| relative_humidity||Relative Humidity||Range (0-1)
|-
| tday||Mean Daytime Temperature||°C
|-
| tnightmax||Night time temperature at sundown (used for soil heat flux)||°C
|-
| tsoil||Soil temperature||°C
|-
| vpd||Vapour pressure deficit||Pa
|-
| wind||Wind speed||meters/ sec.
|-
| CO2||Carbon Dioxide||parts per million/year
|-
| lapse_rate_tmin || minimum daily temperature lapse rate with elevation || °C/m
|-
| lapse_rate_tmax || maximum daily temperature lapse rate with elevation || °C/m

|}

All possible base station filenames must be listed in the worldfile header, as described in the discussion of grass2world below.

===Format for Time Series Input Files===
The first line of each input time series file must give the start date of the time series. The start date of the input must precede the start date listed in the worldfile. Following the start date, time series values are listed sequentially. For example:
example_simulation_daily.rain will contain the following

<pre>
1986 1 1 1
0.0028
0.000
0.0157
0.000
…
</pre>

==Gridded Climate Data==

Climate data in gridded form is not tied to any particular met station, but is a grid of climate data over the watershed such as an interpolation
between multiple climate stations, or downscaled data from a climate model. While it is possible to fake gridded climate data by representing each grid cell as a unique climate station, using gridded climate files is easier to work with.

Gridded climate data will have only a single base file, and a single file for each climate variable. The base file is identical to that of non-gridded climate data,
except that the first line that set the base station id is replaced with a line specifying the total number of grid cells. So if you had a gridded climate dataset
with 90 cells, the first line of your climate base file would be:
'''90 grid_cells'''

===Running RHESSys with Gridded Climate Data===

# Edit your template file to refer to the climate base file.
# When running RHESSys, use the command line option '--asciigrid' and RHESSs will properly deal with your gridded climate data.
# There's no step 3.

Climate data

2010-10-13T20:15:02Z

Dgroulx: /* Gridded Climate Data */

==Met Station Based Climate Data==

Climate data in this form is based on having a single file for each meteorological station available. Each base station is represented by
it's own base station file, and separate files for each climate variable as listed in the base station file. At the very least, daily time
series of tmin, tmax, and rain are required.

Climate inputs are linked to particular zones by the climate station ID affiliated with that zone. A single climate station (or base station) will typically serve multiple zones within the landscape. Each base station is described by a base station file.

Example Base Station File:
<pre>
101 base_station_id
100.0 x_coordinate
100.0 y_coordinate
22.9 z_coordinate
2.0 effective_lai
22.9 screen_height
clim\rbw_prime_annual annual_climate_prefix
0 number_non_critical_annual_sequences
clim\rbw_prime_monthly monthly_climate_prefix
0 number_non_critical_monthly_sequences
clim\rbw daily_climate_prefix
2
ndep_NO3
ndep_NH4
0
clim\rbw_prime_hourly hourly_climate_prefix
0 number_non_critical_hourly_sequences
</pre>

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Climate Input Sequence Name / File Extension'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Units'''
|-
| rain||precipitation (rain + snow)* required||meters
|-
| tmin||minimum daily temperature* required||°C
|-
| tmax||maximum daily temperature* required||°C
|-
| dayl||day length||seconds
|-
| daytime_rain_duration||duration of rainfall||hours
|-
| LAI_scalar||zone and seasonal scaling of LAI - only applied to stratum of non-zero height||Unitless
|-
| Ldown||incoming longwave radiation||KJ / (meters2)/day
|-
| Kdown_direct||incoming direct shortwave radiation||KJ / (meters2)/day
|-
| Kdown_diffuse||incoming diffuse shortwave radiation||KJ / (meters2)/day
|-
| ndep_NO3||nitrogen deposition as NO3||kg / (meters2)/day
|-
| ndep_NH4||nitrogen deposition as NH4||kg / (meters2) /day
|-
| PAR_direct||incoming direct PAR radiation||KJ / (meters2)/day
|-
| PAR_diffuse||incoming diffuse PAR radiation||KJ / (meters2)/day
|-
| relative_humidity||Relative Humidity||Range (0-1)
|-
| tday||Mean Daytime Temperature||°C
|-
| tnightmax||Night time temperature at sundown (used for soil heat flux)||°C
|-
| tsoil||Soil temperature||°C
|-
| vpd||Vapour pressure deficit||Pa
|-
| wind||Wind speed||meters/ sec.
|-
| CO2||Carbon Dioxide||parts per million/year
|-
| lapse_rate_tmin || minimum daily temperature lapse rate with elevation || °C/m
|-
| lapse_rate_tmax || maximum daily temperature lapse rate with elevation || °C/m

|}

All possible base station filenames must be listed in the worldfile header, as described in the discussion of grass2world below.

===Format for Time Series Input Files===
The first line of each input time series file must give the start date of the time series. The start date of the input must precede the start date listed in the worldfile. Following the start date, time series values are listed sequentially. For example:
example_simulation_daily.rain will contain the following

<pre>
1986 1 1 1
0.0028
0.000
0.0157
0.000
…
</pre>

==Gridded Climate Data==

Climate data in gridded form is not tied to any particular met station, but is a grid of climate data over the watershed such as an interpolation
between multiple climate stations, or downscaled data from a climate model. While it is possible to fake gridded climate data by representing each grid cell as a unique climate station, using gridded climate files is easier to work with.

Gridded climate data will have only a single base file, and a single file for each climate variable. The base file is identical to that of non-gridded climate data,
except that the first line that set the base station id is replaced with a line specifying the total number of grid cells. So if you had a gridded climate dataset
with 90 cells, the first line of your climate base file would be:

90 grid_cells

===Running RHESSys with Gridded Climate Data===

# Edit your template file to refer to the climate base file.
# When running RHESSys, use the command line option '--asciigrid' and RHESSs will properly deal with your gridded climate data.
# There's no step 3.

Climate data

2010-10-13T20:05:18Z

Dgroulx:

Climate data

2010-10-13T20:05:04Z

Dgroulx: /* Format for Time Series Input Files */

===Met Station Based Climate Data===

Climate data in this form is based on having a single file for each meteorological station available. Each base station is represented by
it's own base station file, and separate files for each climate variable as listed in the base station file. At the very least, daily time
series of tmin, tmax, and rain are required.

Climate inputs are linked to particular zones by the climate station ID affiliated with that zone. A single climate station (or base station) will typically serve multiple zones within the landscape. Each base station is described by a base station file.

Example Base Station File:
<pre>
101 base_station_id
100.0 x_coordinate
100.0 y_coordinate
22.9 z_coordinate
2.0 effective_lai
22.9 screen_height
clim\rbw_prime_annual annual_climate_prefix
0 number_non_critical_annual_sequences
clim\rbw_prime_monthly monthly_climate_prefix
0 number_non_critical_monthly_sequences
clim\rbw daily_climate_prefix
2
ndep_NO3
ndep_NH4
0
clim\rbw_prime_hourly hourly_climate_prefix
0 number_non_critical_hourly_sequences
</pre>

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Climate Input Sequence Name / File Extension'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Units'''
|-
| rain||precipitation (rain + snow)* required||meters
|-
| tmin||minimum daily temperature* required||°C
|-
| tmax||maximum daily temperature* required||°C
|-
| dayl||day length||seconds
|-
| daytime_rain_duration||duration of rainfall||hours
|-
| LAI_scalar||zone and seasonal scaling of LAI - only applied to stratum of non-zero height||Unitless
|-
| Ldown||incoming longwave radiation||KJ / (meters2)/day
|-
| Kdown_direct||incoming direct shortwave radiation||KJ / (meters2)/day
|-
| Kdown_diffuse||incoming diffuse shortwave radiation||KJ / (meters2)/day
|-
| ndep_NO3||nitrogen deposition as NO3||kg / (meters2)/day
|-
| ndep_NH4||nitrogen deposition as NH4||kg / (meters2) /day
|-
| PAR_direct||incoming direct PAR radiation||KJ / (meters2)/day
|-
| PAR_diffuse||incoming diffuse PAR radiation||KJ / (meters2)/day
|-
| relative_humidity||Relative Humidity||Range (0-1)
|-
| tday||Mean Daytime Temperature||°C
|-
| tnightmax||Night time temperature at sundown (used for soil heat flux)||°C
|-
| tsoil||Soil temperature||°C
|-
| vpd||Vapour pressure deficit||Pa
|-
| wind||Wind speed||meters/ sec.
|-
| CO2||Carbon Dioxide||parts per million/year
|-
| lapse_rate_tmin || minimum daily temperature lapse rate with elevation || °C/m
|-
| lapse_rate_tmax || maximum daily temperature lapse rate with elevation || °C/m

|}

All possible base station filenames must be listed in the worldfile header, as described in the discussion of grass2world below.

===Format for Time Series Input Files===
The first line of each input time series file must give the start date of the time series. The start date of the input must precede the start date listed in the worldfile. Following the start date, time series values are listed sequentially. For example:
example_simulation_daily.rain will contain the following

<pre>
1986 1 1 1
0.0028
0.000
0.0157
0.000
…
</pre>

==Gridded Climate Data==

Climate data in gridded form is not tied to any particular met station, but is a grid of climate data over the watershed such as an interpolation
between multiple climate stations, or downscaled data from a climate model. While it is possible to fake gridded climate data by representing each grid cell as a unique climate station, using gridded climate files is easier to work with. Gridded climate data will have only a single base file, and a single file for each climate variable.

Climate data

2010-10-13T20:04:31Z

Dgroulx:

===Met Station Based Climate Data===

Climate data in this form is based on having a single file for each meteorological station available. Each base station is represented by
it's own base station file, and separate files for each climate variable as listed in the base station file. At the very least, daily time
series of tmin, tmax, and rain are required.

Climate inputs are linked to particular zones by the climate station ID affiliated with that zone. A single climate station (or base station) will typically serve multiple zones within the landscape. Each base station is described by a base station file.

Example Base Station File:
<pre>
101 base_station_id
100.0 x_coordinate
100.0 y_coordinate
22.9 z_coordinate
2.0 effective_lai
22.9 screen_height
clim\rbw_prime_annual annual_climate_prefix
0 number_non_critical_annual_sequences
clim\rbw_prime_monthly monthly_climate_prefix
0 number_non_critical_monthly_sequences
clim\rbw daily_climate_prefix
2
ndep_NO3
ndep_NH4
0
clim\rbw_prime_hourly hourly_climate_prefix
0 number_non_critical_hourly_sequences
</pre>

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Climate Input Sequence Name / File Extension'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Units'''
|-
| rain||precipitation (rain + snow)* required||meters
|-
| tmin||minimum daily temperature* required||°C
|-
| tmax||maximum daily temperature* required||°C
|-
| dayl||day length||seconds
|-
| daytime_rain_duration||duration of rainfall||hours
|-
| LAI_scalar||zone and seasonal scaling of LAI - only applied to stratum of non-zero height||Unitless
|-
| Ldown||incoming longwave radiation||KJ / (meters2)/day
|-
| Kdown_direct||incoming direct shortwave radiation||KJ / (meters2)/day
|-
| Kdown_diffuse||incoming diffuse shortwave radiation||KJ / (meters2)/day
|-
| ndep_NO3||nitrogen deposition as NO3||kg / (meters2)/day
|-
| ndep_NH4||nitrogen deposition as NH4||kg / (meters2) /day
|-
| PAR_direct||incoming direct PAR radiation||KJ / (meters2)/day
|-
| PAR_diffuse||incoming diffuse PAR radiation||KJ / (meters2)/day
|-
| relative_humidity||Relative Humidity||Range (0-1)
|-
| tday||Mean Daytime Temperature||°C
|-
| tnightmax||Night time temperature at sundown (used for soil heat flux)||°C
|-
| tsoil||Soil temperature||°C
|-
| vpd||Vapour pressure deficit||Pa
|-
| wind||Wind speed||meters/ sec.
|-
| CO2||Carbon Dioxide||parts per million/year
|-
| lapse_rate_tmin || minimum daily temperature lapse rate with elevation || °C/m
|-
| lapse_rate_tmax || maximum daily temperature lapse rate with elevation || °C/m

|}

All possible base station filenames must be listed in the worldfile header, as described in the discussion of grass2world below.

==Format for Time Series Input Files==
The first line of each input time series file must give the start date of the time series. The start date of the input must precede the start date listed in the worldfile. Following the start date, time series values are listed sequentially. For example:
example_simulation_daily.rain will contain the following

<pre>
1986 1 1 1
0.0028
0.000
0.0157
0.000
…
</pre>

===Gridded Climate Data===

Climate data in gridded form is not tied to any particular met station, but is a grid of climate data over the watershed such as an interpolation
between multiple climate stations, or downscaled data from a climate model. While it is possible to fake gridded climate data by representing each grid cell as a unique climate station, using gridded climate files is easier to work with. Gridded climate data will have only a single base file, and a single file for each climate variable.

RHESSys

2010-10-01T23:33:16Z

Dgroulx: /* Data Sources */

== Using RHESSys ==

[[How to get RHESSys]]

[[Directory structure]]

[[Creating Patch Maps]]

== Publications ==
[[Published Literature]]

== RHESSys Tutorial ==

[[Preparing input data sets]]

[[Generating RHESSys input files]]

[[Calibrating and running RHESSys]]

[[Visualizing Spatial Output]]

[[Command Line Options]]

[[Performing a Redefine World]]

==RHESSys File Formats==

[[Climate data]]

[[Default files]]

[[Worldfiles]]

[[Temporal Event Control files]]

[[Flow Table]]

[[Output Files]]

==GRASS GIS==

[[Developing custom GRASS programs]]

==Data Sources==

[http://wiki.icess.ucsb.edu/snow/index.php/STATSGO2-soil_data STATSGO2-soil data]

[[Incorporating LANDSAT data into GRASS]]

[[Climate data scaling with PRISM]]

== Getting started (wiki help) ==
Consult the [http://meta.wikimedia.org/wiki/Help:Contents User's Guide] for information on using the wiki software.
* [http://www.mediawiki.org/wiki/Help:Configuration_settings Configuration settings list]
* [http://www.mediawiki.org/wiki/Help:FAQ MediaWiki FAQ]
* [http://mail.wikimedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]

Preparing input data sets

2010-10-01T23:07:11Z

Dgroulx: /* Create horizon maps */

The GRASS GIS program will be used to process and store your set of spatial data layers associated with a project. The latest GRASS build
can be downloaded at [http://grass.itc.it/ http://grass.itc.it].

==Set the geographic region==

A region refers to a geographic area with some defined boundaries, based on a specific map coordinate system and map projection. In GRASS, each region also has associated with it the specific east-west and north-south resolutions of its smallest units (rectangular units called "cells").

The region's boundaries are given as the northernmost, southernmost, easternmost, and westernmost points that define its extent. The north and south boundaries are commonly called northings, while the east and west boundaries are called eastings.

You need to set the geographic region for your personal mapset. For now, this will be the same as the DEM. Set the region with: 
'''grass> g.region rast=<dem>'''

To find out the settings of the current region: 
'''grass> g.region –p'''

This will tell you the projection, zone, datum, ellipsoid, N/S/E/W coordinates, resolution,
and number of rows and columns of your DEM.

==Start a display monitor and view a map==

To look at the DEM, start a monitor with the GRASS command: 
'''grass> d.mon start=x0'''

This will start a graphics display monitor called x0.
You can have up to 10 monitors open at once (each one must be started with
grass> d.mon start=x_); each must be assigned a different number, i.e. x0, x1, x2, etc...; when you have more than one monitor open, select one for use with the command: 
'''grass> d.mon select=x2'''

To display the raster map layer, type the GRASS command: 
'''grass> d.rast map=hjadem'''

To clear the monitor, type the GRASS command: 
'''grass> d.erase'''

==Defining a watershed boundary==
Rather than working with the full extent of the DEM (which probably contains areas outside of the watershed you are interested in) you can define the boundaries of a landscape that drain to a specific point (or outlet). You will use the GRASS watershed basin creation program (r.water.outlet) to define the boundaries for a sub-watershed within the HJ Andrews basin. First however, r.water.outlet requires a drainage direction map that must be created with the GRASS program r.watershed.

To create the drainage direction map, type the GRASS command: 
'''grass> r.watershed elevation=hjadem drainage=hja_drain'''

This traces the flow through the elevation model and creates a new raster map called drain in your personal mapset.

GRASS recognizes geographic coordinates as the Easting and Northing of each point across the landscape. To define the watershed boundaries associated with a particular outlet, you will need to identify the Easting (E) and Northing (N) of a point on the stream network.
For this exercise, you can experiment with picking any point you choose on the stream network, regardless if it is a gaged stream or not. The purpose of this exercise is simply to acquaint you with how to create a sub-watershed.

Generally, you will want to work with a watershed for which you have some measured information, such as streamflow, soil moisture, or LAI, so you have observed data to compare model results to. This is most often observed streamflow data, which is widely and readily available from many gaged streams. Therefore, you attempt to delineate the modeled watershed to match the real watershed draining to that gage. To identify the outlet point for a gaged stream, it is helpful to overlay a map of stream gages on the stream network if available. To do this, you will need to import the stream and gage maps provided with the tutorial data set into GRASS. At the beginning of this tutorial, you should have copied the ascii files hjagages.asc and hjastreams.asc into your grassdata directory.

==Importing files into grass==

To import ascii raster files into GRASS, direct input to the ascii map, give the resultant map an output name, and set null values to 0 (read working in GRASS and UNIX below): 
'''grass> r.in.ascii input=/full_path_name/hjagages.asc output=hjagages nv=0''' 
'''grass> r.in.ascii input=/full_path_name/hjastreams.asc output=hjastreams nv=0'''

(GRASS supports many formats. For information on importing different formats, i.e. ARC-ASCII-GRID with r.in.arc, ESRI/E00 with m.in.e00, see the GRASS data import help webpage).

Display the maps, overlaying the gages on the streams, with: 
'''grass> d.rast map=hjastreams''' 
'''grass> d.rast -o map=hjagages'''

A map of the stream network overlain by the stream gages should be displayed in your monitor. Note the gages are very small points across the watershed and can be hard to see without zooming in, which will be discussed shortly.

This map illustrates gage locations throughout the HJA.

Identify an outlet point
To identify location information on either the stream or gage maps, type the GRASS command 
'''grass> d.what.rast'''

Move the cursor over the display; use the left mouse button to click on a gage point. The E and N and map category value of the point you clicked will be displayed on your terminal window. Right click to end the session.

If you are having trouble placing your mouse right on top of a gage point, it may be helpful to zoom in with the GRASS command
'''grass> d.zoom'''

Follow the on screen instructions using the mouse to zoom in on a gage or group of gages. Then use '''grass> d.what.rast''' to query the points.

NOTE: You want to find the E and N coordinates for an outlet that falls on the stream network in order to delineate the boundary of all area draining to that point. However, the gages may not fall exactly on the stream network, so you may need to adjust where you choose your E and N coordinates so the point you choose falls on the stream network as close to the gage as possible.
d.zoom resets the region to the area you are zoomed in on. Any additional functions
you perform after zooming in would only process the area you are zoomed in on. As you
may be zoomed in very tightly on a stream segment and the full area of the watershed
you want to capture may not be displayed, you should reset your region with: 
'''grass> g.region rast=hjadem'''

To redisplay the map at the full extent of the hjadem region, you could use: 
'''grass> d.redraw'''

Or to clear your monitor, use: 
'''grass> d.erase'''

==Create a watershed==
Once you have the location of an outlet (the E and N coordinates), you can generate the sub-basin from the drainage direction map created with r.watershed and the E and N coordinates you isolated with r.what.rast. 

'''G> r.water.outlet drainage=drain basin=new_basin_name easting=xxx northing=xxx'''

This will generate a watershed basin map (new_basin_name) from the drainage direction
map (drain) and put it in your personal mapset. This map will have a value of 1 everywhere inside the boundary, and a value of 0 everywhere that falls outside of new_basin_name (ie. the rest of the DEM).

Display this map: 
'''G> d.rast map=new_basin_name'''

NOTE: Remember, the set of coordinates you use represents the outlet point of the
watershed, and the watershed basin is all area upstream of that point that drains to that point. Therefore, if the point you choose is on a hill slope, the resulting map will only reflect the small sliver of land uphill that drains to that point. This may take several tries, so don't get frustrated!

Using the overlay option with a new map generated from an existing map 
When you create a new map that represents a portion of the extent of an
existing map, you may need to run the GRASS command r.support in order to set all null
values to transparent. For example, you would use r.support if you wanted to overlay
new_basin_name on top of the DEM so that all areas outside of the new sub- basin were
transparent, allowing the DEM underneath to show through. You may find the GRASS
command r.support helpful as you create new maps. r.support can only be run interactively.
To use it for the purpose of setting null values to transparent, accept the default (no) for
the first six questions, but answer yes to the last question ‘Do you want to delete null file
for map_name?’ Answer yes.

==Preparing spatial input data sets==
You have a DEM (hjadem) and have now created a basin (new_basin_name) map. However, RHESSys requires additional spatial data to form a complete landscape representation and establish connectivity between spatial units. One of the unique features of RHESSys is its hierarchical landscape representation. RHESSys partitions the landscape into a hierarchical spatial structure, where each level of the spatial hierarchy fully covers the spatial extent of the landscape. For example, stratum (vegetation) are processed within each patch, patches are contained within hillslopes and zones, which are units contained within the full basin. Each level of the hierarchy is defined as a particular object type with a set of storage (state) and flux variables, and an associated set of model parameters (default files).

Object type and associated processes:
* Basin - defines the drainage basin, full extent of location being modeled.
* Hillslope - defines areas which drain to a single point or stream reach.
* Zone - denotes areas of similar climate.
* Patch - soil moisture processes and carbon and nitrogen cycling.
* Stratum - vertical layers within a patch (ie. vegetation)

From the DEM you'll need to derive the following maps:
* Slope
* Aspect
* Basin
* Hillslope
* Patch
* Saturated soil hydraulic conductivity at the surface (Ksat0)
* Decay of hydraulic conductivity with depth (m)
*Stream network
*Roads

===Create horizon maps===

RHESSys expects horizon values as sin(horizon angle). You will need to compute two horizon maps, one
for east, and one for west. In GRASS, you would do this with the commands

'''g> r.horizon -d elevin=<DEM> direction=0 horizon=east''' 
'''g> r.horizon -d elevin=<DEM> direction=180 horizon=west'''

This will produce two maps, east_0, and west_0. These maps are
the horizon in degrees though, so you will need to use mapcalc to create new maps with the sin of these
values.

'''g> r.mapcalc 'east_horizon = sin(east_0)' ''' 
'''g> r.mapcalc 'west_horizon = sin(west_0)' '''

These two maps will be referenced by your template file.

===Create slope and aspect maps===
To generate slope and aspect layers for the new_basin_name map from the DEM, give the
the input elevation map (el), and output names for both the slope and aspect maps.
For this exercise use the following: 
'''grass> r.slope.aspect el=hjadem slope=slope aspect=aspect'''

This will create 2 new maps in your personal mapset, slope and aspect. You can name
these maps whatever you want, but by convention, they are generally called slope and
aspect. As you created these for the full DEM, you may want to use demslope, etc….
If you were still zoomed in and did not reset your region to the full extent of the DEM
then you may want to give your slope and aspect maps an identifying extension.

Verify the maps are there with: 
'''grass> g.list type=rast mapset=your_userID'''
will list maps only in your personal mapset directory.

===Create hillslope and stream maps===
You will use a GRASS watershed basin analysis program to generate a set of maps used to delineate key spatial layers in RHESSys. RHESSys uses different spatial objects to model specific hydro-ecological processes. These objects form a hierarchical representation of the landscapes key objects. The hillslope and stream maps are necessary as they represent key landscape objects. The GRASS r.watershed program creates maps of watershed basins, hillslopes, flow accumulation, drainage direction, and stream segments within a DEM. You only want to create these maps for the new_basin_name portion of the DEM.

For this step, zoom in on the new_basin_name map fairly close, however, leave at
least one pixel width of space around the watershed. As d.zoom resets the region, it
allows you to work with only the portion of the map displayed as you create additional maps in this step. 
'''grass> d.zoom'''

Hillslopes are defined as land area draining either side of a stream reach in each sub-basin. Hillslopes are created by breaking up the watershed into sub basins associated with a particular stream reach. To generate a hillslope map and a stream map, you will use the r.watershed program (r.watershed was used to create the hjastreams map you viewed previously). This program can be run interactively or non-interactively. To run non-interactively (command line): 
'''grass> r.watershed el=hjadem t=100 ac=acc dr=drain ba=b100 ha=h100 stream=str100'''

The proceeding was an abbreviation of: 
'''grass> r.watershed elevation=hjadem threshold=100 accumulation=acc drainage=drain basin=b100 half.basin=h100 stream=str100'''

Where threshold sets the aggregation value, elevation is the input map, and the rest are output maps.

This will put several new maps in your PERMANENT mapset (you can check with g.list). You can name the output maps whatever you choose, this is simply the convention established by previous RHESSys users (h100 indicates hillslopes at a threshold of 100 cells, etc...). Threshold represents the minimum size of a sub-basin in cells, or overland flow units. Try experimenting with different threshold values (i.e. try additional thresholds at 50 and 200), then display the hillslope maps (in different monitors) to see the difference.

===Setting a mask===
In order to work with data that falls only inside of this new sub-basin area rather than working with the full extent of the DEM or region you currently have set (i.e. as a result of zooming), you must set a mask. Setting a mask 'ignores' those areas that fall outside of the designated mask area on all subsequent operations, blocking them from analysis. This program can only be run interactively.

Type the GRASS command: 
'''grass> r.mask'''

Choose option 2 'Identify a new mask'

You will be prompted to enter the name of a raster map layer 
'''grass> new_basin_name'''

You will be shown a listing of this map's categories, and asked to assign a value of "1" or "0" to each map category. Areas assigned category value "1" will become part of the mask's surface, while areas assigned category value "0" will become "no data" areas in the MASK file.

Hit enter to move your cursor to the second category and type 1 in the space (type 1 next to all non-zero categories), hit <Esc><Enter> as instructed at the bottom of the page. You will be returned to the option page where you will see listed at the top of the screen that the current mask is new_basin_name, enter to return to the GRASS prompt.

Now if you display the DEM you will only see the area of the DEM that falls inside the new_basin_name basin area. 
'''grass> d.rast map=hjadem'''

Now reset the region to the geographic boundaries of new_basin_name with the g.region zoom option (sets the current region settings to the smallest region encompassing all non-zero data in the named raster map layer):
'''grass> g.region raster=new_basin_name zoom=new_basin_name''' 
'''grass> d.redraw'''

You should now have a much closer view of the DEM for new_basin_name.

===Zones===

Zones denote areas of similar climate. Zones store climate variables such as radiation, temperature etc... Each zone is linked to an input climate station. Precipitation and temperature data, for example, from this station are modified based on zone elevation, slope and aspect relative to the climate station. Zone processing also generates climate data not available from climate station (i.e. zones will estimate radiation fluxes if they are not available). Numerous strategies exist to partition areas of similar climate. Elevation bands in a mountainous area, for example, are likely to denote similarity. Distribution of climate stations can also be used to define zone partitioning, where each zone defines the area associated with a particular climate station. For these exercises, you will not be creating a zone map, as meteorological data from 1 climate station is sufficient for this small watershed. In this instance, it
is best to use the same map for zones as you use for hillslopes.

===Ksat0, m, and roads===
You will now use the GRASS raster map layer data calculator to create additional maps required to run RHESSys. The maps you will create in this exercise are the basic maps required to run RHESSys. However, this GRASS command can also be used to perform many arithmetic functions involving one or several existing map layers to create new map layers. See the GRASS website for a list of arithmetic operators.

The GRASS command r.mapcalc is typed in the form: 
'''grass> r.mapcalc 'result = expression' '''

where result is the name of the new map you are creating and expression is the arithmetic
being performed. Use r.mapcalc to generate three additional maps needed by RHESSys. The m and Ksat0 maps define spatial patterns of two soil hydrologic parameters. For this exercise we will assume these parameters do not vary spatially and use the same value for the entire watershed.

Type the following GRASS commands to create maps for Ksat0, m, and roads: (the ' are deliberate characters) 
'''grass> r.mapcalc 'K = new_basin_name * 2' ''' 
'''grass> r.mapcalc 'm = new_basin_name * 0.12' ''' 
'''grass> r.mapcalc 'zero = 0' ''' (zero will be used as the road map as there are no roads in this watershed)

When you created new_basin_name, it was assigned a value of 1. The multiplication operator (*) was used to create a new map called K (Ksat0-saturated soil hydraulic conductivity at the surface) that covers the extent of this sub-basin, which will have a value of 2, and a new map called m (decay of hydraulic conductivity with depth) with a value of 0.12. You also created a road map equal to zero to indicate that there are no roads in this dataset. K and m should be initialized based on values for the soil type in your area of study (see website for soil type values).

===Patches===
The final map required for a basic RHESSys run is the patch map. Patches represent the smallest resolution spatial unit and define areas of similar soil moisture and land cover characteristics. Vertical soil moisture processing and soil biogeochemistry are modeled within each unit defined as a patch. Lateral transport of material and water occurs between patches, so patch definition must reflect drainage organization of the watershed. You have considerable flexibility in defining a patch structure; patches can be strictly grid-based (i.e. based on 30m DEM), or of arbitrary shape (reflecting the patterns of relevant variability within the landscape, i.e. wetness index, vegetation cover, and stream/road networks).

However, when defining a patch structure attention should be given to the landscape size due to the associated processing time. Most of the processing in RHESSYS – for patch and stratum processes – is done at the patch spatial level. These processes must be performed for each individual patch. Therefore, the more patches there are, the more processing that must be done. Choosing a smaller resolution spatial unit will increase the number of patches, therefore, increase total processing time for a simulation.

For this exercise, you will define the patch structure for new_map_name based on the 30 meter DEM. The GRASS command r.clump re-categorizes data in a raster map layer by grouping cells that form physically discrete areas into unique categories. 
'''grass> r.clump input=hjadem output=new_map_name.cl'''

By user defined convention, when a map is clumped the extension .cl is added to the map name to identify that the r.clump function has be done.

To look at the patch structure: 
'''grass> d.rast map=new_map_name.cl'''

===Stratum===

Strata define vertical, aspatial layers within the patch. Processes such as photosynthesis and transpiration are modeled at the stratum level. Strata usually have the same spatial structure as patches. So the patch (new_map_name.cl) map will also be used to define the stratum object.

You have now created all the maps necessary for RHESSys to define the landscape representation. For now, however, you can quit out of GRASS (G> quit) and work on the additional timeseries data sets required to run RHESSys.

===Carbon Stores===

==Developing timeseries data sets==
Climate
RHESSys requires daily climate inputs for precipitation, minimum and maximum air temperature. These climate inputs are linked to zones in the landscape representation by a base station ID affiliated with that zone. A single base station will typically serve multiple (or all) zones within the landscape. Each base station is described by a base station file and stored in the clim directory.

The tutorial data set included a base station file (w8_base) and 3 climate files (w8_daily.rain, w8_daily.tmin, w8_daily.tmax) for a small watershed (w8) in the HJA that you should have copied into your clim directory. Have a look at the base station file structure.

From the UNIX prompt: 
'''unix> more w8_base'''

Take note of the following content:

Line 1: 101 base_station_id.
This ID will be read by zones in the landscape to link it to the base station climate file.

Line 4: 485 z_coordinate.
Elevation (in meters) of meterological station where climate data was collected.

Line 11: ../clim/w8_daily daily_climate_prefix.
Tells the base station what daily precipitation and temperature files to read, and the directory they are in.

NOTE: if you were developing your own climate input files, you would edit this base station file to reflect your meteorological station elevation and daily climate prefix.

Each of the climate input files (precipitation, maximum temperature and minimum temperature) is contained in a separate file. RHESSys assumes that the climate input files associated with a base station are all named with the same prefix (i.e. w8_daily = daily climate inputs for w8). A filename extension specifying the kind of climate variable (ie. precipitation, maximum or minimum temperature) contained in each file is attached to the end of the prefix. The prefix is then given in the base station description file, directing it to read in all climate files with that prefix.

There are 3 required climate input files - precipitaiton, minimum and maximum daily temperature. (There are also a number of optional climate inputs. If optional climate sequences are not available/used, a process model within RHESSys will provide estimates of these variables. See the RHESSys website for more information.) RHESSys requires the climate files to be in a particular format:

Review the structure of these climate input files. The first line of each input time series file must give the starting date of the time series (Year Month Day Hour). Following the starting date, daily time series values are listed sequentially.

'''unix> more w8_daily.rain''' (daily precipitation in meters)
These are long files, to end viewing a file, type U> q.
'''unix> more w8_daily.tmax''' (daily maximum temperature °C)
'''unix> more w8_daily.tmin''' (daily minimum temperature °C)

Developing your own daily climate files may require some preprocessing in order to format the data so it can be read by RHESSys. Be sure to check for missing data and make sure data is in the correct units. The RHESSys website describes a process for dealing with missing data and formatting it for RHESSys. It is also a good idea to inspect a graph of your input time series data visually to check for abnormal spikes or unrealistic values such as negative precipitation events. You may need to use a statistical computation program such as R, S-Plus, SPSS, or Excel to fill in missing data.

A climate data file should only consist of the start date at the top, followed by 1 value for each day. When naming the files you can use any name you want for the beginning of the prefix (just make sure all three have the same prefix). However, by convention, the prefix should include the time period of the data (i.e. daily, to distinguish these from hourly time series inputs, an optional input type in RHESSys) followed by the extensions: .rain, .tmin, .tmax

NOTE: Depending on the program you use to save your data files, it may attach an additional file extension to the end of the file (such as .txt). When you bring the files into your UNIX clim directory, make sure to remove any file extensions.
Also, if you develop the files on a PC and transfer them to UNIX, you may need to run the converter dos2unix to convert from DOS text format to UNIX format - which will remove the ^M characters from the file. If you open one of the files with vi, you can see if the characters are present.

==Streamflow==
You will need observed streamflow data for calibration. As with climate, when creating your own streamflow files some preprocessing may be necessary to check for missing or abnormal data, and for formatting. When used in the calibration procedure (discussed in Module III) format for streamflow files is the same as for climate files. The Observed streamflow has been provided for w8 (obs.wy79_80dw8) for the exercises you will do in the next module.

RHESSys outputs streamflow in millimeters per day (streamflow normalized by basin area), so the observed streamflow must also be converted to millimeters per day. (RHESSys also aggregates output at a monthly timestep in the event you only have observed monthly streamflow.)

For example, the USGS uses cubic-feet per second (CFS) as their unit of measurement, so you would need to convert from CFS to mm/day. To convert from mean daily CFS to mm per day, you need to know the area of the watershed draining to the gage you have streamflow (Q) data for in square feet.

(If necessary, to convert area in hectares (ha) to square feet (sq.ft.), multiply ha by 107639.104169.)

To convert mean CFS to mm per day:

1. divide mean CFS by the basin area in sq.ft = Q ft/sec

2. multiply Q ft/sec by 86400 = Q ft/day

3. multiply Q ft/day by 304.8 = Q mm/day

Preparing input data sets

2010-10-01T23:03:34Z

Dgroulx: /* Preparing spatial input data sets */

The GRASS GIS program will be used to process and store your set of spatial data layers associated with a project. The latest GRASS build
can be downloaded at [http://grass.itc.it/ http://grass.itc.it].

==Set the geographic region==

A region refers to a geographic area with some defined boundaries, based on a specific map coordinate system and map projection. In GRASS, each region also has associated with it the specific east-west and north-south resolutions of its smallest units (rectangular units called "cells").

The region's boundaries are given as the northernmost, southernmost, easternmost, and westernmost points that define its extent. The north and south boundaries are commonly called northings, while the east and west boundaries are called eastings.

You need to set the geographic region for your personal mapset. For now, this will be the same as the DEM. Set the region with: 
'''grass> g.region rast=<dem>'''

To find out the settings of the current region: 
'''grass> g.region –p'''

This will tell you the projection, zone, datum, ellipsoid, N/S/E/W coordinates, resolution,
and number of rows and columns of your DEM.

==Start a display monitor and view a map==

To look at the DEM, start a monitor with the GRASS command: 
'''grass> d.mon start=x0'''

This will start a graphics display monitor called x0.
You can have up to 10 monitors open at once (each one must be started with
grass> d.mon start=x_); each must be assigned a different number, i.e. x0, x1, x2, etc...; when you have more than one monitor open, select one for use with the command: 
'''grass> d.mon select=x2'''

To display the raster map layer, type the GRASS command: 
'''grass> d.rast map=hjadem'''

To clear the monitor, type the GRASS command: 
'''grass> d.erase'''

==Defining a watershed boundary==
Rather than working with the full extent of the DEM (which probably contains areas outside of the watershed you are interested in) you can define the boundaries of a landscape that drain to a specific point (or outlet). You will use the GRASS watershed basin creation program (r.water.outlet) to define the boundaries for a sub-watershed within the HJ Andrews basin. First however, r.water.outlet requires a drainage direction map that must be created with the GRASS program r.watershed.

To create the drainage direction map, type the GRASS command: 
'''grass> r.watershed elevation=hjadem drainage=hja_drain'''

This traces the flow through the elevation model and creates a new raster map called drain in your personal mapset.

GRASS recognizes geographic coordinates as the Easting and Northing of each point across the landscape. To define the watershed boundaries associated with a particular outlet, you will need to identify the Easting (E) and Northing (N) of a point on the stream network.
For this exercise, you can experiment with picking any point you choose on the stream network, regardless if it is a gaged stream or not. The purpose of this exercise is simply to acquaint you with how to create a sub-watershed.

Generally, you will want to work with a watershed for which you have some measured information, such as streamflow, soil moisture, or LAI, so you have observed data to compare model results to. This is most often observed streamflow data, which is widely and readily available from many gaged streams. Therefore, you attempt to delineate the modeled watershed to match the real watershed draining to that gage. To identify the outlet point for a gaged stream, it is helpful to overlay a map of stream gages on the stream network if available. To do this, you will need to import the stream and gage maps provided with the tutorial data set into GRASS. At the beginning of this tutorial, you should have copied the ascii files hjagages.asc and hjastreams.asc into your grassdata directory.

==Importing files into grass==

To import ascii raster files into GRASS, direct input to the ascii map, give the resultant map an output name, and set null values to 0 (read working in GRASS and UNIX below): 
'''grass> r.in.ascii input=/full_path_name/hjagages.asc output=hjagages nv=0''' 
'''grass> r.in.ascii input=/full_path_name/hjastreams.asc output=hjastreams nv=0'''

(GRASS supports many formats. For information on importing different formats, i.e. ARC-ASCII-GRID with r.in.arc, ESRI/E00 with m.in.e00, see the GRASS data import help webpage).

Display the maps, overlaying the gages on the streams, with: 
'''grass> d.rast map=hjastreams''' 
'''grass> d.rast -o map=hjagages'''

A map of the stream network overlain by the stream gages should be displayed in your monitor. Note the gages are very small points across the watershed and can be hard to see without zooming in, which will be discussed shortly.

This map illustrates gage locations throughout the HJA.

Identify an outlet point
To identify location information on either the stream or gage maps, type the GRASS command 
'''grass> d.what.rast'''

Move the cursor over the display; use the left mouse button to click on a gage point. The E and N and map category value of the point you clicked will be displayed on your terminal window. Right click to end the session.

If you are having trouble placing your mouse right on top of a gage point, it may be helpful to zoom in with the GRASS command
'''grass> d.zoom'''

Follow the on screen instructions using the mouse to zoom in on a gage or group of gages. Then use '''grass> d.what.rast''' to query the points.

NOTE: You want to find the E and N coordinates for an outlet that falls on the stream network in order to delineate the boundary of all area draining to that point. However, the gages may not fall exactly on the stream network, so you may need to adjust where you choose your E and N coordinates so the point you choose falls on the stream network as close to the gage as possible.
d.zoom resets the region to the area you are zoomed in on. Any additional functions
you perform after zooming in would only process the area you are zoomed in on. As you
may be zoomed in very tightly on a stream segment and the full area of the watershed
you want to capture may not be displayed, you should reset your region with: 
'''grass> g.region rast=hjadem'''

To redisplay the map at the full extent of the hjadem region, you could use: 
'''grass> d.redraw'''

Or to clear your monitor, use: 
'''grass> d.erase'''

==Create a watershed==
Once you have the location of an outlet (the E and N coordinates), you can generate the sub-basin from the drainage direction map created with r.watershed and the E and N coordinates you isolated with r.what.rast. 

'''G> r.water.outlet drainage=drain basin=new_basin_name easting=xxx northing=xxx'''

This will generate a watershed basin map (new_basin_name) from the drainage direction
map (drain) and put it in your personal mapset. This map will have a value of 1 everywhere inside the boundary, and a value of 0 everywhere that falls outside of new_basin_name (ie. the rest of the DEM).

Display this map: 
'''G> d.rast map=new_basin_name'''

NOTE: Remember, the set of coordinates you use represents the outlet point of the
watershed, and the watershed basin is all area upstream of that point that drains to that point. Therefore, if the point you choose is on a hill slope, the resulting map will only reflect the small sliver of land uphill that drains to that point. This may take several tries, so don't get frustrated!

Using the overlay option with a new map generated from an existing map 
When you create a new map that represents a portion of the extent of an
existing map, you may need to run the GRASS command r.support in order to set all null
values to transparent. For example, you would use r.support if you wanted to overlay
new_basin_name on top of the DEM so that all areas outside of the new sub- basin were
transparent, allowing the DEM underneath to show through. You may find the GRASS
command r.support helpful as you create new maps. r.support can only be run interactively.
To use it for the purpose of setting null values to transparent, accept the default (no) for
the first six questions, but answer yes to the last question ‘Do you want to delete null file
for map_name?’ Answer yes.

==Preparing spatial input data sets==
You have a DEM (hjadem) and have now created a basin (new_basin_name) map. However, RHESSys requires additional spatial data to form a complete landscape representation and establish connectivity between spatial units. One of the unique features of RHESSys is its hierarchical landscape representation. RHESSys partitions the landscape into a hierarchical spatial structure, where each level of the spatial hierarchy fully covers the spatial extent of the landscape. For example, stratum (vegetation) are processed within each patch, patches are contained within hillslopes and zones, which are units contained within the full basin. Each level of the hierarchy is defined as a particular object type with a set of storage (state) and flux variables, and an associated set of model parameters (default files).

Object type and associated processes:
* Basin - defines the drainage basin, full extent of location being modeled.
* Hillslope - defines areas which drain to a single point or stream reach.
* Zone - denotes areas of similar climate.
* Patch - soil moisture processes and carbon and nitrogen cycling.
* Stratum - vertical layers within a patch (ie. vegetation)

From the DEM you'll need to derive the following maps:
* Slope
* Aspect
* Basin
* Hillslope
* Patch
* Saturated soil hydraulic conductivity at the surface (Ksat0)
* Decay of hydraulic conductivity with depth (m)
*Stream network
*Roads

===Create horizon maps===

RHESSys expects horizon values as sin(horizon angle). You will need to compute two horizon maps, one
for east, and one for west. In GRASS, you would do this with the commands

'''g> r.horizon -d elevin=<DEM> direction=0 horizon=horizon''' 
'''g> r.horizon -d elevin=<DEM> direction=180 horizon=horizon'''

This will produce two maps, horizon_0, and horizon_180, where 0 is east and 180 is west. These maps are
the horizon in degrees though, so you will need to use mapcalc to create new maps with the sin of these
values.

'''g> r.mapcalc 'east_horizon = sin(horizon_0)' ''' 
'''g> r.mapcalc 'west_horizon = sin(horizon_180)' '''

These two maps will be referenced by your template file.

===Create slope and aspect maps===
To generate slope and aspect layers for the new_basin_name map from the DEM, give the
the input elevation map (el), and output names for both the slope and aspect maps.
For this exercise use the following: 
'''grass> r.slope.aspect el=hjadem slope=slope aspect=aspect'''

This will create 2 new maps in your personal mapset, slope and aspect. You can name
these maps whatever you want, but by convention, they are generally called slope and
aspect. As you created these for the full DEM, you may want to use demslope, etc….
If you were still zoomed in and did not reset your region to the full extent of the DEM
then you may want to give your slope and aspect maps an identifying extension.

Verify the maps are there with: 
'''grass> g.list type=rast mapset=your_userID'''
will list maps only in your personal mapset directory.

===Create hillslope and stream maps===
You will use a GRASS watershed basin analysis program to generate a set of maps used to delineate key spatial layers in RHESSys. RHESSys uses different spatial objects to model specific hydro-ecological processes. These objects form a hierarchical representation of the landscapes key objects. The hillslope and stream maps are necessary as they represent key landscape objects. The GRASS r.watershed program creates maps of watershed basins, hillslopes, flow accumulation, drainage direction, and stream segments within a DEM. You only want to create these maps for the new_basin_name portion of the DEM.

For this step, zoom in on the new_basin_name map fairly close, however, leave at
least one pixel width of space around the watershed. As d.zoom resets the region, it
allows you to work with only the portion of the map displayed as you create additional maps in this step. 
'''grass> d.zoom'''

Hillslopes are defined as land area draining either side of a stream reach in each sub-basin. Hillslopes are created by breaking up the watershed into sub basins associated with a particular stream reach. To generate a hillslope map and a stream map, you will use the r.watershed program (r.watershed was used to create the hjastreams map you viewed previously). This program can be run interactively or non-interactively. To run non-interactively (command line): 
'''grass> r.watershed el=hjadem t=100 ac=acc dr=drain ba=b100 ha=h100 stream=str100'''

The proceeding was an abbreviation of: 
'''grass> r.watershed elevation=hjadem threshold=100 accumulation=acc drainage=drain basin=b100 half.basin=h100 stream=str100'''

Where threshold sets the aggregation value, elevation is the input map, and the rest are output maps.

This will put several new maps in your PERMANENT mapset (you can check with g.list). You can name the output maps whatever you choose, this is simply the convention established by previous RHESSys users (h100 indicates hillslopes at a threshold of 100 cells, etc...). Threshold represents the minimum size of a sub-basin in cells, or overland flow units. Try experimenting with different threshold values (i.e. try additional thresholds at 50 and 200), then display the hillslope maps (in different monitors) to see the difference.

===Setting a mask===
In order to work with data that falls only inside of this new sub-basin area rather than working with the full extent of the DEM or region you currently have set (i.e. as a result of zooming), you must set a mask. Setting a mask 'ignores' those areas that fall outside of the designated mask area on all subsequent operations, blocking them from analysis. This program can only be run interactively.

Type the GRASS command: 
'''grass> r.mask'''

Choose option 2 'Identify a new mask'

You will be prompted to enter the name of a raster map layer 
'''grass> new_basin_name'''

You will be shown a listing of this map's categories, and asked to assign a value of "1" or "0" to each map category. Areas assigned category value "1" will become part of the mask's surface, while areas assigned category value "0" will become "no data" areas in the MASK file.

Hit enter to move your cursor to the second category and type 1 in the space (type 1 next to all non-zero categories), hit <Esc><Enter> as instructed at the bottom of the page. You will be returned to the option page where you will see listed at the top of the screen that the current mask is new_basin_name, enter to return to the GRASS prompt.

Now if you display the DEM you will only see the area of the DEM that falls inside the new_basin_name basin area. 
'''grass> d.rast map=hjadem'''

Now reset the region to the geographic boundaries of new_basin_name with the g.region zoom option (sets the current region settings to the smallest region encompassing all non-zero data in the named raster map layer):
'''grass> g.region raster=new_basin_name zoom=new_basin_name''' 
'''grass> d.redraw'''

You should now have a much closer view of the DEM for new_basin_name.

===Zones===

Zones denote areas of similar climate. Zones store climate variables such as radiation, temperature etc... Each zone is linked to an input climate station. Precipitation and temperature data, for example, from this station are modified based on zone elevation, slope and aspect relative to the climate station. Zone processing also generates climate data not available from climate station (i.e. zones will estimate radiation fluxes if they are not available). Numerous strategies exist to partition areas of similar climate. Elevation bands in a mountainous area, for example, are likely to denote similarity. Distribution of climate stations can also be used to define zone partitioning, where each zone defines the area associated with a particular climate station. For these exercises, you will not be creating a zone map, as meteorological data from 1 climate station is sufficient for this small watershed. In this instance, it
is best to use the same map for zones as you use for hillslopes.

===Ksat0, m, and roads===
You will now use the GRASS raster map layer data calculator to create additional maps required to run RHESSys. The maps you will create in this exercise are the basic maps required to run RHESSys. However, this GRASS command can also be used to perform many arithmetic functions involving one or several existing map layers to create new map layers. See the GRASS website for a list of arithmetic operators.

The GRASS command r.mapcalc is typed in the form: 
'''grass> r.mapcalc 'result = expression' '''

where result is the name of the new map you are creating and expression is the arithmetic
being performed. Use r.mapcalc to generate three additional maps needed by RHESSys. The m and Ksat0 maps define spatial patterns of two soil hydrologic parameters. For this exercise we will assume these parameters do not vary spatially and use the same value for the entire watershed.

Type the following GRASS commands to create maps for Ksat0, m, and roads: (the ' are deliberate characters) 
'''grass> r.mapcalc 'K = new_basin_name * 2' ''' 
'''grass> r.mapcalc 'm = new_basin_name * 0.12' ''' 
'''grass> r.mapcalc 'zero = 0' ''' (zero will be used as the road map as there are no roads in this watershed)

When you created new_basin_name, it was assigned a value of 1. The multiplication operator (*) was used to create a new map called K (Ksat0-saturated soil hydraulic conductivity at the surface) that covers the extent of this sub-basin, which will have a value of 2, and a new map called m (decay of hydraulic conductivity with depth) with a value of 0.12. You also created a road map equal to zero to indicate that there are no roads in this dataset. K and m should be initialized based on values for the soil type in your area of study (see website for soil type values).

===Patches===
The final map required for a basic RHESSys run is the patch map. Patches represent the smallest resolution spatial unit and define areas of similar soil moisture and land cover characteristics. Vertical soil moisture processing and soil biogeochemistry are modeled within each unit defined as a patch. Lateral transport of material and water occurs between patches, so patch definition must reflect drainage organization of the watershed. You have considerable flexibility in defining a patch structure; patches can be strictly grid-based (i.e. based on 30m DEM), or of arbitrary shape (reflecting the patterns of relevant variability within the landscape, i.e. wetness index, vegetation cover, and stream/road networks).

However, when defining a patch structure attention should be given to the landscape size due to the associated processing time. Most of the processing in RHESSYS – for patch and stratum processes – is done at the patch spatial level. These processes must be performed for each individual patch. Therefore, the more patches there are, the more processing that must be done. Choosing a smaller resolution spatial unit will increase the number of patches, therefore, increase total processing time for a simulation.

For this exercise, you will define the patch structure for new_map_name based on the 30 meter DEM. The GRASS command r.clump re-categorizes data in a raster map layer by grouping cells that form physically discrete areas into unique categories. 
'''grass> r.clump input=hjadem output=new_map_name.cl'''

By user defined convention, when a map is clumped the extension .cl is added to the map name to identify that the r.clump function has be done.

To look at the patch structure: 
'''grass> d.rast map=new_map_name.cl'''

===Stratum===

Strata define vertical, aspatial layers within the patch. Processes such as photosynthesis and transpiration are modeled at the stratum level. Strata usually have the same spatial structure as patches. So the patch (new_map_name.cl) map will also be used to define the stratum object.

You have now created all the maps necessary for RHESSys to define the landscape representation. For now, however, you can quit out of GRASS (G> quit) and work on the additional timeseries data sets required to run RHESSys.

===Carbon Stores===

==Developing timeseries data sets==
Climate
RHESSys requires daily climate inputs for precipitation, minimum and maximum air temperature. These climate inputs are linked to zones in the landscape representation by a base station ID affiliated with that zone. A single base station will typically serve multiple (or all) zones within the landscape. Each base station is described by a base station file and stored in the clim directory.

The tutorial data set included a base station file (w8_base) and 3 climate files (w8_daily.rain, w8_daily.tmin, w8_daily.tmax) for a small watershed (w8) in the HJA that you should have copied into your clim directory. Have a look at the base station file structure.

From the UNIX prompt: 
'''unix> more w8_base'''

Take note of the following content:

Line 1: 101 base_station_id.
This ID will be read by zones in the landscape to link it to the base station climate file.

Line 4: 485 z_coordinate.
Elevation (in meters) of meterological station where climate data was collected.

Line 11: ../clim/w8_daily daily_climate_prefix.
Tells the base station what daily precipitation and temperature files to read, and the directory they are in.

NOTE: if you were developing your own climate input files, you would edit this base station file to reflect your meteorological station elevation and daily climate prefix.

Each of the climate input files (precipitation, maximum temperature and minimum temperature) is contained in a separate file. RHESSys assumes that the climate input files associated with a base station are all named with the same prefix (i.e. w8_daily = daily climate inputs for w8). A filename extension specifying the kind of climate variable (ie. precipitation, maximum or minimum temperature) contained in each file is attached to the end of the prefix. The prefix is then given in the base station description file, directing it to read in all climate files with that prefix.

There are 3 required climate input files - precipitaiton, minimum and maximum daily temperature. (There are also a number of optional climate inputs. If optional climate sequences are not available/used, a process model within RHESSys will provide estimates of these variables. See the RHESSys website for more information.) RHESSys requires the climate files to be in a particular format:

Review the structure of these climate input files. The first line of each input time series file must give the starting date of the time series (Year Month Day Hour). Following the starting date, daily time series values are listed sequentially.

'''unix> more w8_daily.rain''' (daily precipitation in meters)
These are long files, to end viewing a file, type U> q.
'''unix> more w8_daily.tmax''' (daily maximum temperature °C)
'''unix> more w8_daily.tmin''' (daily minimum temperature °C)

Developing your own daily climate files may require some preprocessing in order to format the data so it can be read by RHESSys. Be sure to check for missing data and make sure data is in the correct units. The RHESSys website describes a process for dealing with missing data and formatting it for RHESSys. It is also a good idea to inspect a graph of your input time series data visually to check for abnormal spikes or unrealistic values such as negative precipitation events. You may need to use a statistical computation program such as R, S-Plus, SPSS, or Excel to fill in missing data.

A climate data file should only consist of the start date at the top, followed by 1 value for each day. When naming the files you can use any name you want for the beginning of the prefix (just make sure all three have the same prefix). However, by convention, the prefix should include the time period of the data (i.e. daily, to distinguish these from hourly time series inputs, an optional input type in RHESSys) followed by the extensions: .rain, .tmin, .tmax

NOTE: Depending on the program you use to save your data files, it may attach an additional file extension to the end of the file (such as .txt). When you bring the files into your UNIX clim directory, make sure to remove any file extensions.
Also, if you develop the files on a PC and transfer them to UNIX, you may need to run the converter dos2unix to convert from DOS text format to UNIX format - which will remove the ^M characters from the file. If you open one of the files with vi, you can see if the characters are present.

==Streamflow==
You will need observed streamflow data for calibration. As with climate, when creating your own streamflow files some preprocessing may be necessary to check for missing or abnormal data, and for formatting. When used in the calibration procedure (discussed in Module III) format for streamflow files is the same as for climate files. The Observed streamflow has been provided for w8 (obs.wy79_80dw8) for the exercises you will do in the next module.

RHESSys outputs streamflow in millimeters per day (streamflow normalized by basin area), so the observed streamflow must also be converted to millimeters per day. (RHESSys also aggregates output at a monthly timestep in the event you only have observed monthly streamflow.)

For example, the USGS uses cubic-feet per second (CFS) as their unit of measurement, so you would need to convert from CFS to mm/day. To convert from mean daily CFS to mm per day, you need to know the area of the watershed draining to the gage you have streamflow (Q) data for in square feet.

(If necessary, to convert area in hectares (ha) to square feet (sq.ft.), multiply ha by 107639.104169.)

To convert mean CFS to mm per day:

1. divide mean CFS by the basin area in sq.ft = Q ft/sec

2. multiply Q ft/sec by 86400 = Q ft/day

3. multiply Q ft/day by 304.8 = Q mm/day

Ksat vertical

2010-10-01T19:31:31Z

Dgroulx: Created page with 'If this value is set to 0, then Ksat will be pulled from the soil def file for that patch.'

If this value is set to 0, then Ksat will be pulled from the soil def
file for that patch.

Preparing input data sets

2010-09-28T23:49:39Z

Dgroulx: /* Creating horizon maps */

The GRASS GIS program will be used to process and store your set of spatial data layers associated with a project. The latest GRASS build
can be downloaded at [http://grass.itc.it/ http://grass.itc.it].

==Set the geographic region==

A region refers to a geographic area with some defined boundaries, based on a specific map coordinate system and map projection. In GRASS, each region also has associated with it the specific east-west and north-south resolutions of its smallest units (rectangular units called "cells").

The region's boundaries are given as the northernmost, southernmost, easternmost, and westernmost points that define its extent. The north and south boundaries are commonly called northings, while the east and west boundaries are called eastings.

You need to set the geographic region for your personal mapset. For now, this will be the same as the DEM. Set the region with: 
'''grass> g.region rast=<dem>'''

To find out the settings of the current region: 
'''grass> g.region –p'''

This will tell you the projection, zone, datum, ellipsoid, N/S/E/W coordinates, resolution,
and number of rows and columns of your DEM.

==Start a display monitor and view a map==

To look at the DEM, start a monitor with the GRASS command: 
'''grass> d.mon start=x0'''

This will start a graphics display monitor called x0.
You can have up to 10 monitors open at once (each one must be started with
grass> d.mon start=x_); each must be assigned a different number, i.e. x0, x1, x2, etc...; when you have more than one monitor open, select one for use with the command: 
'''grass> d.mon select=x2'''

To display the raster map layer, type the GRASS command: 
'''grass> d.rast map=hjadem'''

To clear the monitor, type the GRASS command: 
'''grass> d.erase'''

==Defining a watershed boundary==
Rather than working with the full extent of the DEM (which probably contains areas outside of the watershed you are interested in) you can define the boundaries of a landscape that drain to a specific point (or outlet). You will use the GRASS watershed basin creation program (r.water.outlet) to define the boundaries for a sub-watershed within the HJ Andrews basin. First however, r.water.outlet requires a drainage direction map that must be created with the GRASS program r.watershed.

To create the drainage direction map, type the GRASS command: 
'''grass> r.watershed elevation=hjadem drainage=hja_drain'''

This traces the flow through the elevation model and creates a new raster map called drain in your personal mapset.

GRASS recognizes geographic coordinates as the Easting and Northing of each point across the landscape. To define the watershed boundaries associated with a particular outlet, you will need to identify the Easting (E) and Northing (N) of a point on the stream network.
For this exercise, you can experiment with picking any point you choose on the stream network, regardless if it is a gaged stream or not. The purpose of this exercise is simply to acquaint you with how to create a sub-watershed.

Generally, you will want to work with a watershed for which you have some measured information, such as streamflow, soil moisture, or LAI, so you have observed data to compare model results to. This is most often observed streamflow data, which is widely and readily available from many gaged streams. Therefore, you attempt to delineate the modeled watershed to match the real watershed draining to that gage. To identify the outlet point for a gaged stream, it is helpful to overlay a map of stream gages on the stream network if available. To do this, you will need to import the stream and gage maps provided with the tutorial data set into GRASS. At the beginning of this tutorial, you should have copied the ascii files hjagages.asc and hjastreams.asc into your grassdata directory.

==Importing files into grass==

To import ascii raster files into GRASS, direct input to the ascii map, give the resultant map an output name, and set null values to 0 (read working in GRASS and UNIX below): 
'''grass> r.in.ascii input=/full_path_name/hjagages.asc output=hjagages nv=0''' 
'''grass> r.in.ascii input=/full_path_name/hjastreams.asc output=hjastreams nv=0'''

(GRASS supports many formats. For information on importing different formats, i.e. ARC-ASCII-GRID with r.in.arc, ESRI/E00 with m.in.e00, see the GRASS data import help webpage).

Display the maps, overlaying the gages on the streams, with: 
'''grass> d.rast map=hjastreams''' 
'''grass> d.rast -o map=hjagages'''

A map of the stream network overlain by the stream gages should be displayed in your monitor. Note the gages are very small points across the watershed and can be hard to see without zooming in, which will be discussed shortly.

This map illustrates gage locations throughout the HJA.

Identify an outlet point
To identify location information on either the stream or gage maps, type the GRASS command 
'''grass> d.what.rast'''

Move the cursor over the display; use the left mouse button to click on a gage point. The E and N and map category value of the point you clicked will be displayed on your terminal window. Right click to end the session.

If you are having trouble placing your mouse right on top of a gage point, it may be helpful to zoom in with the GRASS command
'''grass> d.zoom'''

Follow the on screen instructions using the mouse to zoom in on a gage or group of gages. Then use '''grass> d.what.rast''' to query the points.

NOTE: You want to find the E and N coordinates for an outlet that falls on the stream network in order to delineate the boundary of all area draining to that point. However, the gages may not fall exactly on the stream network, so you may need to adjust where you choose your E and N coordinates so the point you choose falls on the stream network as close to the gage as possible.
d.zoom resets the region to the area you are zoomed in on. Any additional functions
you perform after zooming in would only process the area you are zoomed in on. As you
may be zoomed in very tightly on a stream segment and the full area of the watershed
you want to capture may not be displayed, you should reset your region with: 
'''grass> g.region rast=hjadem'''

To redisplay the map at the full extent of the hjadem region, you could use: 
'''grass> d.redraw'''

Or to clear your monitor, use: 
'''grass> d.erase'''

==Create a watershed==
Once you have the location of an outlet (the E and N coordinates), you can generate the sub-basin from the drainage direction map created with r.watershed and the E and N coordinates you isolated with r.what.rast. 

'''G> r.water.outlet drainage=drain basin=new_basin_name easting=xxx northing=xxx'''

This will generate a watershed basin map (new_basin_name) from the drainage direction
map (drain) and put it in your personal mapset. This map will have a value of 1 everywhere inside the boundary, and a value of 0 everywhere that falls outside of new_basin_name (ie. the rest of the DEM).

Display this map: 
'''G> d.rast map=new_basin_name'''

NOTE: Remember, the set of coordinates you use represents the outlet point of the
watershed, and the watershed basin is all area upstream of that point that drains to that point. Therefore, if the point you choose is on a hill slope, the resulting map will only reflect the small sliver of land uphill that drains to that point. This may take several tries, so don't get frustrated!

Using the overlay option with a new map generated from an existing map 
When you create a new map that represents a portion of the extent of an
existing map, you may need to run the GRASS command r.support in order to set all null
values to transparent. For example, you would use r.support if you wanted to overlay
new_basin_name on top of the DEM so that all areas outside of the new sub- basin were
transparent, allowing the DEM underneath to show through. You may find the GRASS
command r.support helpful as you create new maps. r.support can only be run interactively.
To use it for the purpose of setting null values to transparent, accept the default (no) for
the first six questions, but answer yes to the last question ‘Do you want to delete null file
for map_name?’ Answer yes.

==Preparing spatial input data sets==
You have a DEM (hjadem) and have now created a basin (new_basin_name) map. However, RHESSys requires additional spatial data to form a complete landscape representation and establish connectivity between spatial units. One of the unique features of RHESSys is its hierarchical landscape representation. RHESSys partitions the landscape into a hierarchical spatial structure, where each level of the spatial hierarchy fully covers the spatial extent of the landscape. For example, stratum (vegetation) are processed within each patch, patches are contained within hillslopes and zones, which are units contained within the full basin. Each level of the hierarchy is defined as a particular object type with a set of storage (state) and flux variables, and an associated set of model parameters (default files).

Object type and associated processes:
* Basin - defines the drainage basin, full extent of location being modeled.
* Hillslope - defines areas which drain to a single point or stream reach.
* Zone - denotes areas of similar climate.
* Patch - soil moisture processes and carbon and nitrogen cycling.
* Stratum - vertical layers within a patch (ie. vegetation)

From the DEM you'll need to derive the following maps:
* Slope
* Aspect
* Basin
* Hillslope
* Patch
* Saturated soil hydraulic conductivity at the surface (Ksat0)
* Decay of hydraulic conductivity with depth (m)
*Stream network
*Roads

===Creating horizon maps===

RHESSys expects horizon values as sin(horizon angle). You will need to compute two horizon maps, one
for east, and one for west. In GRASS, you would do this with the commands

'''g> r.horizon -d elevin=<DEM> direction=0 horizon=horizon''' 
'''g> r.horizon -d elevin=<DEM> direction=180 horizon=horizon'''

This will produce two maps, horizon_0, and horizon_180, where 0 is east and 180 is west. These maps are
the horizon in degrees though, so you will need to use mapcalc to create new maps with the sin of these
values.

'''g> r.mapcalc 'east_horizon = sin(horizon_0)' ''' 
'''g> r.mapcalc 'west_horizon = sin(horizon_180)' '''

These two maps will be referenced by your template file.

===Create slope and aspect maps===
To generate slope and aspect layers for the new_basin_name map from the DEM, give the
the input elevation map (el), and output names for both the slope and aspect maps.
For this exercise use the following: 
'''grass> r.slope.aspect el=hjadem slope=slope aspect=aspect'''

This will create 2 new maps in your personal mapset, slope and aspect. You can name
these maps whatever you want, but by convention, they are generally called slope and
aspect. As you created these for the full DEM, you may want to use demslope, etc….
If you were still zoomed in and did not reset your region to the full extent of the DEM
then you may want to give your slope and aspect maps an identifying extension.

Verify the maps are there with: 
'''grass> g.list type=rast mapset=your_userID'''
will list maps only in your personal mapset directory.

===Create hillslope and stream maps===
You will use a GRASS watershed basin analysis program to generate a set of maps used to delineate key spatial layers in RHESSys. RHESSys uses different spatial objects to model specific hydro-ecological processes. These objects form a hierarchical representation of the landscapes key objects. The hillslope and stream maps are necessary as they represent key landscape objects. The GRASS r.watershed program creates maps of watershed basins, hillslopes, flow accumulation, drainage direction, and stream segments within a DEM. You only want to create these maps for the new_basin_name portion of the DEM.

For this step, zoom in on the new_basin_name map fairly close, however, leave at
least one pixel width of space around the watershed. As d.zoom resets the region, it
allows you to work with only the portion of the map displayed as you create additional maps in this step. 
'''grass> d.zoom'''

Hillslopes are defined as land area draining either side of a stream reach in each sub-basin. Hillslopes are created by breaking up the watershed into sub basins associated with a particular stream reach. To generate a hillslope map and a stream map, you will use the r.watershed program (r.watershed was used to create the hjastreams map you viewed previously). This program can be run interactively or non-interactively. To run non-interactively (command line): 
'''grass> r.watershed el=hjadem t=100 ac=acc dr=drain ba=b100 ha=h100 stream=str100'''

The proceeding was an abbreviation of: 
'''grass> r.watershed elevation=hjadem threshold=100 accumulation=acc drainage=drain basin=b100 half.basin=h100 stream=str100'''

Where threshold sets the aggregation value, elevation is the input map, and the rest are output maps.

This will put several new maps in your PERMANENT mapset (you can check with g.list). You can name the output maps whatever you choose, this is simply the convention established by previous RHESSys users (h100 indicates hillslopes at a threshold of 100 cells, etc...). Threshold represents the minimum size of a sub-basin in cells, or overland flow units. Try experimenting with different threshold values (i.e. try additional thresholds at 50 and 200), then display the hillslope maps (in different monitors) to see the difference.

===Setting a mask===
In order to work with data that falls only inside of this new sub-basin area rather than working with the full extent of the DEM or region you currently have set (i.e. as a result of zooming), you must set a mask. Setting a mask 'ignores' those areas that fall outside of the designated mask area on all subsequent operations, blocking them from analysis. This program can only be run interactively.

Type the GRASS command: 
'''grass> r.mask'''

Choose option 2 'Identify a new mask'

You will be prompted to enter the name of a raster map layer 
'''grass> new_basin_name'''

You will be shown a listing of this map's categories, and asked to assign a value of "1" or "0" to each map category. Areas assigned category value "1" will become part of the mask's surface, while areas assigned category value "0" will become "no data" areas in the MASK file.

Hit enter to move your cursor to the second category and type 1 in the space (type 1 next to all non-zero categories), hit <Esc><Enter> as instructed at the bottom of the page. You will be returned to the option page where you will see listed at the top of the screen that the current mask is new_basin_name, enter to return to the GRASS prompt.

Now if you display the DEM you will only see the area of the DEM that falls inside the new_basin_name basin area. 
'''grass> d.rast map=hjadem'''

Now reset the region to the geographic boundaries of new_basin_name with the g.region zoom option (sets the current region settings to the smallest region encompassing all non-zero data in the named raster map layer):
'''grass> g.region raster=new_basin_name zoom=new_basin_name''' 
'''grass> d.redraw'''

You should now have a much closer view of the DEM for new_basin_name.

===Zones===

Zones denote areas of similar climate. Zones store climate variables such as radiation, temperature etc... Each zone is linked to an input climate station. Precipitation and temperature data, for example, from this station are modified based on zone elevation, slope and aspect relative to the climate station. Zone processing also generates climate data not available from climate station (i.e. zones will estimate radiation fluxes if they are not available). Numerous strategies exist to partition areas of similar climate. Elevation bands in a mountainous area, for example, are likely to denote similarity. Distribution of climate stations can also be used to define zone partitioning, where each zone defines the area associated with a particular climate station. For these exercises, you will not be creating a zone map, as meteorological data from 1 climate station is sufficient for this small watershed. In this instance, it
is best to use the same map for zones as you use for hillslopes.

===Ksat0, m, and roads===
You will now use the GRASS raster map layer data calculator to create additional maps required to run RHESSys. The maps you will create in this exercise are the basic maps required to run RHESSys. However, this GRASS command can also be used to perform many arithmetic functions involving one or several existing map layers to create new map layers. See the GRASS website for a list of arithmetic operators.

The GRASS command r.mapcalc is typed in the form: 
'''grass> r.mapcalc 'result = expression' '''

where result is the name of the new map you are creating and expression is the arithmetic
being performed. Use r.mapcalc to generate three additional maps needed by RHESSys. The m and Ksat0 maps define spatial patterns of two soil hydrologic parameters. For this exercise we will assume these parameters do not vary spatially and use the same value for the entire watershed.

Type the following GRASS commands to create maps for Ksat0, m, and roads: (the ' are deliberate characters) 
'''grass> r.mapcalc 'K = new_basin_name * 2' ''' 
'''grass> r.mapcalc 'm = new_basin_name * 0.12' ''' 
'''grass> r.mapcalc 'zero = 0' ''' (zero will be used as the road map as there are no roads in this watershed)

When you created new_basin_name, it was assigned a value of 1. The multiplication operator (*) was used to create a new map called K (Ksat0-saturated soil hydraulic conductivity at the surface) that covers the extent of this sub-basin, which will have a value of 2, and a new map called m (decay of hydraulic conductivity with depth) with a value of 0.12. You also created a road map equal to zero to indicate that there are no roads in this dataset. K and m should be initialized based on values for the soil type in your area of study (see website for soil type values).

===Patches===
The final map required for a basic RHESSys run is the patch map. Patches represent the smallest resolution spatial unit and define areas of similar soil moisture and land cover characteristics. Vertical soil moisture processing and soil biogeochemistry are modeled within each unit defined as a patch. Lateral transport of material and water occurs between patches, so patch definition must reflect drainage organization of the watershed. You have considerable flexibility in defining a patch structure; patches can be strictly grid-based (i.e. based on 30m DEM), or of arbitrary shape (reflecting the patterns of relevant variability within the landscape, i.e. wetness index, vegetation cover, and stream/road networks).

However, when defining a patch structure attention should be given to the landscape size due to the associated processing time. Most of the processing in RHESSYS – for patch and stratum processes – is done at the patch spatial level. These processes must be performed for each individual patch. Therefore, the more patches there are, the more processing that must be done. Choosing a smaller resolution spatial unit will increase the number of patches, therefore, increase total processing time for a simulation.

For this exercise, you will define the patch structure for new_map_name based on the 30 meter DEM. The GRASS command r.clump re-categorizes data in a raster map layer by grouping cells that form physically discrete areas into unique categories. 
'''grass> r.clump input=hjadem output=new_map_name.cl'''

By user defined convention, when a map is clumped the extension .cl is added to the map name to identify that the r.clump function has be done.

To look at the patch structure: 
'''grass> d.rast map=new_map_name.cl'''

===Stratum===

Strata define vertical, aspatial layers within the patch. Processes such as photosynthesis and transpiration are modeled at the stratum level. Strata usually have the same spatial structure as patches. So the patch (new_map_name.cl) map will also be used to define the stratum object.

You have now created all the maps necessary for RHESSys to define the landscape representation. For now, however, you can quit out of GRASS (G> quit) and work on the additional timeseries data sets required to run RHESSys.

===Carbon Stores===

==Developing timeseries data sets==
Climate
RHESSys requires daily climate inputs for precipitation, minimum and maximum air temperature. These climate inputs are linked to zones in the landscape representation by a base station ID affiliated with that zone. A single base station will typically serve multiple (or all) zones within the landscape. Each base station is described by a base station file and stored in the clim directory.

The tutorial data set included a base station file (w8_base) and 3 climate files (w8_daily.rain, w8_daily.tmin, w8_daily.tmax) for a small watershed (w8) in the HJA that you should have copied into your clim directory. Have a look at the base station file structure.

From the UNIX prompt: 
'''unix> more w8_base'''

Take note of the following content:

Line 1: 101 base_station_id.
This ID will be read by zones in the landscape to link it to the base station climate file.

Line 4: 485 z_coordinate.
Elevation (in meters) of meterological station where climate data was collected.

Line 11: ../clim/w8_daily daily_climate_prefix.
Tells the base station what daily precipitation and temperature files to read, and the directory they are in.

NOTE: if you were developing your own climate input files, you would edit this base station file to reflect your meteorological station elevation and daily climate prefix.

Each of the climate input files (precipitation, maximum temperature and minimum temperature) is contained in a separate file. RHESSys assumes that the climate input files associated with a base station are all named with the same prefix (i.e. w8_daily = daily climate inputs for w8). A filename extension specifying the kind of climate variable (ie. precipitation, maximum or minimum temperature) contained in each file is attached to the end of the prefix. The prefix is then given in the base station description file, directing it to read in all climate files with that prefix.

There are 3 required climate input files - precipitaiton, minimum and maximum daily temperature. (There are also a number of optional climate inputs. If optional climate sequences are not available/used, a process model within RHESSys will provide estimates of these variables. See the RHESSys website for more information.) RHESSys requires the climate files to be in a particular format:

Review the structure of these climate input files. The first line of each input time series file must give the starting date of the time series (Year Month Day Hour). Following the starting date, daily time series values are listed sequentially.

'''unix> more w8_daily.rain''' (daily precipitation in meters)
These are long files, to end viewing a file, type U> q.
'''unix> more w8_daily.tmax''' (daily maximum temperature °C)
'''unix> more w8_daily.tmin''' (daily minimum temperature °C)

Developing your own daily climate files may require some preprocessing in order to format the data so it can be read by RHESSys. Be sure to check for missing data and make sure data is in the correct units. The RHESSys website describes a process for dealing with missing data and formatting it for RHESSys. It is also a good idea to inspect a graph of your input time series data visually to check for abnormal spikes or unrealistic values such as negative precipitation events. You may need to use a statistical computation program such as R, S-Plus, SPSS, or Excel to fill in missing data.

A climate data file should only consist of the start date at the top, followed by 1 value for each day. When naming the files you can use any name you want for the beginning of the prefix (just make sure all three have the same prefix). However, by convention, the prefix should include the time period of the data (i.e. daily, to distinguish these from hourly time series inputs, an optional input type in RHESSys) followed by the extensions: .rain, .tmin, .tmax

NOTE: Depending on the program you use to save your data files, it may attach an additional file extension to the end of the file (such as .txt). When you bring the files into your UNIX clim directory, make sure to remove any file extensions.
Also, if you develop the files on a PC and transfer them to UNIX, you may need to run the converter dos2unix to convert from DOS text format to UNIX format - which will remove the ^M characters from the file. If you open one of the files with vi, you can see if the characters are present.

==Streamflow==
You will need observed streamflow data for calibration. As with climate, when creating your own streamflow files some preprocessing may be necessary to check for missing or abnormal data, and for formatting. When used in the calibration procedure (discussed in Module III) format for streamflow files is the same as for climate files. The Observed streamflow has been provided for w8 (obs.wy79_80dw8) for the exercises you will do in the next module.

RHESSys outputs streamflow in millimeters per day (streamflow normalized by basin area), so the observed streamflow must also be converted to millimeters per day. (RHESSys also aggregates output at a monthly timestep in the event you only have observed monthly streamflow.)

For example, the USGS uses cubic-feet per second (CFS) as their unit of measurement, so you would need to convert from CFS to mm/day. To convert from mean daily CFS to mm per day, you need to know the area of the watershed draining to the gage you have streamflow (Q) data for in square feet.

(If necessary, to convert area in hectares (ha) to square feet (sq.ft.), multiply ha by 107639.104169.)

To convert mean CFS to mm per day:

1. divide mean CFS by the basin area in sq.ft = Q ft/sec

2. multiply Q ft/sec by 86400 = Q ft/day

3. multiply Q ft/day by 304.8 = Q mm/day

Preparing input data sets

2010-09-28T23:49:18Z

Dgroulx: /* Importing files into grass */

The GRASS GIS program will be used to process and store your set of spatial data layers associated with a project. The latest GRASS build
can be downloaded at [http://grass.itc.it/ http://grass.itc.it].

==Set the geographic region==

A region refers to a geographic area with some defined boundaries, based on a specific map coordinate system and map projection. In GRASS, each region also has associated with it the specific east-west and north-south resolutions of its smallest units (rectangular units called "cells").

The region's boundaries are given as the northernmost, southernmost, easternmost, and westernmost points that define its extent. The north and south boundaries are commonly called northings, while the east and west boundaries are called eastings.

You need to set the geographic region for your personal mapset. For now, this will be the same as the DEM. Set the region with: 
'''grass> g.region rast=<dem>'''

To find out the settings of the current region: 
'''grass> g.region –p'''

This will tell you the projection, zone, datum, ellipsoid, N/S/E/W coordinates, resolution,
and number of rows and columns of your DEM.

==Start a display monitor and view a map==

To look at the DEM, start a monitor with the GRASS command: 
'''grass> d.mon start=x0'''

This will start a graphics display monitor called x0.
You can have up to 10 monitors open at once (each one must be started with
grass> d.mon start=x_); each must be assigned a different number, i.e. x0, x1, x2, etc...; when you have more than one monitor open, select one for use with the command: 
'''grass> d.mon select=x2'''

To display the raster map layer, type the GRASS command: 
'''grass> d.rast map=hjadem'''

To clear the monitor, type the GRASS command: 
'''grass> d.erase'''

==Defining a watershed boundary==
Rather than working with the full extent of the DEM (which probably contains areas outside of the watershed you are interested in) you can define the boundaries of a landscape that drain to a specific point (or outlet). You will use the GRASS watershed basin creation program (r.water.outlet) to define the boundaries for a sub-watershed within the HJ Andrews basin. First however, r.water.outlet requires a drainage direction map that must be created with the GRASS program r.watershed.

To create the drainage direction map, type the GRASS command: 
'''grass> r.watershed elevation=hjadem drainage=hja_drain'''

This traces the flow through the elevation model and creates a new raster map called drain in your personal mapset.

GRASS recognizes geographic coordinates as the Easting and Northing of each point across the landscape. To define the watershed boundaries associated with a particular outlet, you will need to identify the Easting (E) and Northing (N) of a point on the stream network.
For this exercise, you can experiment with picking any point you choose on the stream network, regardless if it is a gaged stream or not. The purpose of this exercise is simply to acquaint you with how to create a sub-watershed.

Generally, you will want to work with a watershed for which you have some measured information, such as streamflow, soil moisture, or LAI, so you have observed data to compare model results to. This is most often observed streamflow data, which is widely and readily available from many gaged streams. Therefore, you attempt to delineate the modeled watershed to match the real watershed draining to that gage. To identify the outlet point for a gaged stream, it is helpful to overlay a map of stream gages on the stream network if available. To do this, you will need to import the stream and gage maps provided with the tutorial data set into GRASS. At the beginning of this tutorial, you should have copied the ascii files hjagages.asc and hjastreams.asc into your grassdata directory.

==Importing files into grass==

To import ascii raster files into GRASS, direct input to the ascii map, give the resultant map an output name, and set null values to 0 (read working in GRASS and UNIX below): 
'''grass> r.in.ascii input=/full_path_name/hjagages.asc output=hjagages nv=0''' 
'''grass> r.in.ascii input=/full_path_name/hjastreams.asc output=hjastreams nv=0'''

(GRASS supports many formats. For information on importing different formats, i.e. ARC-ASCII-GRID with r.in.arc, ESRI/E00 with m.in.e00, see the GRASS data import help webpage).

Display the maps, overlaying the gages on the streams, with: 
'''grass> d.rast map=hjastreams''' 
'''grass> d.rast -o map=hjagages'''

A map of the stream network overlain by the stream gages should be displayed in your monitor. Note the gages are very small points across the watershed and can be hard to see without zooming in, which will be discussed shortly.

This map illustrates gage locations throughout the HJA.

Identify an outlet point
To identify location information on either the stream or gage maps, type the GRASS command 
'''grass> d.what.rast'''

Move the cursor over the display; use the left mouse button to click on a gage point. The E and N and map category value of the point you clicked will be displayed on your terminal window. Right click to end the session.

If you are having trouble placing your mouse right on top of a gage point, it may be helpful to zoom in with the GRASS command
'''grass> d.zoom'''

Follow the on screen instructions using the mouse to zoom in on a gage or group of gages. Then use '''grass> d.what.rast''' to query the points.

NOTE: You want to find the E and N coordinates for an outlet that falls on the stream network in order to delineate the boundary of all area draining to that point. However, the gages may not fall exactly on the stream network, so you may need to adjust where you choose your E and N coordinates so the point you choose falls on the stream network as close to the gage as possible.
d.zoom resets the region to the area you are zoomed in on. Any additional functions
you perform after zooming in would only process the area you are zoomed in on. As you
may be zoomed in very tightly on a stream segment and the full area of the watershed
you want to capture may not be displayed, you should reset your region with: 
'''grass> g.region rast=hjadem'''

To redisplay the map at the full extent of the hjadem region, you could use: 
'''grass> d.redraw'''

Or to clear your monitor, use: 
'''grass> d.erase'''

==Create a watershed==
Once you have the location of an outlet (the E and N coordinates), you can generate the sub-basin from the drainage direction map created with r.watershed and the E and N coordinates you isolated with r.what.rast. 

'''G> r.water.outlet drainage=drain basin=new_basin_name easting=xxx northing=xxx'''

This will generate a watershed basin map (new_basin_name) from the drainage direction
map (drain) and put it in your personal mapset. This map will have a value of 1 everywhere inside the boundary, and a value of 0 everywhere that falls outside of new_basin_name (ie. the rest of the DEM).

Display this map: 
'''G> d.rast map=new_basin_name'''

NOTE: Remember, the set of coordinates you use represents the outlet point of the
watershed, and the watershed basin is all area upstream of that point that drains to that point. Therefore, if the point you choose is on a hill slope, the resulting map will only reflect the small sliver of land uphill that drains to that point. This may take several tries, so don't get frustrated!

Using the overlay option with a new map generated from an existing map 
When you create a new map that represents a portion of the extent of an
existing map, you may need to run the GRASS command r.support in order to set all null
values to transparent. For example, you would use r.support if you wanted to overlay
new_basin_name on top of the DEM so that all areas outside of the new sub- basin were
transparent, allowing the DEM underneath to show through. You may find the GRASS
command r.support helpful as you create new maps. r.support can only be run interactively.
To use it for the purpose of setting null values to transparent, accept the default (no) for
the first six questions, but answer yes to the last question ‘Do you want to delete null file
for map_name?’ Answer yes.

==Preparing spatial input data sets==
You have a DEM (hjadem) and have now created a basin (new_basin_name) map. However, RHESSys requires additional spatial data to form a complete landscape representation and establish connectivity between spatial units. One of the unique features of RHESSys is its hierarchical landscape representation. RHESSys partitions the landscape into a hierarchical spatial structure, where each level of the spatial hierarchy fully covers the spatial extent of the landscape. For example, stratum (vegetation) are processed within each patch, patches are contained within hillslopes and zones, which are units contained within the full basin. Each level of the hierarchy is defined as a particular object type with a set of storage (state) and flux variables, and an associated set of model parameters (default files).

Object type and associated processes:
* Basin - defines the drainage basin, full extent of location being modeled.
* Hillslope - defines areas which drain to a single point or stream reach.
* Zone - denotes areas of similar climate.
* Patch - soil moisture processes and carbon and nitrogen cycling.
* Stratum - vertical layers within a patch (ie. vegetation)

From the DEM you'll need to derive the following maps:
* Slope
* Aspect
* Basin
* Hillslope
* Patch
* Saturated soil hydraulic conductivity at the surface (Ksat0)
* Decay of hydraulic conductivity with depth (m)
*Stream network
*Roads

===Creating horizon maps===

RHESSys expects horizon values as sin(horizon angle). You will need to compute two horizon maps, one
for east, and one for west. In GRASS, you would do this with the commands

'''g> r.horizon -d elevin=<DEM> direction=0 horizon=horizon'''

'''g> r.horizon -d elevin=<DEM> direction=180 horizon=horizon'''

This will produce two maps, horizon_0, and horizon_180, where 0 is east and 180 is west. These maps are
the horizon in degrees though, so you will need to use mapcalc to create new maps with the sin of these
values.

'''g> r.mapcalc 'east_horizon = sin(horizon_0)' '''

'''g> r.mapcalc 'west_horizon = sin(horizon_180)' '''

These two maps will be referenced by your template file.

===Create slope and aspect maps===
To generate slope and aspect layers for the new_basin_name map from the DEM, give the
the input elevation map (el), and output names for both the slope and aspect maps.
For this exercise use the following: 
'''grass> r.slope.aspect el=hjadem slope=slope aspect=aspect'''

This will create 2 new maps in your personal mapset, slope and aspect. You can name
these maps whatever you want, but by convention, they are generally called slope and
aspect. As you created these for the full DEM, you may want to use demslope, etc….
If you were still zoomed in and did not reset your region to the full extent of the DEM
then you may want to give your slope and aspect maps an identifying extension.

Verify the maps are there with: 
'''grass> g.list type=rast mapset=your_userID'''
will list maps only in your personal mapset directory.

===Create hillslope and stream maps===
You will use a GRASS watershed basin analysis program to generate a set of maps used to delineate key spatial layers in RHESSys. RHESSys uses different spatial objects to model specific hydro-ecological processes. These objects form a hierarchical representation of the landscapes key objects. The hillslope and stream maps are necessary as they represent key landscape objects. The GRASS r.watershed program creates maps of watershed basins, hillslopes, flow accumulation, drainage direction, and stream segments within a DEM. You only want to create these maps for the new_basin_name portion of the DEM.

For this step, zoom in on the new_basin_name map fairly close, however, leave at
least one pixel width of space around the watershed. As d.zoom resets the region, it
allows you to work with only the portion of the map displayed as you create additional maps in this step. 
'''grass> d.zoom'''

Hillslopes are defined as land area draining either side of a stream reach in each sub-basin. Hillslopes are created by breaking up the watershed into sub basins associated with a particular stream reach. To generate a hillslope map and a stream map, you will use the r.watershed program (r.watershed was used to create the hjastreams map you viewed previously). This program can be run interactively or non-interactively. To run non-interactively (command line): 
'''grass> r.watershed el=hjadem t=100 ac=acc dr=drain ba=b100 ha=h100 stream=str100'''

The proceeding was an abbreviation of: 
'''grass> r.watershed elevation=hjadem threshold=100 accumulation=acc drainage=drain basin=b100 half.basin=h100 stream=str100'''

Where threshold sets the aggregation value, elevation is the input map, and the rest are output maps.

This will put several new maps in your PERMANENT mapset (you can check with g.list). You can name the output maps whatever you choose, this is simply the convention established by previous RHESSys users (h100 indicates hillslopes at a threshold of 100 cells, etc...). Threshold represents the minimum size of a sub-basin in cells, or overland flow units. Try experimenting with different threshold values (i.e. try additional thresholds at 50 and 200), then display the hillslope maps (in different monitors) to see the difference.

===Setting a mask===
In order to work with data that falls only inside of this new sub-basin area rather than working with the full extent of the DEM or region you currently have set (i.e. as a result of zooming), you must set a mask. Setting a mask 'ignores' those areas that fall outside of the designated mask area on all subsequent operations, blocking them from analysis. This program can only be run interactively.

Type the GRASS command: 
'''grass> r.mask'''

Choose option 2 'Identify a new mask'

You will be prompted to enter the name of a raster map layer 
'''grass> new_basin_name'''

You will be shown a listing of this map's categories, and asked to assign a value of "1" or "0" to each map category. Areas assigned category value "1" will become part of the mask's surface, while areas assigned category value "0" will become "no data" areas in the MASK file.

Hit enter to move your cursor to the second category and type 1 in the space (type 1 next to all non-zero categories), hit <Esc><Enter> as instructed at the bottom of the page. You will be returned to the option page where you will see listed at the top of the screen that the current mask is new_basin_name, enter to return to the GRASS prompt.

Now if you display the DEM you will only see the area of the DEM that falls inside the new_basin_name basin area. 
'''grass> d.rast map=hjadem'''

Now reset the region to the geographic boundaries of new_basin_name with the g.region zoom option (sets the current region settings to the smallest region encompassing all non-zero data in the named raster map layer):
'''grass> g.region raster=new_basin_name zoom=new_basin_name''' 
'''grass> d.redraw'''

You should now have a much closer view of the DEM for new_basin_name.

===Zones===

Zones denote areas of similar climate. Zones store climate variables such as radiation, temperature etc... Each zone is linked to an input climate station. Precipitation and temperature data, for example, from this station are modified based on zone elevation, slope and aspect relative to the climate station. Zone processing also generates climate data not available from climate station (i.e. zones will estimate radiation fluxes if they are not available). Numerous strategies exist to partition areas of similar climate. Elevation bands in a mountainous area, for example, are likely to denote similarity. Distribution of climate stations can also be used to define zone partitioning, where each zone defines the area associated with a particular climate station. For these exercises, you will not be creating a zone map, as meteorological data from 1 climate station is sufficient for this small watershed. In this instance, it
is best to use the same map for zones as you use for hillslopes.

===Ksat0, m, and roads===
You will now use the GRASS raster map layer data calculator to create additional maps required to run RHESSys. The maps you will create in this exercise are the basic maps required to run RHESSys. However, this GRASS command can also be used to perform many arithmetic functions involving one or several existing map layers to create new map layers. See the GRASS website for a list of arithmetic operators.

The GRASS command r.mapcalc is typed in the form: 
'''grass> r.mapcalc 'result = expression' '''

where result is the name of the new map you are creating and expression is the arithmetic
being performed. Use r.mapcalc to generate three additional maps needed by RHESSys. The m and Ksat0 maps define spatial patterns of two soil hydrologic parameters. For this exercise we will assume these parameters do not vary spatially and use the same value for the entire watershed.

Type the following GRASS commands to create maps for Ksat0, m, and roads: (the ' are deliberate characters) 
'''grass> r.mapcalc 'K = new_basin_name * 2' ''' 
'''grass> r.mapcalc 'm = new_basin_name * 0.12' ''' 
'''grass> r.mapcalc 'zero = 0' ''' (zero will be used as the road map as there are no roads in this watershed)

When you created new_basin_name, it was assigned a value of 1. The multiplication operator (*) was used to create a new map called K (Ksat0-saturated soil hydraulic conductivity at the surface) that covers the extent of this sub-basin, which will have a value of 2, and a new map called m (decay of hydraulic conductivity with depth) with a value of 0.12. You also created a road map equal to zero to indicate that there are no roads in this dataset. K and m should be initialized based on values for the soil type in your area of study (see website for soil type values).

===Patches===
The final map required for a basic RHESSys run is the patch map. Patches represent the smallest resolution spatial unit and define areas of similar soil moisture and land cover characteristics. Vertical soil moisture processing and soil biogeochemistry are modeled within each unit defined as a patch. Lateral transport of material and water occurs between patches, so patch definition must reflect drainage organization of the watershed. You have considerable flexibility in defining a patch structure; patches can be strictly grid-based (i.e. based on 30m DEM), or of arbitrary shape (reflecting the patterns of relevant variability within the landscape, i.e. wetness index, vegetation cover, and stream/road networks).

However, when defining a patch structure attention should be given to the landscape size due to the associated processing time. Most of the processing in RHESSYS – for patch and stratum processes – is done at the patch spatial level. These processes must be performed for each individual patch. Therefore, the more patches there are, the more processing that must be done. Choosing a smaller resolution spatial unit will increase the number of patches, therefore, increase total processing time for a simulation.

For this exercise, you will define the patch structure for new_map_name based on the 30 meter DEM. The GRASS command r.clump re-categorizes data in a raster map layer by grouping cells that form physically discrete areas into unique categories. 
'''grass> r.clump input=hjadem output=new_map_name.cl'''

By user defined convention, when a map is clumped the extension .cl is added to the map name to identify that the r.clump function has be done.

To look at the patch structure: 
'''grass> d.rast map=new_map_name.cl'''

===Stratum===

Strata define vertical, aspatial layers within the patch. Processes such as photosynthesis and transpiration are modeled at the stratum level. Strata usually have the same spatial structure as patches. So the patch (new_map_name.cl) map will also be used to define the stratum object.

You have now created all the maps necessary for RHESSys to define the landscape representation. For now, however, you can quit out of GRASS (G> quit) and work on the additional timeseries data sets required to run RHESSys.

===Carbon Stores===

==Developing timeseries data sets==
Climate
RHESSys requires daily climate inputs for precipitation, minimum and maximum air temperature. These climate inputs are linked to zones in the landscape representation by a base station ID affiliated with that zone. A single base station will typically serve multiple (or all) zones within the landscape. Each base station is described by a base station file and stored in the clim directory.

The tutorial data set included a base station file (w8_base) and 3 climate files (w8_daily.rain, w8_daily.tmin, w8_daily.tmax) for a small watershed (w8) in the HJA that you should have copied into your clim directory. Have a look at the base station file structure.

From the UNIX prompt: 
'''unix> more w8_base'''

Take note of the following content:

Line 1: 101 base_station_id.
This ID will be read by zones in the landscape to link it to the base station climate file.

Line 4: 485 z_coordinate.
Elevation (in meters) of meterological station where climate data was collected.

Line 11: ../clim/w8_daily daily_climate_prefix.
Tells the base station what daily precipitation and temperature files to read, and the directory they are in.

NOTE: if you were developing your own climate input files, you would edit this base station file to reflect your meteorological station elevation and daily climate prefix.

Each of the climate input files (precipitation, maximum temperature and minimum temperature) is contained in a separate file. RHESSys assumes that the climate input files associated with a base station are all named with the same prefix (i.e. w8_daily = daily climate inputs for w8). A filename extension specifying the kind of climate variable (ie. precipitation, maximum or minimum temperature) contained in each file is attached to the end of the prefix. The prefix is then given in the base station description file, directing it to read in all climate files with that prefix.

There are 3 required climate input files - precipitaiton, minimum and maximum daily temperature. (There are also a number of optional climate inputs. If optional climate sequences are not available/used, a process model within RHESSys will provide estimates of these variables. See the RHESSys website for more information.) RHESSys requires the climate files to be in a particular format:

Review the structure of these climate input files. The first line of each input time series file must give the starting date of the time series (Year Month Day Hour). Following the starting date, daily time series values are listed sequentially.

'''unix> more w8_daily.rain''' (daily precipitation in meters)
These are long files, to end viewing a file, type U> q.
'''unix> more w8_daily.tmax''' (daily maximum temperature °C)
'''unix> more w8_daily.tmin''' (daily minimum temperature °C)

Developing your own daily climate files may require some preprocessing in order to format the data so it can be read by RHESSys. Be sure to check for missing data and make sure data is in the correct units. The RHESSys website describes a process for dealing with missing data and formatting it for RHESSys. It is also a good idea to inspect a graph of your input time series data visually to check for abnormal spikes or unrealistic values such as negative precipitation events. You may need to use a statistical computation program such as R, S-Plus, SPSS, or Excel to fill in missing data.

A climate data file should only consist of the start date at the top, followed by 1 value for each day. When naming the files you can use any name you want for the beginning of the prefix (just make sure all three have the same prefix). However, by convention, the prefix should include the time period of the data (i.e. daily, to distinguish these from hourly time series inputs, an optional input type in RHESSys) followed by the extensions: .rain, .tmin, .tmax

NOTE: Depending on the program you use to save your data files, it may attach an additional file extension to the end of the file (such as .txt). When you bring the files into your UNIX clim directory, make sure to remove any file extensions.
Also, if you develop the files on a PC and transfer them to UNIX, you may need to run the converter dos2unix to convert from DOS text format to UNIX format - which will remove the ^M characters from the file. If you open one of the files with vi, you can see if the characters are present.

==Streamflow==
You will need observed streamflow data for calibration. As with climate, when creating your own streamflow files some preprocessing may be necessary to check for missing or abnormal data, and for formatting. When used in the calibration procedure (discussed in Module III) format for streamflow files is the same as for climate files. The Observed streamflow has been provided for w8 (obs.wy79_80dw8) for the exercises you will do in the next module.

RHESSys outputs streamflow in millimeters per day (streamflow normalized by basin area), so the observed streamflow must also be converted to millimeters per day. (RHESSys also aggregates output at a monthly timestep in the event you only have observed monthly streamflow.)

For example, the USGS uses cubic-feet per second (CFS) as their unit of measurement, so you would need to convert from CFS to mm/day. To convert from mean daily CFS to mm per day, you need to know the area of the watershed draining to the gage you have streamflow (Q) data for in square feet.

(If necessary, to convert area in hectares (ha) to square feet (sq.ft.), multiply ha by 107639.104169.)

To convert mean CFS to mm per day:

1. divide mean CFS by the basin area in sq.ft = Q ft/sec

2. multiply Q ft/sec by 86400 = Q ft/day

3. multiply Q ft/day by 304.8 = Q mm/day

Preparing input data sets

2010-09-28T23:49:01Z

Dgroulx: /* Creating horizon maps */

The GRASS GIS program will be used to process and store your set of spatial data layers associated with a project. The latest GRASS build
can be downloaded at [http://grass.itc.it/ http://grass.itc.it].

==Set the geographic region==

A region refers to a geographic area with some defined boundaries, based on a specific map coordinate system and map projection. In GRASS, each region also has associated with it the specific east-west and north-south resolutions of its smallest units (rectangular units called "cells").

The region's boundaries are given as the northernmost, southernmost, easternmost, and westernmost points that define its extent. The north and south boundaries are commonly called northings, while the east and west boundaries are called eastings.

You need to set the geographic region for your personal mapset. For now, this will be the same as the DEM. Set the region with: 
'''grass> g.region rast=<dem>'''

To find out the settings of the current region: 
'''grass> g.region –p'''

This will tell you the projection, zone, datum, ellipsoid, N/S/E/W coordinates, resolution,
and number of rows and columns of your DEM.

==Start a display monitor and view a map==

To look at the DEM, start a monitor with the GRASS command: 
'''grass> d.mon start=x0'''

This will start a graphics display monitor called x0.
You can have up to 10 monitors open at once (each one must be started with
grass> d.mon start=x_); each must be assigned a different number, i.e. x0, x1, x2, etc...; when you have more than one monitor open, select one for use with the command: 
'''grass> d.mon select=x2'''

To display the raster map layer, type the GRASS command: 
'''grass> d.rast map=hjadem'''

To clear the monitor, type the GRASS command: 
'''grass> d.erase'''

==Defining a watershed boundary==
Rather than working with the full extent of the DEM (which probably contains areas outside of the watershed you are interested in) you can define the boundaries of a landscape that drain to a specific point (or outlet). You will use the GRASS watershed basin creation program (r.water.outlet) to define the boundaries for a sub-watershed within the HJ Andrews basin. First however, r.water.outlet requires a drainage direction map that must be created with the GRASS program r.watershed.

To create the drainage direction map, type the GRASS command: 
'''grass> r.watershed elevation=hjadem drainage=hja_drain'''

This traces the flow through the elevation model and creates a new raster map called drain in your personal mapset.

GRASS recognizes geographic coordinates as the Easting and Northing of each point across the landscape. To define the watershed boundaries associated with a particular outlet, you will need to identify the Easting (E) and Northing (N) of a point on the stream network.
For this exercise, you can experiment with picking any point you choose on the stream network, regardless if it is a gaged stream or not. The purpose of this exercise is simply to acquaint you with how to create a sub-watershed.

Generally, you will want to work with a watershed for which you have some measured information, such as streamflow, soil moisture, or LAI, so you have observed data to compare model results to. This is most often observed streamflow data, which is widely and readily available from many gaged streams. Therefore, you attempt to delineate the modeled watershed to match the real watershed draining to that gage. To identify the outlet point for a gaged stream, it is helpful to overlay a map of stream gages on the stream network if available. To do this, you will need to import the stream and gage maps provided with the tutorial data set into GRASS. At the beginning of this tutorial, you should have copied the ascii files hjagages.asc and hjastreams.asc into your grassdata directory.

==Importing files into grass==

To import ascii raster files into GRASS, direct input to the ascii map, give the resultant map an output name, and set null values to 0 (read working in GRASS and UNIX below): 
'''grass> r.in.ascii input=/full_path_name/hjagages.asc output=hjagages nv=0'''

'''grass> r.in.ascii input=/full_path_name/hjastreams.asc output=hjastreams nv=0'''

(GRASS supports many formats. For information on importing different formats, i.e. ARC-ASCII-GRID with r.in.arc, ESRI/E00 with m.in.e00, see the GRASS data import help webpage).

Display the maps, overlaying the gages on the streams, with: 
'''grass> d.rast map=hjastreams''' 
'''grass> d.rast -o map=hjagages'''

A map of the stream network overlain by the stream gages should be displayed in your monitor. Note the gages are very small points across the watershed and can be hard to see without zooming in, which will be discussed shortly.

This map illustrates gage locations throughout the HJA.

Identify an outlet point
To identify location information on either the stream or gage maps, type the GRASS command 
'''grass> d.what.rast'''

Move the cursor over the display; use the left mouse button to click on a gage point. The E and N and map category value of the point you clicked will be displayed on your terminal window. Right click to end the session.

If you are having trouble placing your mouse right on top of a gage point, it may be helpful to zoom in with the GRASS command
'''grass> d.zoom'''

Follow the on screen instructions using the mouse to zoom in on a gage or group of gages. Then use '''grass> d.what.rast''' to query the points.

NOTE: You want to find the E and N coordinates for an outlet that falls on the stream network in order to delineate the boundary of all area draining to that point. However, the gages may not fall exactly on the stream network, so you may need to adjust where you choose your E and N coordinates so the point you choose falls on the stream network as close to the gage as possible.
d.zoom resets the region to the area you are zoomed in on. Any additional functions
you perform after zooming in would only process the area you are zoomed in on. As you
may be zoomed in very tightly on a stream segment and the full area of the watershed
you want to capture may not be displayed, you should reset your region with: 
'''grass> g.region rast=hjadem'''

To redisplay the map at the full extent of the hjadem region, you could use: 
'''grass> d.redraw'''

Or to clear your monitor, use: 
'''grass> d.erase'''

==Create a watershed==
Once you have the location of an outlet (the E and N coordinates), you can generate the sub-basin from the drainage direction map created with r.watershed and the E and N coordinates you isolated with r.what.rast. 

'''G> r.water.outlet drainage=drain basin=new_basin_name easting=xxx northing=xxx'''

This will generate a watershed basin map (new_basin_name) from the drainage direction
map (drain) and put it in your personal mapset. This map will have a value of 1 everywhere inside the boundary, and a value of 0 everywhere that falls outside of new_basin_name (ie. the rest of the DEM).

Display this map: 
'''G> d.rast map=new_basin_name'''

NOTE: Remember, the set of coordinates you use represents the outlet point of the
watershed, and the watershed basin is all area upstream of that point that drains to that point. Therefore, if the point you choose is on a hill slope, the resulting map will only reflect the small sliver of land uphill that drains to that point. This may take several tries, so don't get frustrated!

Using the overlay option with a new map generated from an existing map 
When you create a new map that represents a portion of the extent of an
existing map, you may need to run the GRASS command r.support in order to set all null
values to transparent. For example, you would use r.support if you wanted to overlay
new_basin_name on top of the DEM so that all areas outside of the new sub- basin were
transparent, allowing the DEM underneath to show through. You may find the GRASS
command r.support helpful as you create new maps. r.support can only be run interactively.
To use it for the purpose of setting null values to transparent, accept the default (no) for
the first six questions, but answer yes to the last question ‘Do you want to delete null file
for map_name?’ Answer yes.

==Preparing spatial input data sets==
You have a DEM (hjadem) and have now created a basin (new_basin_name) map. However, RHESSys requires additional spatial data to form a complete landscape representation and establish connectivity between spatial units. One of the unique features of RHESSys is its hierarchical landscape representation. RHESSys partitions the landscape into a hierarchical spatial structure, where each level of the spatial hierarchy fully covers the spatial extent of the landscape. For example, stratum (vegetation) are processed within each patch, patches are contained within hillslopes and zones, which are units contained within the full basin. Each level of the hierarchy is defined as a particular object type with a set of storage (state) and flux variables, and an associated set of model parameters (default files).

Object type and associated processes:
* Basin - defines the drainage basin, full extent of location being modeled.
* Hillslope - defines areas which drain to a single point or stream reach.
* Zone - denotes areas of similar climate.
* Patch - soil moisture processes and carbon and nitrogen cycling.
* Stratum - vertical layers within a patch (ie. vegetation)

From the DEM you'll need to derive the following maps:
* Slope
* Aspect
* Basin
* Hillslope
* Patch
* Saturated soil hydraulic conductivity at the surface (Ksat0)
* Decay of hydraulic conductivity with depth (m)
*Stream network
*Roads

===Creating horizon maps===

RHESSys expects horizon values as sin(horizon angle). You will need to compute two horizon maps, one
for east, and one for west. In GRASS, you would do this with the commands

'''g> r.horizon -d elevin=<DEM> direction=0 horizon=horizon'''

'''g> r.horizon -d elevin=<DEM> direction=180 horizon=horizon'''

This will produce two maps, horizon_0, and horizon_180, where 0 is east and 180 is west. These maps are
the horizon in degrees though, so you will need to use mapcalc to create new maps with the sin of these
values.

'''g> r.mapcalc 'east_horizon = sin(horizon_0)' '''

'''g> r.mapcalc 'west_horizon = sin(horizon_180)' '''

These two maps will be referenced by your template file.

===Create slope and aspect maps===
To generate slope and aspect layers for the new_basin_name map from the DEM, give the
the input elevation map (el), and output names for both the slope and aspect maps.
For this exercise use the following: 
'''grass> r.slope.aspect el=hjadem slope=slope aspect=aspect'''

This will create 2 new maps in your personal mapset, slope and aspect. You can name
these maps whatever you want, but by convention, they are generally called slope and
aspect. As you created these for the full DEM, you may want to use demslope, etc….
If you were still zoomed in and did not reset your region to the full extent of the DEM
then you may want to give your slope and aspect maps an identifying extension.

Verify the maps are there with: 
'''grass> g.list type=rast mapset=your_userID'''
will list maps only in your personal mapset directory.

===Create hillslope and stream maps===
You will use a GRASS watershed basin analysis program to generate a set of maps used to delineate key spatial layers in RHESSys. RHESSys uses different spatial objects to model specific hydro-ecological processes. These objects form a hierarchical representation of the landscapes key objects. The hillslope and stream maps are necessary as they represent key landscape objects. The GRASS r.watershed program creates maps of watershed basins, hillslopes, flow accumulation, drainage direction, and stream segments within a DEM. You only want to create these maps for the new_basin_name portion of the DEM.

For this step, zoom in on the new_basin_name map fairly close, however, leave at
least one pixel width of space around the watershed. As d.zoom resets the region, it
allows you to work with only the portion of the map displayed as you create additional maps in this step. 
'''grass> d.zoom'''

Hillslopes are defined as land area draining either side of a stream reach in each sub-basin. Hillslopes are created by breaking up the watershed into sub basins associated with a particular stream reach. To generate a hillslope map and a stream map, you will use the r.watershed program (r.watershed was used to create the hjastreams map you viewed previously). This program can be run interactively or non-interactively. To run non-interactively (command line): 
'''grass> r.watershed el=hjadem t=100 ac=acc dr=drain ba=b100 ha=h100 stream=str100'''

The proceeding was an abbreviation of: 
'''grass> r.watershed elevation=hjadem threshold=100 accumulation=acc drainage=drain basin=b100 half.basin=h100 stream=str100'''

Where threshold sets the aggregation value, elevation is the input map, and the rest are output maps.

This will put several new maps in your PERMANENT mapset (you can check with g.list). You can name the output maps whatever you choose, this is simply the convention established by previous RHESSys users (h100 indicates hillslopes at a threshold of 100 cells, etc...). Threshold represents the minimum size of a sub-basin in cells, or overland flow units. Try experimenting with different threshold values (i.e. try additional thresholds at 50 and 200), then display the hillslope maps (in different monitors) to see the difference.

===Setting a mask===
In order to work with data that falls only inside of this new sub-basin area rather than working with the full extent of the DEM or region you currently have set (i.e. as a result of zooming), you must set a mask. Setting a mask 'ignores' those areas that fall outside of the designated mask area on all subsequent operations, blocking them from analysis. This program can only be run interactively.

Type the GRASS command: 
'''grass> r.mask'''

Choose option 2 'Identify a new mask'

You will be prompted to enter the name of a raster map layer 
'''grass> new_basin_name'''

You will be shown a listing of this map's categories, and asked to assign a value of "1" or "0" to each map category. Areas assigned category value "1" will become part of the mask's surface, while areas assigned category value "0" will become "no data" areas in the MASK file.

Hit enter to move your cursor to the second category and type 1 in the space (type 1 next to all non-zero categories), hit <Esc><Enter> as instructed at the bottom of the page. You will be returned to the option page where you will see listed at the top of the screen that the current mask is new_basin_name, enter to return to the GRASS prompt.

Now if you display the DEM you will only see the area of the DEM that falls inside the new_basin_name basin area. 
'''grass> d.rast map=hjadem'''

Now reset the region to the geographic boundaries of new_basin_name with the g.region zoom option (sets the current region settings to the smallest region encompassing all non-zero data in the named raster map layer):
'''grass> g.region raster=new_basin_name zoom=new_basin_name''' 
'''grass> d.redraw'''

You should now have a much closer view of the DEM for new_basin_name.

===Zones===

Zones denote areas of similar climate. Zones store climate variables such as radiation, temperature etc... Each zone is linked to an input climate station. Precipitation and temperature data, for example, from this station are modified based on zone elevation, slope and aspect relative to the climate station. Zone processing also generates climate data not available from climate station (i.e. zones will estimate radiation fluxes if they are not available). Numerous strategies exist to partition areas of similar climate. Elevation bands in a mountainous area, for example, are likely to denote similarity. Distribution of climate stations can also be used to define zone partitioning, where each zone defines the area associated with a particular climate station. For these exercises, you will not be creating a zone map, as meteorological data from 1 climate station is sufficient for this small watershed. In this instance, it
is best to use the same map for zones as you use for hillslopes.

===Ksat0, m, and roads===
You will now use the GRASS raster map layer data calculator to create additional maps required to run RHESSys. The maps you will create in this exercise are the basic maps required to run RHESSys. However, this GRASS command can also be used to perform many arithmetic functions involving one or several existing map layers to create new map layers. See the GRASS website for a list of arithmetic operators.

The GRASS command r.mapcalc is typed in the form: 
'''grass> r.mapcalc 'result = expression' '''

where result is the name of the new map you are creating and expression is the arithmetic
being performed. Use r.mapcalc to generate three additional maps needed by RHESSys. The m and Ksat0 maps define spatial patterns of two soil hydrologic parameters. For this exercise we will assume these parameters do not vary spatially and use the same value for the entire watershed.

Type the following GRASS commands to create maps for Ksat0, m, and roads: (the ' are deliberate characters) 
'''grass> r.mapcalc 'K = new_basin_name * 2' ''' 
'''grass> r.mapcalc 'm = new_basin_name * 0.12' ''' 
'''grass> r.mapcalc 'zero = 0' ''' (zero will be used as the road map as there are no roads in this watershed)

When you created new_basin_name, it was assigned a value of 1. The multiplication operator (*) was used to create a new map called K (Ksat0-saturated soil hydraulic conductivity at the surface) that covers the extent of this sub-basin, which will have a value of 2, and a new map called m (decay of hydraulic conductivity with depth) with a value of 0.12. You also created a road map equal to zero to indicate that there are no roads in this dataset. K and m should be initialized based on values for the soil type in your area of study (see website for soil type values).

===Patches===
The final map required for a basic RHESSys run is the patch map. Patches represent the smallest resolution spatial unit and define areas of similar soil moisture and land cover characteristics. Vertical soil moisture processing and soil biogeochemistry are modeled within each unit defined as a patch. Lateral transport of material and water occurs between patches, so patch definition must reflect drainage organization of the watershed. You have considerable flexibility in defining a patch structure; patches can be strictly grid-based (i.e. based on 30m DEM), or of arbitrary shape (reflecting the patterns of relevant variability within the landscape, i.e. wetness index, vegetation cover, and stream/road networks).

However, when defining a patch structure attention should be given to the landscape size due to the associated processing time. Most of the processing in RHESSYS – for patch and stratum processes – is done at the patch spatial level. These processes must be performed for each individual patch. Therefore, the more patches there are, the more processing that must be done. Choosing a smaller resolution spatial unit will increase the number of patches, therefore, increase total processing time for a simulation.

For this exercise, you will define the patch structure for new_map_name based on the 30 meter DEM. The GRASS command r.clump re-categorizes data in a raster map layer by grouping cells that form physically discrete areas into unique categories. 
'''grass> r.clump input=hjadem output=new_map_name.cl'''

By user defined convention, when a map is clumped the extension .cl is added to the map name to identify that the r.clump function has be done.

To look at the patch structure: 
'''grass> d.rast map=new_map_name.cl'''

===Stratum===

Strata define vertical, aspatial layers within the patch. Processes such as photosynthesis and transpiration are modeled at the stratum level. Strata usually have the same spatial structure as patches. So the patch (new_map_name.cl) map will also be used to define the stratum object.

You have now created all the maps necessary for RHESSys to define the landscape representation. For now, however, you can quit out of GRASS (G> quit) and work on the additional timeseries data sets required to run RHESSys.

===Carbon Stores===

==Developing timeseries data sets==
Climate
RHESSys requires daily climate inputs for precipitation, minimum and maximum air temperature. These climate inputs are linked to zones in the landscape representation by a base station ID affiliated with that zone. A single base station will typically serve multiple (or all) zones within the landscape. Each base station is described by a base station file and stored in the clim directory.

The tutorial data set included a base station file (w8_base) and 3 climate files (w8_daily.rain, w8_daily.tmin, w8_daily.tmax) for a small watershed (w8) in the HJA that you should have copied into your clim directory. Have a look at the base station file structure.

From the UNIX prompt: 
'''unix> more w8_base'''

Take note of the following content:

Line 1: 101 base_station_id.
This ID will be read by zones in the landscape to link it to the base station climate file.

Line 4: 485 z_coordinate.
Elevation (in meters) of meterological station where climate data was collected.

Line 11: ../clim/w8_daily daily_climate_prefix.
Tells the base station what daily precipitation and temperature files to read, and the directory they are in.

NOTE: if you were developing your own climate input files, you would edit this base station file to reflect your meteorological station elevation and daily climate prefix.

Each of the climate input files (precipitation, maximum temperature and minimum temperature) is contained in a separate file. RHESSys assumes that the climate input files associated with a base station are all named with the same prefix (i.e. w8_daily = daily climate inputs for w8). A filename extension specifying the kind of climate variable (ie. precipitation, maximum or minimum temperature) contained in each file is attached to the end of the prefix. The prefix is then given in the base station description file, directing it to read in all climate files with that prefix.

There are 3 required climate input files - precipitaiton, minimum and maximum daily temperature. (There are also a number of optional climate inputs. If optional climate sequences are not available/used, a process model within RHESSys will provide estimates of these variables. See the RHESSys website for more information.) RHESSys requires the climate files to be in a particular format:

Review the structure of these climate input files. The first line of each input time series file must give the starting date of the time series (Year Month Day Hour). Following the starting date, daily time series values are listed sequentially.

'''unix> more w8_daily.rain''' (daily precipitation in meters)
These are long files, to end viewing a file, type U> q.
'''unix> more w8_daily.tmax''' (daily maximum temperature °C)
'''unix> more w8_daily.tmin''' (daily minimum temperature °C)

Developing your own daily climate files may require some preprocessing in order to format the data so it can be read by RHESSys. Be sure to check for missing data and make sure data is in the correct units. The RHESSys website describes a process for dealing with missing data and formatting it for RHESSys. It is also a good idea to inspect a graph of your input time series data visually to check for abnormal spikes or unrealistic values such as negative precipitation events. You may need to use a statistical computation program such as R, S-Plus, SPSS, or Excel to fill in missing data.

A climate data file should only consist of the start date at the top, followed by 1 value for each day. When naming the files you can use any name you want for the beginning of the prefix (just make sure all three have the same prefix). However, by convention, the prefix should include the time period of the data (i.e. daily, to distinguish these from hourly time series inputs, an optional input type in RHESSys) followed by the extensions: .rain, .tmin, .tmax

NOTE: Depending on the program you use to save your data files, it may attach an additional file extension to the end of the file (such as .txt). When you bring the files into your UNIX clim directory, make sure to remove any file extensions.
Also, if you develop the files on a PC and transfer them to UNIX, you may need to run the converter dos2unix to convert from DOS text format to UNIX format - which will remove the ^M characters from the file. If you open one of the files with vi, you can see if the characters are present.

==Streamflow==
You will need observed streamflow data for calibration. As with climate, when creating your own streamflow files some preprocessing may be necessary to check for missing or abnormal data, and for formatting. When used in the calibration procedure (discussed in Module III) format for streamflow files is the same as for climate files. The Observed streamflow has been provided for w8 (obs.wy79_80dw8) for the exercises you will do in the next module.

RHESSys outputs streamflow in millimeters per day (streamflow normalized by basin area), so the observed streamflow must also be converted to millimeters per day. (RHESSys also aggregates output at a monthly timestep in the event you only have observed monthly streamflow.)

For example, the USGS uses cubic-feet per second (CFS) as their unit of measurement, so you would need to convert from CFS to mm/day. To convert from mean daily CFS to mm per day, you need to know the area of the watershed draining to the gage you have streamflow (Q) data for in square feet.

(If necessary, to convert area in hectares (ha) to square feet (sq.ft.), multiply ha by 107639.104169.)

To convert mean CFS to mm per day:

1. divide mean CFS by the basin area in sq.ft = Q ft/sec

2. multiply Q ft/sec by 86400 = Q ft/day

3. multiply Q ft/day by 304.8 = Q mm/day

Preparing input data sets

2010-09-28T23:48:12Z

Dgroulx:

The GRASS GIS program will be used to process and store your set of spatial data layers associated with a project. The latest GRASS build
can be downloaded at [http://grass.itc.it/ http://grass.itc.it].

==Set the geographic region==

A region refers to a geographic area with some defined boundaries, based on a specific map coordinate system and map projection. In GRASS, each region also has associated with it the specific east-west and north-south resolutions of its smallest units (rectangular units called "cells").

The region's boundaries are given as the northernmost, southernmost, easternmost, and westernmost points that define its extent. The north and south boundaries are commonly called northings, while the east and west boundaries are called eastings.

You need to set the geographic region for your personal mapset. For now, this will be the same as the DEM. Set the region with: 
'''grass> g.region rast=<dem>'''

To find out the settings of the current region: 
'''grass> g.region –p'''

This will tell you the projection, zone, datum, ellipsoid, N/S/E/W coordinates, resolution,
and number of rows and columns of your DEM.

==Start a display monitor and view a map==

To look at the DEM, start a monitor with the GRASS command: 
'''grass> d.mon start=x0'''

This will start a graphics display monitor called x0.
You can have up to 10 monitors open at once (each one must be started with
grass> d.mon start=x_); each must be assigned a different number, i.e. x0, x1, x2, etc...; when you have more than one monitor open, select one for use with the command: 
'''grass> d.mon select=x2'''

To display the raster map layer, type the GRASS command: 
'''grass> d.rast map=hjadem'''

To clear the monitor, type the GRASS command: 
'''grass> d.erase'''

==Defining a watershed boundary==
Rather than working with the full extent of the DEM (which probably contains areas outside of the watershed you are interested in) you can define the boundaries of a landscape that drain to a specific point (or outlet). You will use the GRASS watershed basin creation program (r.water.outlet) to define the boundaries for a sub-watershed within the HJ Andrews basin. First however, r.water.outlet requires a drainage direction map that must be created with the GRASS program r.watershed.

To create the drainage direction map, type the GRASS command: 
'''grass> r.watershed elevation=hjadem drainage=hja_drain'''

This traces the flow through the elevation model and creates a new raster map called drain in your personal mapset.

GRASS recognizes geographic coordinates as the Easting and Northing of each point across the landscape. To define the watershed boundaries associated with a particular outlet, you will need to identify the Easting (E) and Northing (N) of a point on the stream network.
For this exercise, you can experiment with picking any point you choose on the stream network, regardless if it is a gaged stream or not. The purpose of this exercise is simply to acquaint you with how to create a sub-watershed.

Generally, you will want to work with a watershed for which you have some measured information, such as streamflow, soil moisture, or LAI, so you have observed data to compare model results to. This is most often observed streamflow data, which is widely and readily available from many gaged streams. Therefore, you attempt to delineate the modeled watershed to match the real watershed draining to that gage. To identify the outlet point for a gaged stream, it is helpful to overlay a map of stream gages on the stream network if available. To do this, you will need to import the stream and gage maps provided with the tutorial data set into GRASS. At the beginning of this tutorial, you should have copied the ascii files hjagages.asc and hjastreams.asc into your grassdata directory.

==Importing files into grass==

To import ascii raster files into GRASS, direct input to the ascii map, give the resultant map an output name, and set null values to 0 (read working in GRASS and UNIX below): 
'''grass> r.in.ascii input=/full_path_name/hjagages.asc output=hjagages nv=0'''

'''grass> r.in.ascii input=/full_path_name/hjastreams.asc output=hjastreams nv=0'''

(GRASS supports many formats. For information on importing different formats, i.e. ARC-ASCII-GRID with r.in.arc, ESRI/E00 with m.in.e00, see the GRASS data import help webpage).

Display the maps, overlaying the gages on the streams, with: 
'''grass> d.rast map=hjastreams''' 
'''grass> d.rast -o map=hjagages'''

A map of the stream network overlain by the stream gages should be displayed in your monitor. Note the gages are very small points across the watershed and can be hard to see without zooming in, which will be discussed shortly.

This map illustrates gage locations throughout the HJA.

Identify an outlet point
To identify location information on either the stream or gage maps, type the GRASS command 
'''grass> d.what.rast'''

Move the cursor over the display; use the left mouse button to click on a gage point. The E and N and map category value of the point you clicked will be displayed on your terminal window. Right click to end the session.

If you are having trouble placing your mouse right on top of a gage point, it may be helpful to zoom in with the GRASS command
'''grass> d.zoom'''

Follow the on screen instructions using the mouse to zoom in on a gage or group of gages. Then use '''grass> d.what.rast''' to query the points.

NOTE: You want to find the E and N coordinates for an outlet that falls on the stream network in order to delineate the boundary of all area draining to that point. However, the gages may not fall exactly on the stream network, so you may need to adjust where you choose your E and N coordinates so the point you choose falls on the stream network as close to the gage as possible.
d.zoom resets the region to the area you are zoomed in on. Any additional functions
you perform after zooming in would only process the area you are zoomed in on. As you
may be zoomed in very tightly on a stream segment and the full area of the watershed
you want to capture may not be displayed, you should reset your region with: 
'''grass> g.region rast=hjadem'''

To redisplay the map at the full extent of the hjadem region, you could use: 
'''grass> d.redraw'''

Or to clear your monitor, use: 
'''grass> d.erase'''

==Create a watershed==
Once you have the location of an outlet (the E and N coordinates), you can generate the sub-basin from the drainage direction map created with r.watershed and the E and N coordinates you isolated with r.what.rast. 

'''G> r.water.outlet drainage=drain basin=new_basin_name easting=xxx northing=xxx'''

This will generate a watershed basin map (new_basin_name) from the drainage direction
map (drain) and put it in your personal mapset. This map will have a value of 1 everywhere inside the boundary, and a value of 0 everywhere that falls outside of new_basin_name (ie. the rest of the DEM).

Display this map: 
'''G> d.rast map=new_basin_name'''

NOTE: Remember, the set of coordinates you use represents the outlet point of the
watershed, and the watershed basin is all area upstream of that point that drains to that point. Therefore, if the point you choose is on a hill slope, the resulting map will only reflect the small sliver of land uphill that drains to that point. This may take several tries, so don't get frustrated!

Using the overlay option with a new map generated from an existing map 
When you create a new map that represents a portion of the extent of an
existing map, you may need to run the GRASS command r.support in order to set all null
values to transparent. For example, you would use r.support if you wanted to overlay
new_basin_name on top of the DEM so that all areas outside of the new sub- basin were
transparent, allowing the DEM underneath to show through. You may find the GRASS
command r.support helpful as you create new maps. r.support can only be run interactively.
To use it for the purpose of setting null values to transparent, accept the default (no) for
the first six questions, but answer yes to the last question ‘Do you want to delete null file
for map_name?’ Answer yes.

==Preparing spatial input data sets==
You have a DEM (hjadem) and have now created a basin (new_basin_name) map. However, RHESSys requires additional spatial data to form a complete landscape representation and establish connectivity between spatial units. One of the unique features of RHESSys is its hierarchical landscape representation. RHESSys partitions the landscape into a hierarchical spatial structure, where each level of the spatial hierarchy fully covers the spatial extent of the landscape. For example, stratum (vegetation) are processed within each patch, patches are contained within hillslopes and zones, which are units contained within the full basin. Each level of the hierarchy is defined as a particular object type with a set of storage (state) and flux variables, and an associated set of model parameters (default files).

Object type and associated processes:
* Basin - defines the drainage basin, full extent of location being modeled.
* Hillslope - defines areas which drain to a single point or stream reach.
* Zone - denotes areas of similar climate.
* Patch - soil moisture processes and carbon and nitrogen cycling.
* Stratum - vertical layers within a patch (ie. vegetation)

From the DEM you'll need to derive the following maps:
* Slope
* Aspect
* Basin
* Hillslope
* Patch
* Saturated soil hydraulic conductivity at the surface (Ksat0)
* Decay of hydraulic conductivity with depth (m)
*Stream network
*Roads

===Creating horizon maps===

RHESSys expects horizon values as sin(horizon angle). You will need to compute two horizon maps, one
for east, and one for west. In GRASS, you would do this with the commands

'''g> r.horizon -d elevin=<DEM> direction=0 horizon=horizon'''
'''g> r.horizon -d elevin=<DEM> direction=180 horizon=horizon'''

This will produce two maps, horizon_0, and horizon_180, where 0 is east and 180 is west. These maps are
the horizon in degrees though, so you will need to use mapcalc to create new maps with the sin of these
values.

'''g> r.mapcalc 'east_horizon = sin(horizon_0)' '''
'''g> r.mapcalc 'west_horizon = sin(horizon_180)' '''

These two maps will be referenced by your template file.

===Create slope and aspect maps===
To generate slope and aspect layers for the new_basin_name map from the DEM, give the
the input elevation map (el), and output names for both the slope and aspect maps.
For this exercise use the following: 
'''grass> r.slope.aspect el=hjadem slope=slope aspect=aspect'''

This will create 2 new maps in your personal mapset, slope and aspect. You can name
these maps whatever you want, but by convention, they are generally called slope and
aspect. As you created these for the full DEM, you may want to use demslope, etc….
If you were still zoomed in and did not reset your region to the full extent of the DEM
then you may want to give your slope and aspect maps an identifying extension.

Verify the maps are there with: 
'''grass> g.list type=rast mapset=your_userID'''
will list maps only in your personal mapset directory.

===Create hillslope and stream maps===
You will use a GRASS watershed basin analysis program to generate a set of maps used to delineate key spatial layers in RHESSys. RHESSys uses different spatial objects to model specific hydro-ecological processes. These objects form a hierarchical representation of the landscapes key objects. The hillslope and stream maps are necessary as they represent key landscape objects. The GRASS r.watershed program creates maps of watershed basins, hillslopes, flow accumulation, drainage direction, and stream segments within a DEM. You only want to create these maps for the new_basin_name portion of the DEM.

For this step, zoom in on the new_basin_name map fairly close, however, leave at
least one pixel width of space around the watershed. As d.zoom resets the region, it
allows you to work with only the portion of the map displayed as you create additional maps in this step. 
'''grass> d.zoom'''

Hillslopes are defined as land area draining either side of a stream reach in each sub-basin. Hillslopes are created by breaking up the watershed into sub basins associated with a particular stream reach. To generate a hillslope map and a stream map, you will use the r.watershed program (r.watershed was used to create the hjastreams map you viewed previously). This program can be run interactively or non-interactively. To run non-interactively (command line): 
'''grass> r.watershed el=hjadem t=100 ac=acc dr=drain ba=b100 ha=h100 stream=str100'''

The proceeding was an abbreviation of: 
'''grass> r.watershed elevation=hjadem threshold=100 accumulation=acc drainage=drain basin=b100 half.basin=h100 stream=str100'''

Where threshold sets the aggregation value, elevation is the input map, and the rest are output maps.

This will put several new maps in your PERMANENT mapset (you can check with g.list). You can name the output maps whatever you choose, this is simply the convention established by previous RHESSys users (h100 indicates hillslopes at a threshold of 100 cells, etc...). Threshold represents the minimum size of a sub-basin in cells, or overland flow units. Try experimenting with different threshold values (i.e. try additional thresholds at 50 and 200), then display the hillslope maps (in different monitors) to see the difference.

===Setting a mask===
In order to work with data that falls only inside of this new sub-basin area rather than working with the full extent of the DEM or region you currently have set (i.e. as a result of zooming), you must set a mask. Setting a mask 'ignores' those areas that fall outside of the designated mask area on all subsequent operations, blocking them from analysis. This program can only be run interactively.

Type the GRASS command: 
'''grass> r.mask'''

Choose option 2 'Identify a new mask'

You will be prompted to enter the name of a raster map layer 
'''grass> new_basin_name'''

You will be shown a listing of this map's categories, and asked to assign a value of "1" or "0" to each map category. Areas assigned category value "1" will become part of the mask's surface, while areas assigned category value "0" will become "no data" areas in the MASK file.

Hit enter to move your cursor to the second category and type 1 in the space (type 1 next to all non-zero categories), hit <Esc><Enter> as instructed at the bottom of the page. You will be returned to the option page where you will see listed at the top of the screen that the current mask is new_basin_name, enter to return to the GRASS prompt.

Now if you display the DEM you will only see the area of the DEM that falls inside the new_basin_name basin area. 
'''grass> d.rast map=hjadem'''

Now reset the region to the geographic boundaries of new_basin_name with the g.region zoom option (sets the current region settings to the smallest region encompassing all non-zero data in the named raster map layer):
'''grass> g.region raster=new_basin_name zoom=new_basin_name''' 
'''grass> d.redraw'''

You should now have a much closer view of the DEM for new_basin_name.

===Zones===

Zones denote areas of similar climate. Zones store climate variables such as radiation, temperature etc... Each zone is linked to an input climate station. Precipitation and temperature data, for example, from this station are modified based on zone elevation, slope and aspect relative to the climate station. Zone processing also generates climate data not available from climate station (i.e. zones will estimate radiation fluxes if they are not available). Numerous strategies exist to partition areas of similar climate. Elevation bands in a mountainous area, for example, are likely to denote similarity. Distribution of climate stations can also be used to define zone partitioning, where each zone defines the area associated with a particular climate station. For these exercises, you will not be creating a zone map, as meteorological data from 1 climate station is sufficient for this small watershed. In this instance, it
is best to use the same map for zones as you use for hillslopes.

===Ksat0, m, and roads===
You will now use the GRASS raster map layer data calculator to create additional maps required to run RHESSys. The maps you will create in this exercise are the basic maps required to run RHESSys. However, this GRASS command can also be used to perform many arithmetic functions involving one or several existing map layers to create new map layers. See the GRASS website for a list of arithmetic operators.

The GRASS command r.mapcalc is typed in the form: 
'''grass> r.mapcalc 'result = expression' '''

where result is the name of the new map you are creating and expression is the arithmetic
being performed. Use r.mapcalc to generate three additional maps needed by RHESSys. The m and Ksat0 maps define spatial patterns of two soil hydrologic parameters. For this exercise we will assume these parameters do not vary spatially and use the same value for the entire watershed.

Type the following GRASS commands to create maps for Ksat0, m, and roads: (the ' are deliberate characters) 
'''grass> r.mapcalc 'K = new_basin_name * 2' ''' 
'''grass> r.mapcalc 'm = new_basin_name * 0.12' ''' 
'''grass> r.mapcalc 'zero = 0' ''' (zero will be used as the road map as there are no roads in this watershed)

When you created new_basin_name, it was assigned a value of 1. The multiplication operator (*) was used to create a new map called K (Ksat0-saturated soil hydraulic conductivity at the surface) that covers the extent of this sub-basin, which will have a value of 2, and a new map called m (decay of hydraulic conductivity with depth) with a value of 0.12. You also created a road map equal to zero to indicate that there are no roads in this dataset. K and m should be initialized based on values for the soil type in your area of study (see website for soil type values).

===Patches===
The final map required for a basic RHESSys run is the patch map. Patches represent the smallest resolution spatial unit and define areas of similar soil moisture and land cover characteristics. Vertical soil moisture processing and soil biogeochemistry are modeled within each unit defined as a patch. Lateral transport of material and water occurs between patches, so patch definition must reflect drainage organization of the watershed. You have considerable flexibility in defining a patch structure; patches can be strictly grid-based (i.e. based on 30m DEM), or of arbitrary shape (reflecting the patterns of relevant variability within the landscape, i.e. wetness index, vegetation cover, and stream/road networks).

However, when defining a patch structure attention should be given to the landscape size due to the associated processing time. Most of the processing in RHESSYS – for patch and stratum processes – is done at the patch spatial level. These processes must be performed for each individual patch. Therefore, the more patches there are, the more processing that must be done. Choosing a smaller resolution spatial unit will increase the number of patches, therefore, increase total processing time for a simulation.

For this exercise, you will define the patch structure for new_map_name based on the 30 meter DEM. The GRASS command r.clump re-categorizes data in a raster map layer by grouping cells that form physically discrete areas into unique categories. 
'''grass> r.clump input=hjadem output=new_map_name.cl'''

By user defined convention, when a map is clumped the extension .cl is added to the map name to identify that the r.clump function has be done.

To look at the patch structure: 
'''grass> d.rast map=new_map_name.cl'''

===Stratum===

Strata define vertical, aspatial layers within the patch. Processes such as photosynthesis and transpiration are modeled at the stratum level. Strata usually have the same spatial structure as patches. So the patch (new_map_name.cl) map will also be used to define the stratum object.

You have now created all the maps necessary for RHESSys to define the landscape representation. For now, however, you can quit out of GRASS (G> quit) and work on the additional timeseries data sets required to run RHESSys.

===Carbon Stores===

==Developing timeseries data sets==
Climate
RHESSys requires daily climate inputs for precipitation, minimum and maximum air temperature. These climate inputs are linked to zones in the landscape representation by a base station ID affiliated with that zone. A single base station will typically serve multiple (or all) zones within the landscape. Each base station is described by a base station file and stored in the clim directory.

The tutorial data set included a base station file (w8_base) and 3 climate files (w8_daily.rain, w8_daily.tmin, w8_daily.tmax) for a small watershed (w8) in the HJA that you should have copied into your clim directory. Have a look at the base station file structure.

From the UNIX prompt: 
'''unix> more w8_base'''

Take note of the following content:

Line 1: 101 base_station_id.
This ID will be read by zones in the landscape to link it to the base station climate file.

Line 4: 485 z_coordinate.
Elevation (in meters) of meterological station where climate data was collected.

Line 11: ../clim/w8_daily daily_climate_prefix.
Tells the base station what daily precipitation and temperature files to read, and the directory they are in.

NOTE: if you were developing your own climate input files, you would edit this base station file to reflect your meteorological station elevation and daily climate prefix.

Each of the climate input files (precipitation, maximum temperature and minimum temperature) is contained in a separate file. RHESSys assumes that the climate input files associated with a base station are all named with the same prefix (i.e. w8_daily = daily climate inputs for w8). A filename extension specifying the kind of climate variable (ie. precipitation, maximum or minimum temperature) contained in each file is attached to the end of the prefix. The prefix is then given in the base station description file, directing it to read in all climate files with that prefix.

There are 3 required climate input files - precipitaiton, minimum and maximum daily temperature. (There are also a number of optional climate inputs. If optional climate sequences are not available/used, a process model within RHESSys will provide estimates of these variables. See the RHESSys website for more information.) RHESSys requires the climate files to be in a particular format:

Review the structure of these climate input files. The first line of each input time series file must give the starting date of the time series (Year Month Day Hour). Following the starting date, daily time series values are listed sequentially.

'''unix> more w8_daily.rain''' (daily precipitation in meters)
These are long files, to end viewing a file, type U> q.
'''unix> more w8_daily.tmax''' (daily maximum temperature °C)
'''unix> more w8_daily.tmin''' (daily minimum temperature °C)

Developing your own daily climate files may require some preprocessing in order to format the data so it can be read by RHESSys. Be sure to check for missing data and make sure data is in the correct units. The RHESSys website describes a process for dealing with missing data and formatting it for RHESSys. It is also a good idea to inspect a graph of your input time series data visually to check for abnormal spikes or unrealistic values such as negative precipitation events. You may need to use a statistical computation program such as R, S-Plus, SPSS, or Excel to fill in missing data.

A climate data file should only consist of the start date at the top, followed by 1 value for each day. When naming the files you can use any name you want for the beginning of the prefix (just make sure all three have the same prefix). However, by convention, the prefix should include the time period of the data (i.e. daily, to distinguish these from hourly time series inputs, an optional input type in RHESSys) followed by the extensions: .rain, .tmin, .tmax

NOTE: Depending on the program you use to save your data files, it may attach an additional file extension to the end of the file (such as .txt). When you bring the files into your UNIX clim directory, make sure to remove any file extensions.
Also, if you develop the files on a PC and transfer them to UNIX, you may need to run the converter dos2unix to convert from DOS text format to UNIX format - which will remove the ^M characters from the file. If you open one of the files with vi, you can see if the characters are present.

==Streamflow==
You will need observed streamflow data for calibration. As with climate, when creating your own streamflow files some preprocessing may be necessary to check for missing or abnormal data, and for formatting. When used in the calibration procedure (discussed in Module III) format for streamflow files is the same as for climate files. The Observed streamflow has been provided for w8 (obs.wy79_80dw8) for the exercises you will do in the next module.

RHESSys outputs streamflow in millimeters per day (streamflow normalized by basin area), so the observed streamflow must also be converted to millimeters per day. (RHESSys also aggregates output at a monthly timestep in the event you only have observed monthly streamflow.)

For example, the USGS uses cubic-feet per second (CFS) as their unit of measurement, so you would need to convert from CFS to mm/day. To convert from mean daily CFS to mm per day, you need to know the area of the watershed draining to the gage you have streamflow (Q) data for in square feet.

(If necessary, to convert area in hectares (ha) to square feet (sq.ft.), multiply ha by 107639.104169.)

To convert mean CFS to mm per day:

1. divide mean CFS by the basin area in sq.ft = Q ft/sec

2. multiply Q ft/sec by 86400 = Q ft/day

3. multiply Q ft/day by 304.8 = Q mm/day

Preparing input data sets

2010-09-28T23:46:20Z

Dgroulx: /* Creating horizon maps */

The GRASS GIS program will be used to process and store your set of spatial data layers associated with a project. The latest GRASS build
can be downloaded at [http://grass.itc.it/ http://grass.itc.it].

==Set the geographic region==

A region refers to a geographic area with some defined boundaries, based on a specific map coordinate system and map projection. In GRASS, each region also has associated with it the specific east-west and north-south resolutions of its smallest units (rectangular units called "cells").

The region's boundaries are given as the northernmost, southernmost, easternmost, and westernmost points that define its extent. The north and south boundaries are commonly called northings, while the east and west boundaries are called eastings.

You need to set the geographic region for your personal mapset. For now, this will be the same as the DEM. Set the region with: 
'''grass> g.region rast=<dem>'''

To find out the settings of the current region: 
'''grass> g.region –p'''

This will tell you the projection, zone, datum, ellipsoid, N/S/E/W coordinates, resolution,
and number of rows and columns of your DEM.

==Start a display monitor and view a map==

To look at the DEM, start a monitor with the GRASS command: 
'''grass> d.mon start=x0'''

This will start a graphics display monitor called x0.
You can have up to 10 monitors open at once (each one must be started with
grass> d.mon start=x_); each must be assigned a different number, i.e. x0, x1, x2, etc...; when you have more than one monitor open, select one for use with the command: 
'''grass> d.mon select=x2'''

To display the raster map layer, type the GRASS command: 
'''grass> d.rast map=hjadem'''

To clear the monitor, type the GRASS command: 
'''grass> d.erase'''

==Defining a watershed boundary==
Rather than working with the full extent of the DEM (which probably contains areas outside of the watershed you are interested in) you can define the boundaries of a landscape that drain to a specific point (or outlet). You will use the GRASS watershed basin creation program (r.water.outlet) to define the boundaries for a sub-watershed within the HJ Andrews basin. First however, r.water.outlet requires a drainage direction map that must be created with the GRASS program r.watershed.

To create the drainage direction map, type the GRASS command: 
'''grass> r.watershed elevation=hjadem drainage=hja_drain'''

This traces the flow through the elevation model and creates a new raster map called drain in your personal mapset.

GRASS recognizes geographic coordinates as the Easting and Northing of each point across the landscape. To define the watershed boundaries associated with a particular outlet, you will need to identify the Easting (E) and Northing (N) of a point on the stream network.
For this exercise, you can experiment with picking any point you choose on the stream network, regardless if it is a gaged stream or not. The purpose of this exercise is simply to acquaint you with how to create a sub-watershed.

Generally, you will want to work with a watershed for which you have some measured information, such as streamflow, soil moisture, or LAI, so you have observed data to compare model results to. This is most often observed streamflow data, which is widely and readily available from many gaged streams. Therefore, you attempt to delineate the modeled watershed to match the real watershed draining to that gage. To identify the outlet point for a gaged stream, it is helpful to overlay a map of stream gages on the stream network if available. To do this, you will need to import the stream and gage maps provided with the tutorial data set into GRASS. At the beginning of this tutorial, you should have copied the ascii files hjagages.asc and hjastreams.asc into your grassdata directory.

==Importing files into grass==

To import ascii raster files into GRASS, direct input to the ascii map, give the resultant map an output name, and set null values to 0 (read working in GRASS and UNIX below): 
'''grass> r.in.ascii input=/full_path_name/hjagages.asc output=hjagages nv=0'''

'''grass> r.in.ascii input=/full_path_name/hjastreams.asc output=hjastreams nv=0'''

(GRASS supports many formats. For information on importing different formats, i.e. ARC-ASCII-GRID with r.in.arc, ESRI/E00 with m.in.e00, see the GRASS data import help webpage).

Display the maps, overlaying the gages on the streams, with: 
'''grass> d.rast map=hjastreams''' 
'''grass> d.rast -o map=hjagages'''

A map of the stream network overlain by the stream gages should be displayed in your monitor. Note the gages are very small points across the watershed and can be hard to see without zooming in, which will be discussed shortly.

This map illustrates gage locations throughout the HJA.

Identify an outlet point
To identify location information on either the stream or gage maps, type the GRASS command 
'''grass> d.what.rast'''

Move the cursor over the display; use the left mouse button to click on a gage point. The E and N and map category value of the point you clicked will be displayed on your terminal window. Right click to end the session.

If you are having trouble placing your mouse right on top of a gage point, it may be helpful to zoom in with the GRASS command
'''grass> d.zoom'''

Follow the on screen instructions using the mouse to zoom in on a gage or group of gages. Then use '''grass> d.what.rast''' to query the points.

NOTE: You want to find the E and N coordinates for an outlet that falls on the stream network in order to delineate the boundary of all area draining to that point. However, the gages may not fall exactly on the stream network, so you may need to adjust where you choose your E and N coordinates so the point you choose falls on the stream network as close to the gage as possible.
d.zoom resets the region to the area you are zoomed in on. Any additional functions
you perform after zooming in would only process the area you are zoomed in on. As you
may be zoomed in very tightly on a stream segment and the full area of the watershed
you want to capture may not be displayed, you should reset your region with: 
'''grass> g.region rast=hjadem'''

To redisplay the map at the full extent of the hjadem region, you could use: 
'''grass> d.redraw'''

Or to clear your monitor, use: 
'''grass> d.erase'''

==Create a watershed==
Once you have the location of an outlet (the E and N coordinates), you can generate the sub-basin from the drainage direction map created with r.watershed and the E and N coordinates you isolated with r.what.rast. 

'''G> r.water.outlet drainage=drain basin=new_basin_name easting=xxx northing=xxx'''

This will generate a watershed basin map (new_basin_name) from the drainage direction
map (drain) and put it in your personal mapset. This map will have a value of 1 everywhere inside the boundary, and a value of 0 everywhere that falls outside of new_basin_name (ie. the rest of the DEM).

Display this map: 
'''G> d.rast map=new_basin_name'''

NOTE: Remember, the set of coordinates you use represents the outlet point of the
watershed, and the watershed basin is all area upstream of that point that drains to that point. Therefore, if the point you choose is on a hill slope, the resulting map will only reflect the small sliver of land uphill that drains to that point. This may take several tries, so don't get frustrated!

Using the overlay option with a new map generated from an existing map 
When you create a new map that represents a portion of the extent of an
existing map, you may need to run the GRASS command r.support in order to set all null
values to transparent. For example, you would use r.support if you wanted to overlay
new_basin_name on top of the DEM so that all areas outside of the new sub- basin were
transparent, allowing the DEM underneath to show through. You may find the GRASS
command r.support helpful as you create new maps. r.support can only be run interactively.
To use it for the purpose of setting null values to transparent, accept the default (no) for
the first six questions, but answer yes to the last question ‘Do you want to delete null file
for map_name?’ Answer yes.

==Preparing spatial input data sets==
You have a DEM (hjadem) and have now created a basin (new_basin_name) map. However, RHESSys requires additional spatial data to form a complete landscape representation and establish connectivity between spatial units. One of the unique features of RHESSys is its hierarchical landscape representation. RHESSys partitions the landscape into a hierarchical spatial structure, where each level of the spatial hierarchy fully covers the spatial extent of the landscape. For example, stratum (vegetation) are processed within each patch, patches are contained within hillslopes and zones, which are units contained within the full basin. Each level of the hierarchy is defined as a particular object type with a set of storage (state) and flux variables, and an associated set of model parameters (default files).

Object type and associated processes:
* Basin - defines the drainage basin, full extent of location being modeled.
* Hillslope - defines areas which drain to a single point or stream reach.
* Zone - denotes areas of similar climate.
* Patch - soil moisture processes and carbon and nitrogen cycling.
* Stratum - vertical layers within a patch (ie. vegetation)

From the DEM you'll need to derive the following maps:
* Slope
* Aspect
* Basin
* Hillslope
* Patch
* Saturated soil hydraulic conductivity at the surface (Ksat0)
* Decay of hydraulic conductivity with depth (m)
*Stream network
*Roads

===Creating horizon maps===

RHESSys expects horizon values as sin(horizon angle). You will need to compute two horizon maps, one
for east, and one for west. In GRASS, you would do this with the commands

g> r.horizon -d elevin=<DEM> direction=0 horizon=horizon
g> r.horizon -d elevin=<DEM> direction=180 horizon=horizon

This will produce two maps, horizon_0, and horizon_180, where 0 is east and 180 is west. These maps are
the horizon in degrees though, so you will need to use mapcalc to create new maps with the sin of these
values.

g> r.mapcalc 'east_horizon = sin(horizon_0)'
g> r.mapcalc 'west_horizon = sin(horizon_180)'

These two maps will be referenced by your template file.

===Create slope and aspect maps===
To generate slope and aspect layers for the new_basin_name map from the DEM, give the
the input elevation map (el), and output names for both the slope and aspect maps.
For this exercise use the following: 
'''grass> r.slope.aspect el=hjadem slope=slope aspect=aspect'''

This will create 2 new maps in your personal mapset, slope and aspect. You can name
these maps whatever you want, but by convention, they are generally called slope and
aspect. As you created these for the full DEM, you may want to use demslope, etc….
If you were still zoomed in and did not reset your region to the full extent of the DEM
then you may want to give your slope and aspect maps an identifying extension.

Verify the maps are there with: 
'''grass> g.list type=rast mapset=your_userID'''
will list maps only in your personal mapset directory.

===Create hillslope and stream maps===
You will use a GRASS watershed basin analysis program to generate a set of maps used to delineate key spatial layers in RHESSys. RHESSys uses different spatial objects to model specific hydro-ecological processes. These objects form a hierarchical representation of the landscapes key objects. The hillslope and stream maps are necessary as they represent key landscape objects. The GRASS r.watershed program creates maps of watershed basins, hillslopes, flow accumulation, drainage direction, and stream segments within a DEM. You only want to create these maps for the new_basin_name portion of the DEM.

For this step, zoom in on the new_basin_name map fairly close, however, leave at
least one pixel width of space around the watershed. As d.zoom resets the region, it
allows you to work with only the portion of the map displayed as you create additional maps in this step. 
'''grass> d.zoom'''

Hillslopes are defined as land area draining either side of a stream reach in each sub-basin. Hillslopes are created by breaking up the watershed into sub basins associated with a particular stream reach. To generate a hillslope map and a stream map, you will use the r.watershed program (r.watershed was used to create the hjastreams map you viewed previously). This program can be run interactively or non-interactively. To run non-interactively (command line): 
'''grass> r.watershed el=hjadem t=100 ac=acc dr=drain ba=b100 ha=h100 stream=str100'''

The proceeding was an abbreviation of: 
'''grass> r.watershed elevation=hjadem threshold=100 accumulation=acc drainage=drain basin=b100 half.basin=h100 stream=str100'''

Where threshold sets the aggregation value, elevation is the input map, and the rest are output maps.

This will put several new maps in your PERMANENT mapset (you can check with g.list). You can name the output maps whatever you choose, this is simply the convention established by previous RHESSys users (h100 indicates hillslopes at a threshold of 100 cells, etc...). Threshold represents the minimum size of a sub-basin in cells, or overland flow units. Try experimenting with different threshold values (i.e. try additional thresholds at 50 and 200), then display the hillslope maps (in different monitors) to see the difference.

===Setting a mask===
In order to work with data that falls only inside of this new sub-basin area rather than working with the full extent of the DEM or region you currently have set (i.e. as a result of zooming), you must set a mask. Setting a mask 'ignores' those areas that fall outside of the designated mask area on all subsequent operations, blocking them from analysis. This program can only be run interactively.

Type the GRASS command: 
'''grass> r.mask'''

Choose option 2 'Identify a new mask'

You will be prompted to enter the name of a raster map layer 
'''grass> new_basin_name'''

You will be shown a listing of this map's categories, and asked to assign a value of "1" or "0" to each map category. Areas assigned category value "1" will become part of the mask's surface, while areas assigned category value "0" will become "no data" areas in the MASK file.

Hit enter to move your cursor to the second category and type 1 in the space (type 1 next to all non-zero categories), hit <Esc><Enter> as instructed at the bottom of the page. You will be returned to the option page where you will see listed at the top of the screen that the current mask is new_basin_name, enter to return to the GRASS prompt.

Now if you display the DEM you will only see the area of the DEM that falls inside the new_basin_name basin area. 
'''grass> d.rast map=hjadem'''

Now reset the region to the geographic boundaries of new_basin_name with the g.region zoom option (sets the current region settings to the smallest region encompassing all non-zero data in the named raster map layer):
'''grass> g.region raster=new_basin_name zoom=new_basin_name''' 
'''grass> d.redraw'''

You should now have a much closer view of the DEM for new_basin_name.

===Zones===

Zones denote areas of similar climate. Zones store climate variables such as radiation, temperature etc... Each zone is linked to an input climate station. Precipitation and temperature data, for example, from this station are modified based on zone elevation, slope and aspect relative to the climate station. Zone processing also generates climate data not available from climate station (i.e. zones will estimate radiation fluxes if they are not available). Numerous strategies exist to partition areas of similar climate. Elevation bands in a mountainous area, for example, are likely to denote similarity. Distribution of climate stations can also be used to define zone partitioning, where each zone defines the area associated with a particular climate station. For these exercises, you will not be creating a zone map, as meteorological data from 1 climate station is sufficient for this small watershed. In this instance, it
is best to use the same map for zones as you use for hillslopes.

===Ksat0, m, and roads===
You will now use the GRASS raster map layer data calculator to create additional maps required to run RHESSys. The maps you will create in this exercise are the basic maps required to run RHESSys. However, this GRASS command can also be used to perform many arithmetic functions involving one or several existing map layers to create new map layers. See the GRASS website for a list of arithmetic operators.

The GRASS command r.mapcalc is typed in the form: 
'''grass> r.mapcalc 'result = expression' '''

where result is the name of the new map you are creating and expression is the arithmetic
being performed. Use r.mapcalc to generate three additional maps needed by RHESSys. The m and Ksat0 maps define spatial patterns of two soil hydrologic parameters. For this exercise we will assume these parameters do not vary spatially and use the same value for the entire watershed.

Type the following GRASS commands to create maps for Ksat0, m, and roads: (the ' are deliberate characters) 
'''grass> r.mapcalc 'K = new_basin_name * 2' ''' 
'''grass> r.mapcalc 'm = new_basin_name * 0.12' ''' 
'''grass> r.mapcalc 'zero = 0' ''' (zero will be used as the road map as there are no roads in this watershed)

When you created new_basin_name, it was assigned a value of 1. The multiplication operator (*) was used to create a new map called K (Ksat0-saturated soil hydraulic conductivity at the surface) that covers the extent of this sub-basin, which will have a value of 2, and a new map called m (decay of hydraulic conductivity with depth) with a value of 0.12. You also created a road map equal to zero to indicate that there are no roads in this dataset. K and m should be initialized based on values for the soil type in your area of study (see website for soil type values).

===Patches===
The final map required for a basic RHESSys run is the patch map. Patches represent the smallest resolution spatial unit and define areas of similar soil moisture and land cover characteristics. Vertical soil moisture processing and soil biogeochemistry are modeled within each unit defined as a patch. Lateral transport of material and water occurs between patches, so patch definition must reflect drainage organization of the watershed. You have considerable flexibility in defining a patch structure; patches can be strictly grid-based (i.e. based on 30m DEM), or of arbitrary shape (reflecting the patterns of relevant variability within the landscape, i.e. wetness index, vegetation cover, and stream/road networks).

However, when defining a patch structure attention should be given to the landscape size due to the associated processing time. Most of the processing in RHESSYS – for patch and stratum processes – is done at the patch spatial level. These processes must be performed for each individual patch. Therefore, the more patches there are, the more processing that must be done. Choosing a smaller resolution spatial unit will increase the number of patches, therefore, increase total processing time for a simulation.

For this exercise, you will define the patch structure for new_map_name based on the 30 meter DEM. The GRASS command r.clump re-categorizes data in a raster map layer by grouping cells that form physically discrete areas into unique categories. 
'''grass> r.clump input=hjadem output=new_map_name.cl'''

By user defined convention, when a map is clumped the extension .cl is added to the map name to identify that the r.clump function has be done.

To look at the patch structure: 
'''grass> d.rast map=new_map_name.cl'''

===Stratum===

Strata define vertical, aspatial layers within the patch. Processes such as photosynthesis and transpiration are modeled at the stratum level. Strata usually have the same spatial structure as patches. So the patch (new_map_name.cl) map will also be used to define the stratum object.

You have now created all the maps necessary for RHESSys to define the landscape representation. For now, however, you can quit out of GRASS (G> quit) and work on the additional timeseries data sets required to run RHESSys.

===Carbon Stores===

==Developing timeseries data sets==
Climate
RHESSys requires daily climate inputs for precipitation, minimum and maximum air temperature. These climate inputs are linked to zones in the landscape representation by a base station ID affiliated with that zone. A single base station will typically serve multiple (or all) zones within the landscape. Each base station is described by a base station file and stored in the clim directory.

The tutorial data set included a base station file (w8_base) and 3 climate files (w8_daily.rain, w8_daily.tmin, w8_daily.tmax) for a small watershed (w8) in the HJA that you should have copied into your clim directory. Have a look at the base station file structure.

From the UNIX prompt: 
'''unix> more w8_base'''

Take note of the following content:

Line 1: 101 base_station_id.
This ID will be read by zones in the landscape to link it to the base station climate file.

Line 4: 485 z_coordinate.
Elevation (in meters) of meterological station where climate data was collected.

Line 11: ../clim/w8_daily daily_climate_prefix.
Tells the base station what daily precipitation and temperature files to read, and the directory they are in.

NOTE: if you were developing your own climate input files, you would edit this base station file to reflect your meteorological station elevation and daily climate prefix.

Each of the climate input files (precipitation, maximum temperature and minimum temperature) is contained in a separate file. RHESSys assumes that the climate input files associated with a base station are all named with the same prefix (i.e. w8_daily = daily climate inputs for w8). A filename extension specifying the kind of climate variable (ie. precipitation, maximum or minimum temperature) contained in each file is attached to the end of the prefix. The prefix is then given in the base station description file, directing it to read in all climate files with that prefix.

There are 3 required climate input files - precipitaiton, minimum and maximum daily temperature. (There are also a number of optional climate inputs. If optional climate sequences are not available/used, a process model within RHESSys will provide estimates of these variables. See the RHESSys website for more information.) RHESSys requires the climate files to be in a particular format:

Review the structure of these climate input files. The first line of each input time series file must give the starting date of the time series (Year Month Day Hour). Following the starting date, daily time series values are listed sequentially.

'''unix> more w8_daily.rain''' (daily precipitation in meters)
These are long files, to end viewing a file, type U> q.
'''unix> more w8_daily.tmax''' (daily maximum temperature °C)
'''unix> more w8_daily.tmin''' (daily minimum temperature °C)

Developing your own daily climate files may require some preprocessing in order to format the data so it can be read by RHESSys. Be sure to check for missing data and make sure data is in the correct units. The RHESSys website describes a process for dealing with missing data and formatting it for RHESSys. It is also a good idea to inspect a graph of your input time series data visually to check for abnormal spikes or unrealistic values such as negative precipitation events. You may need to use a statistical computation program such as R, S-Plus, SPSS, or Excel to fill in missing data.

A climate data file should only consist of the start date at the top, followed by 1 value for each day. When naming the files you can use any name you want for the beginning of the prefix (just make sure all three have the same prefix). However, by convention, the prefix should include the time period of the data (i.e. daily, to distinguish these from hourly time series inputs, an optional input type in RHESSys) followed by the extensions: .rain, .tmin, .tmax

NOTE: Depending on the program you use to save your data files, it may attach an additional file extension to the end of the file (such as .txt). When you bring the files into your UNIX clim directory, make sure to remove any file extensions.
Also, if you develop the files on a PC and transfer them to UNIX, you may need to run the converter dos2unix to convert from DOS text format to UNIX format - which will remove the ^M characters from the file. If you open one of the files with vi, you can see if the characters are present.

==Streamflow==
You will need observed streamflow data for calibration. As with climate, when creating your own streamflow files some preprocessing may be necessary to check for missing or abnormal data, and for formatting. When used in the calibration procedure (discussed in Module III) format for streamflow files is the same as for climate files. The Observed streamflow has been provided for w8 (obs.wy79_80dw8) for the exercises you will do in the next module.

RHESSys outputs streamflow in millimeters per day (streamflow normalized by basin area), so the observed streamflow must also be converted to millimeters per day. (RHESSys also aggregates output at a monthly timestep in the event you only have observed monthly streamflow.)

For example, the USGS uses cubic-feet per second (CFS) as their unit of measurement, so you would need to convert from CFS to mm/day. To convert from mean daily CFS to mm per day, you need to know the area of the watershed draining to the gage you have streamflow (Q) data for in square feet.

(If necessary, to convert area in hectares (ha) to square feet (sq.ft.), multiply ha by 107639.104169.)

To convert mean CFS to mm per day:

1. divide mean CFS by the basin area in sq.ft = Q ft/sec

2. multiply Q ft/sec by 86400 = Q ft/day

3. multiply Q ft/day by 304.8 = Q mm/day

Preparing input data sets

2010-09-28T23:42:30Z

Dgroulx:

The GRASS GIS program will be used to process and store your set of spatial data layers associated with a project. The latest GRASS build
can be downloaded at [http://grass.itc.it/ http://grass.itc.it].

==Set the geographic region==

A region refers to a geographic area with some defined boundaries, based on a specific map coordinate system and map projection. In GRASS, each region also has associated with it the specific east-west and north-south resolutions of its smallest units (rectangular units called "cells").

The region's boundaries are given as the northernmost, southernmost, easternmost, and westernmost points that define its extent. The north and south boundaries are commonly called northings, while the east and west boundaries are called eastings.

You need to set the geographic region for your personal mapset. For now, this will be the same as the DEM. Set the region with: 
'''grass> g.region rast=<dem>'''

To find out the settings of the current region: 
'''grass> g.region –p'''

This will tell you the projection, zone, datum, ellipsoid, N/S/E/W coordinates, resolution,
and number of rows and columns of your DEM.

==Start a display monitor and view a map==

To look at the DEM, start a monitor with the GRASS command: 
'''grass> d.mon start=x0'''

This will start a graphics display monitor called x0.
You can have up to 10 monitors open at once (each one must be started with
grass> d.mon start=x_); each must be assigned a different number, i.e. x0, x1, x2, etc...; when you have more than one monitor open, select one for use with the command: 
'''grass> d.mon select=x2'''

To display the raster map layer, type the GRASS command: 
'''grass> d.rast map=hjadem'''

To clear the monitor, type the GRASS command: 
'''grass> d.erase'''

==Defining a watershed boundary==
Rather than working with the full extent of the DEM (which probably contains areas outside of the watershed you are interested in) you can define the boundaries of a landscape that drain to a specific point (or outlet). You will use the GRASS watershed basin creation program (r.water.outlet) to define the boundaries for a sub-watershed within the HJ Andrews basin. First however, r.water.outlet requires a drainage direction map that must be created with the GRASS program r.watershed.

To create the drainage direction map, type the GRASS command: 
'''grass> r.watershed elevation=hjadem drainage=hja_drain'''

This traces the flow through the elevation model and creates a new raster map called drain in your personal mapset.

GRASS recognizes geographic coordinates as the Easting and Northing of each point across the landscape. To define the watershed boundaries associated with a particular outlet, you will need to identify the Easting (E) and Northing (N) of a point on the stream network.
For this exercise, you can experiment with picking any point you choose on the stream network, regardless if it is a gaged stream or not. The purpose of this exercise is simply to acquaint you with how to create a sub-watershed.

Generally, you will want to work with a watershed for which you have some measured information, such as streamflow, soil moisture, or LAI, so you have observed data to compare model results to. This is most often observed streamflow data, which is widely and readily available from many gaged streams. Therefore, you attempt to delineate the modeled watershed to match the real watershed draining to that gage. To identify the outlet point for a gaged stream, it is helpful to overlay a map of stream gages on the stream network if available. To do this, you will need to import the stream and gage maps provided with the tutorial data set into GRASS. At the beginning of this tutorial, you should have copied the ascii files hjagages.asc and hjastreams.asc into your grassdata directory.

==Importing files into grass==

To import ascii raster files into GRASS, direct input to the ascii map, give the resultant map an output name, and set null values to 0 (read working in GRASS and UNIX below): 
'''grass> r.in.ascii input=/full_path_name/hjagages.asc output=hjagages nv=0'''

'''grass> r.in.ascii input=/full_path_name/hjastreams.asc output=hjastreams nv=0'''

(GRASS supports many formats. For information on importing different formats, i.e. ARC-ASCII-GRID with r.in.arc, ESRI/E00 with m.in.e00, see the GRASS data import help webpage).

Display the maps, overlaying the gages on the streams, with: 
'''grass> d.rast map=hjastreams''' 
'''grass> d.rast -o map=hjagages'''

A map of the stream network overlain by the stream gages should be displayed in your monitor. Note the gages are very small points across the watershed and can be hard to see without zooming in, which will be discussed shortly.

This map illustrates gage locations throughout the HJA.

Identify an outlet point
To identify location information on either the stream or gage maps, type the GRASS command 
'''grass> d.what.rast'''

Move the cursor over the display; use the left mouse button to click on a gage point. The E and N and map category value of the point you clicked will be displayed on your terminal window. Right click to end the session.

If you are having trouble placing your mouse right on top of a gage point, it may be helpful to zoom in with the GRASS command
'''grass> d.zoom'''

Follow the on screen instructions using the mouse to zoom in on a gage or group of gages. Then use '''grass> d.what.rast''' to query the points.

NOTE: You want to find the E and N coordinates for an outlet that falls on the stream network in order to delineate the boundary of all area draining to that point. However, the gages may not fall exactly on the stream network, so you may need to adjust where you choose your E and N coordinates so the point you choose falls on the stream network as close to the gage as possible.
d.zoom resets the region to the area you are zoomed in on. Any additional functions
you perform after zooming in would only process the area you are zoomed in on. As you
may be zoomed in very tightly on a stream segment and the full area of the watershed
you want to capture may not be displayed, you should reset your region with: 
'''grass> g.region rast=hjadem'''

To redisplay the map at the full extent of the hjadem region, you could use: 
'''grass> d.redraw'''

Or to clear your monitor, use: 
'''grass> d.erase'''

==Create a watershed==
Once you have the location of an outlet (the E and N coordinates), you can generate the sub-basin from the drainage direction map created with r.watershed and the E and N coordinates you isolated with r.what.rast. 

'''G> r.water.outlet drainage=drain basin=new_basin_name easting=xxx northing=xxx'''

This will generate a watershed basin map (new_basin_name) from the drainage direction
map (drain) and put it in your personal mapset. This map will have a value of 1 everywhere inside the boundary, and a value of 0 everywhere that falls outside of new_basin_name (ie. the rest of the DEM).

Display this map: 
'''G> d.rast map=new_basin_name'''

NOTE: Remember, the set of coordinates you use represents the outlet point of the
watershed, and the watershed basin is all area upstream of that point that drains to that point. Therefore, if the point you choose is on a hill slope, the resulting map will only reflect the small sliver of land uphill that drains to that point. This may take several tries, so don't get frustrated!

Using the overlay option with a new map generated from an existing map 
When you create a new map that represents a portion of the extent of an
existing map, you may need to run the GRASS command r.support in order to set all null
values to transparent. For example, you would use r.support if you wanted to overlay
new_basin_name on top of the DEM so that all areas outside of the new sub- basin were
transparent, allowing the DEM underneath to show through. You may find the GRASS
command r.support helpful as you create new maps. r.support can only be run interactively.
To use it for the purpose of setting null values to transparent, accept the default (no) for
the first six questions, but answer yes to the last question ‘Do you want to delete null file
for map_name?’ Answer yes.

==Preparing spatial input data sets==
You have a DEM (hjadem) and have now created a basin (new_basin_name) map. However, RHESSys requires additional spatial data to form a complete landscape representation and establish connectivity between spatial units. One of the unique features of RHESSys is its hierarchical landscape representation. RHESSys partitions the landscape into a hierarchical spatial structure, where each level of the spatial hierarchy fully covers the spatial extent of the landscape. For example, stratum (vegetation) are processed within each patch, patches are contained within hillslopes and zones, which are units contained within the full basin. Each level of the hierarchy is defined as a particular object type with a set of storage (state) and flux variables, and an associated set of model parameters (default files).

Object type and associated processes:
* Basin - defines the drainage basin, full extent of location being modeled.
* Hillslope - defines areas which drain to a single point or stream reach.
* Zone - denotes areas of similar climate.
* Patch - soil moisture processes and carbon and nitrogen cycling.
* Stratum - vertical layers within a patch (ie. vegetation)

From the DEM you'll need to derive the following maps:
* Slope
* Aspect
* Basin
* Hillslope
* Patch
* Saturated soil hydraulic conductivity at the surface (Ksat0)
* Decay of hydraulic conductivity with depth (m)
*Stream network
*Roads

===Creating horizon maps===

===Create slope and aspect maps===
To generate slope and aspect layers for the new_basin_name map from the DEM, give the
the input elevation map (el), and output names for both the slope and aspect maps.
For this exercise use the following: 
'''grass> r.slope.aspect el=hjadem slope=slope aspect=aspect'''

This will create 2 new maps in your personal mapset, slope and aspect. You can name
these maps whatever you want, but by convention, they are generally called slope and
aspect. As you created these for the full DEM, you may want to use demslope, etc….
If you were still zoomed in and did not reset your region to the full extent of the DEM
then you may want to give your slope and aspect maps an identifying extension.

Verify the maps are there with: 
'''grass> g.list type=rast mapset=your_userID'''
will list maps only in your personal mapset directory.

===Create hillslope and stream maps===
You will use a GRASS watershed basin analysis program to generate a set of maps used to delineate key spatial layers in RHESSys. RHESSys uses different spatial objects to model specific hydro-ecological processes. These objects form a hierarchical representation of the landscapes key objects. The hillslope and stream maps are necessary as they represent key landscape objects. The GRASS r.watershed program creates maps of watershed basins, hillslopes, flow accumulation, drainage direction, and stream segments within a DEM. You only want to create these maps for the new_basin_name portion of the DEM.

For this step, zoom in on the new_basin_name map fairly close, however, leave at
least one pixel width of space around the watershed. As d.zoom resets the region, it
allows you to work with only the portion of the map displayed as you create additional maps in this step. 
'''grass> d.zoom'''

Hillslopes are defined as land area draining either side of a stream reach in each sub-basin. Hillslopes are created by breaking up the watershed into sub basins associated with a particular stream reach. To generate a hillslope map and a stream map, you will use the r.watershed program (r.watershed was used to create the hjastreams map you viewed previously). This program can be run interactively or non-interactively. To run non-interactively (command line): 
'''grass> r.watershed el=hjadem t=100 ac=acc dr=drain ba=b100 ha=h100 stream=str100'''

The proceeding was an abbreviation of: 
'''grass> r.watershed elevation=hjadem threshold=100 accumulation=acc drainage=drain basin=b100 half.basin=h100 stream=str100'''

Where threshold sets the aggregation value, elevation is the input map, and the rest are output maps.

This will put several new maps in your PERMANENT mapset (you can check with g.list). You can name the output maps whatever you choose, this is simply the convention established by previous RHESSys users (h100 indicates hillslopes at a threshold of 100 cells, etc...). Threshold represents the minimum size of a sub-basin in cells, or overland flow units. Try experimenting with different threshold values (i.e. try additional thresholds at 50 and 200), then display the hillslope maps (in different monitors) to see the difference.

===Setting a mask===
In order to work with data that falls only inside of this new sub-basin area rather than working with the full extent of the DEM or region you currently have set (i.e. as a result of zooming), you must set a mask. Setting a mask 'ignores' those areas that fall outside of the designated mask area on all subsequent operations, blocking them from analysis. This program can only be run interactively.

Type the GRASS command: 
'''grass> r.mask'''

Choose option 2 'Identify a new mask'

You will be prompted to enter the name of a raster map layer 
'''grass> new_basin_name'''

You will be shown a listing of this map's categories, and asked to assign a value of "1" or "0" to each map category. Areas assigned category value "1" will become part of the mask's surface, while areas assigned category value "0" will become "no data" areas in the MASK file.

Hit enter to move your cursor to the second category and type 1 in the space (type 1 next to all non-zero categories), hit <Esc><Enter> as instructed at the bottom of the page. You will be returned to the option page where you will see listed at the top of the screen that the current mask is new_basin_name, enter to return to the GRASS prompt.

Now if you display the DEM you will only see the area of the DEM that falls inside the new_basin_name basin area. 
'''grass> d.rast map=hjadem'''

Now reset the region to the geographic boundaries of new_basin_name with the g.region zoom option (sets the current region settings to the smallest region encompassing all non-zero data in the named raster map layer):
'''grass> g.region raster=new_basin_name zoom=new_basin_name''' 
'''grass> d.redraw'''

You should now have a much closer view of the DEM for new_basin_name.

===Zones===

Zones denote areas of similar climate. Zones store climate variables such as radiation, temperature etc... Each zone is linked to an input climate station. Precipitation and temperature data, for example, from this station are modified based on zone elevation, slope and aspect relative to the climate station. Zone processing also generates climate data not available from climate station (i.e. zones will estimate radiation fluxes if they are not available). Numerous strategies exist to partition areas of similar climate. Elevation bands in a mountainous area, for example, are likely to denote similarity. Distribution of climate stations can also be used to define zone partitioning, where each zone defines the area associated with a particular climate station. For these exercises, you will not be creating a zone map, as meteorological data from 1 climate station is sufficient for this small watershed. In this instance, it
is best to use the same map for zones as you use for hillslopes.

===Ksat0, m, and roads===
You will now use the GRASS raster map layer data calculator to create additional maps required to run RHESSys. The maps you will create in this exercise are the basic maps required to run RHESSys. However, this GRASS command can also be used to perform many arithmetic functions involving one or several existing map layers to create new map layers. See the GRASS website for a list of arithmetic operators.

The GRASS command r.mapcalc is typed in the form: 
'''grass> r.mapcalc 'result = expression' '''

where result is the name of the new map you are creating and expression is the arithmetic
being performed. Use r.mapcalc to generate three additional maps needed by RHESSys. The m and Ksat0 maps define spatial patterns of two soil hydrologic parameters. For this exercise we will assume these parameters do not vary spatially and use the same value for the entire watershed.

Type the following GRASS commands to create maps for Ksat0, m, and roads: (the ' are deliberate characters) 
'''grass> r.mapcalc 'K = new_basin_name * 2' ''' 
'''grass> r.mapcalc 'm = new_basin_name * 0.12' ''' 
'''grass> r.mapcalc 'zero = 0' ''' (zero will be used as the road map as there are no roads in this watershed)

When you created new_basin_name, it was assigned a value of 1. The multiplication operator (*) was used to create a new map called K (Ksat0-saturated soil hydraulic conductivity at the surface) that covers the extent of this sub-basin, which will have a value of 2, and a new map called m (decay of hydraulic conductivity with depth) with a value of 0.12. You also created a road map equal to zero to indicate that there are no roads in this dataset. K and m should be initialized based on values for the soil type in your area of study (see website for soil type values).

===Patches===
The final map required for a basic RHESSys run is the patch map. Patches represent the smallest resolution spatial unit and define areas of similar soil moisture and land cover characteristics. Vertical soil moisture processing and soil biogeochemistry are modeled within each unit defined as a patch. Lateral transport of material and water occurs between patches, so patch definition must reflect drainage organization of the watershed. You have considerable flexibility in defining a patch structure; patches can be strictly grid-based (i.e. based on 30m DEM), or of arbitrary shape (reflecting the patterns of relevant variability within the landscape, i.e. wetness index, vegetation cover, and stream/road networks).

However, when defining a patch structure attention should be given to the landscape size due to the associated processing time. Most of the processing in RHESSYS – for patch and stratum processes – is done at the patch spatial level. These processes must be performed for each individual patch. Therefore, the more patches there are, the more processing that must be done. Choosing a smaller resolution spatial unit will increase the number of patches, therefore, increase total processing time for a simulation.

For this exercise, you will define the patch structure for new_map_name based on the 30 meter DEM. The GRASS command r.clump re-categorizes data in a raster map layer by grouping cells that form physically discrete areas into unique categories. 
'''grass> r.clump input=hjadem output=new_map_name.cl'''

By user defined convention, when a map is clumped the extension .cl is added to the map name to identify that the r.clump function has be done.

To look at the patch structure: 
'''grass> d.rast map=new_map_name.cl'''

===Stratum===

Strata define vertical, aspatial layers within the patch. Processes such as photosynthesis and transpiration are modeled at the stratum level. Strata usually have the same spatial structure as patches. So the patch (new_map_name.cl) map will also be used to define the stratum object.

You have now created all the maps necessary for RHESSys to define the landscape representation. For now, however, you can quit out of GRASS (G> quit) and work on the additional timeseries data sets required to run RHESSys.

===Carbon Stores===

==Developing timeseries data sets==
Climate
RHESSys requires daily climate inputs for precipitation, minimum and maximum air temperature. These climate inputs are linked to zones in the landscape representation by a base station ID affiliated with that zone. A single base station will typically serve multiple (or all) zones within the landscape. Each base station is described by a base station file and stored in the clim directory.

The tutorial data set included a base station file (w8_base) and 3 climate files (w8_daily.rain, w8_daily.tmin, w8_daily.tmax) for a small watershed (w8) in the HJA that you should have copied into your clim directory. Have a look at the base station file structure.

From the UNIX prompt: 
'''unix> more w8_base'''

Take note of the following content:

Line 1: 101 base_station_id.
This ID will be read by zones in the landscape to link it to the base station climate file.

Line 4: 485 z_coordinate.
Elevation (in meters) of meterological station where climate data was collected.

Line 11: ../clim/w8_daily daily_climate_prefix.
Tells the base station what daily precipitation and temperature files to read, and the directory they are in.

NOTE: if you were developing your own climate input files, you would edit this base station file to reflect your meteorological station elevation and daily climate prefix.

Each of the climate input files (precipitation, maximum temperature and minimum temperature) is contained in a separate file. RHESSys assumes that the climate input files associated with a base station are all named with the same prefix (i.e. w8_daily = daily climate inputs for w8). A filename extension specifying the kind of climate variable (ie. precipitation, maximum or minimum temperature) contained in each file is attached to the end of the prefix. The prefix is then given in the base station description file, directing it to read in all climate files with that prefix.

There are 3 required climate input files - precipitaiton, minimum and maximum daily temperature. (There are also a number of optional climate inputs. If optional climate sequences are not available/used, a process model within RHESSys will provide estimates of these variables. See the RHESSys website for more information.) RHESSys requires the climate files to be in a particular format:

Review the structure of these climate input files. The first line of each input time series file must give the starting date of the time series (Year Month Day Hour). Following the starting date, daily time series values are listed sequentially.

'''unix> more w8_daily.rain''' (daily precipitation in meters)
These are long files, to end viewing a file, type U> q.
'''unix> more w8_daily.tmax''' (daily maximum temperature °C)
'''unix> more w8_daily.tmin''' (daily minimum temperature °C)

Developing your own daily climate files may require some preprocessing in order to format the data so it can be read by RHESSys. Be sure to check for missing data and make sure data is in the correct units. The RHESSys website describes a process for dealing with missing data and formatting it for RHESSys. It is also a good idea to inspect a graph of your input time series data visually to check for abnormal spikes or unrealistic values such as negative precipitation events. You may need to use a statistical computation program such as R, S-Plus, SPSS, or Excel to fill in missing data.

A climate data file should only consist of the start date at the top, followed by 1 value for each day. When naming the files you can use any name you want for the beginning of the prefix (just make sure all three have the same prefix). However, by convention, the prefix should include the time period of the data (i.e. daily, to distinguish these from hourly time series inputs, an optional input type in RHESSys) followed by the extensions: .rain, .tmin, .tmax

NOTE: Depending on the program you use to save your data files, it may attach an additional file extension to the end of the file (such as .txt). When you bring the files into your UNIX clim directory, make sure to remove any file extensions.
Also, if you develop the files on a PC and transfer them to UNIX, you may need to run the converter dos2unix to convert from DOS text format to UNIX format - which will remove the ^M characters from the file. If you open one of the files with vi, you can see if the characters are present.

==Streamflow==
You will need observed streamflow data for calibration. As with climate, when creating your own streamflow files some preprocessing may be necessary to check for missing or abnormal data, and for formatting. When used in the calibration procedure (discussed in Module III) format for streamflow files is the same as for climate files. The Observed streamflow has been provided for w8 (obs.wy79_80dw8) for the exercises you will do in the next module.

RHESSys outputs streamflow in millimeters per day (streamflow normalized by basin area), so the observed streamflow must also be converted to millimeters per day. (RHESSys also aggregates output at a monthly timestep in the event you only have observed monthly streamflow.)

For example, the USGS uses cubic-feet per second (CFS) as their unit of measurement, so you would need to convert from CFS to mm/day. To convert from mean daily CFS to mm per day, you need to know the area of the watershed draining to the gage you have streamflow (Q) data for in square feet.

(If necessary, to convert area in hectares (ha) to square feet (sq.ft.), multiply ha by 107639.104169.)

To convert mean CFS to mm per day:

1. divide mean CFS by the basin area in sq.ft = Q ft/sec

2. multiply Q ft/sec by 86400 = Q ft/day

3. multiply Q ft/day by 304.8 = Q mm/day

Strata

2010-09-24T22:49:18Z

Dgroulx:

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Variable Name'''
| align="center" style="background:#f0f0f0;"|'''Description'''
| align="center" style="background:#f0f0f0;"|'''Units'''
|-
| stratum_default_ID||Identifier used by stratum objects to indicate their stratum default files||unique value for each default file
|-
| K_absorptance||Direct radiation absorption coefficient||range (0 - 1)
|-
| K_reflectance||Direct radiation reflection coefficient i.e albedo||range (0 - 1)
|-
| K_transmittance||Direct radiation transmittance coefficient||range (0 - 1)
|-
| PAR_absorptance||PAR radiation absorption coefficient||range (0 - 1)
|-
| PAR_reflectance||PAR radiation reflection coefficient i.e albedo||range (0 - 1)
|-
| PAR_transmittance||PAR radiation transmittance coefficient||range (0 - 1)
|-
| epc.ext_coef||Canopy light extinction coefficient||range (0-1)
|-
| specific_rain_capacity||Intercepted rain storage capacity per pai||metres / LAI
|-
| specific_snow_capacity||Intercepted snow storage capacity per pai||metres / LAI
|-
| wind_attenuation_coef||Wind speed attenuation through canopy (exponential decay)||1/metres
|-
| ustar_overu||If u*/u ratio is available for aerodynamic conductance computation the use; otherwise set to -999.9||(metres/s) / (metres/s)
|-
| mrc.q10||Q10 for maintenance respiration||dimensionless
|-
| mrc.per_N||Maintainance respiration per unit nitrogen||Kg C / kg N / day
|-
| epc.gr_perc||Percent of new carbon allocation that is lost to growth respiration||range (0 - 1)
|-
| lai_stomatal_fraction||Stomatal fraction||range (0 - 1)
|-
| epc.flnr||Ration Leaf nitrogen in Rubisco to leaf nitrogen||Kg / kg
|-
| epc.ppfd_coef||Shape parameter for APAR / conductance hyperbola curve||s/metres2/micromol
|-
| epc.topt||Optimum air temperature for stomatal conductance||º C
|-
| epc.tmax||Maximum air temperature for stomatal conductance||º C
|-
| epc.tcoef||Coefficient of temperature curve for stomatal conductance||dimensionless
|-
| epc.psi_open||Leaf water potential for full stomatal conductance||Mpa
|-
| epc.psi_close||Leaf water potential for complete stomatal closure||Mpa
|-
| epc.vpd_open||Vapour pressure deficit for full stomatal conductance||Pa
|-
| epc.vpd_close||Vapour pressure deficit for complete stomatal closure||Pa
|-
| epc.gl_smax||Maximum stomatal conductance||metres / s
|-
| epc.gl_c||Leaf-scale cuticular conductance||metres/ s
|-
| gsurf_slope||Slope of nonvascular conductance vs storage curve - use 0 for vascular strata||dimensionless
|-
| gsurf_intercept||Intercept for nonvascular conductance vs storage curve -||dimensionless
|-
| epc.veg_type||Vegetation type||TREE or GRASS
|-
| epc.phenology_flag||Phenology flag (currently must be static, not modelled)||STATIC or DYNAMIC
|-
| epc.phenology_type||Phenology type||EVERGREEN or DECIDUOUS
|-
| epc.max_lai||Maximum leaf area||meters2 / kg C
|-
| epc.proj_sla||Specific leaf area||meters2 / kg C
|-
| epc.lai_ratio||All-sided LAI / one-sided LAI ratio||dimensionless
|-
| epc.proj_swa||Specific wood area (i.e pai per kg C of stem biomass)||1/kg C
|-
| epc.leaf_turnover||Annual leaf turnover fraction||range (0-1)
|-
| epc.day_leafon||Start of growing season||range(1-365)
|-
| epc.day_leafoff||Beginning of leaf drop||range(1-365)
|-
| epc.ndays_expand||Number of days for leaf out period||# days
|-
| epc.ndays_litfall||Number of days for litterfall perio||# days
|-
| epc.leaf_cn||Carbon:nitrogen ratio of leaves||Kg C / kg N
|-
| epc.leaflitr_cn||Carbon:nitrogen ratio of leaf litter after translocation||Kg C / kg N
|-
| min_heat_capacity||Maximum stratum heat capacity - 0 will ignore heat flux model||J/m3/ºK
|-
| max_heat_capacity||Minimum stratum heat capacity - 0 will ignore heat flux model||J/m3/ ºK
|-
| epc.allocation_flag||Allocation flag (if static, canopy will not grow, as if using V 4.6)||STATIC or DYNAMIC
|-
| epc.storage_transfer_prop||Amount of this year\'s annual allocation to be used - value < 1.0 will maintain a carbon store for use in bad years||range (0-1)
|-
| epc.froot_turnover||Annual fine root turnover fraction (percent carbon per year)||range (0-1)
|}

Command Line Options

2010-09-03T16:51:03Z

Dgroulx:

Incorporating LANDSAT data into GRASS

2010-09-03T16:49:32Z

Dgroulx: /* Getting LANDSAT Data */

==Getting LANDSAT Data==
Landsat imagery can be downloaded using the [http://glovis.usgs.gov/ USGS Glovis website]
From inside grass, use the r.in.gdal program to import the TIF files into your GRASS location.

==Generating LAI maps from LANDSAT DATA==

==Running lairead==

Generating RHESSys input files

2010-08-03T17:30:31Z

Dgroulx: /* Tecfiles */

==Default files==
The default files describe characteristics of the variables associated with each object (level) of the spatial hierarchy. The default parameters are assigned values that stay constant through time and describe the performance of the parameters associated with an object. For example, the patch object would have default files associated with it that describe the characteristics of the soil type identified in that patch. Such parameter files are associated with each level of the spatial hierarchy. A library of commonly used parameter files assigned to specific soil, vegetation, and land use types have been developed, based on extensive literature research.

The basin and hillslope default file structures contain no parameters beyond the default file identifier. The default identifier maintains consistency of every object from basin through strata that has that basin/hillslope default identifier.

The zone default file contains atmospheric parameters associated with zone objects. The values provided in the standard zone default file are likely to be reasonably invariant for many environments, therefore, is a good first source in the absence of atmospheric research specific to a study site.

The soil and land use default files associated with the patch object address the routing and input of water at the patch level. Soil default files describe characteristics of particular soil types. Land use default files account for additional nitrogen and water inputs from developed areas.

The stratum default files describe characteristics of different vegetation types and associated processes such as carbon allocation, radiation interception, respiration, stomatal physiology, phenology, etc...

A set of default files has been provided with the tutorial exercise data, which you should have copied into your defs directory. Open a few of these default files to see the structure and content.

'''unix> more veg_conifer.def''' 
'''unix> more sandyloam.def'''

Notice the first line for each default file assigns a default_ID. Every parameter type has a
numerical identification, which corresponds to the ID's assigned in the GIS spatial layers,
and is defined within the levels of the landscape representation. For details on the file
structure and variable descriptions, see the [[Default files]] page.

==Worldfiles==
The worldfile defines the landscape representation within RHESSys. It is based on the hierarchical structure that describes each spatial level containing progressively finer units. The worldfile is generated with a GRASS interface program that references the input maps and a text document defining initial state variables (starting point for each variable). Within the worldfile, each spatial level is associated with the following items:

Identifier: each instance within a level is assigned an ID based on the map used to partition that level.

State Variables: values for stores and fluxes organized at each spatial level are initialized at the start of the simulation, typically changing as the simulation runs (ie. saturation deficit within the patch level)

A link to a climate station: link between the zone level and a particular climate station and the climate time series input information.

Because the worldfile for a complex landscape may contain hundreds of lines, a program called grass2world (g2w) is used to automatically generate the worldfile from spatial data layers within GRASS GIS. To create a worldfile with g2w, you need a text file (by convention, beginning with the prefix template) to be in your home working directory. The template is essentially a set of instructions that tells the GRASS interface program (g2w) how to create the initial values for each of the state variables in a spatial object at each level of the spatial hierarchy. Within the template file are initial values for variables such as carbon and nitrogen stores, or references to images (maps) that hold those values. grass2world expands the template file to assign values for every basin, hillslope, zone, patch, and stratum within the geographic extent of your modeled landscape. grass2world must be run from inside the GRASS GIS system. The program will look for the template file you designate on the command line in the calling directory, along with the associated maps in the GRASS database.

===Template===
There are 3 things that need to be initialized in the template:

1. Definition of the spatial layers 
Spatial definition of the world objects (ie. basin, hillslope, zone, patch, and stratum) can be identified by looking at the lines beginning with an underscore (ie. _basin). Each level in the spatial hierarchy is defined using a raster map (which you created in GRASS in module I). A specific format must be used to define the various partitions as follows: 
spatial_level map_name extent
Spatial level indicates the level of the spatial heirarchy, and map_name identifies the GRASS raster map which defines the spatial partition. Extent specifies the number of vertical layers defined at that particular level of the spatial hierarchy. The extent parameter allows for non-spatial partitioning at a given level in the spatial hierarchy. The current version of RHESSys only allows non-spatial partitioning to occur at the stratum level (see special module for understory/overstory). Thus, for all levels other than canopy stratum, extent should be equal to 1.

2. Initialization of state variables 
Generally, there are two ways to initialize state variables: assign a constant value, or use a map to assign values. This allows soil or vegetation to either be of one homogenous coverage or vary throughout the landscape, in which case you would reference a map containing multiple ID's. The default ID's used to identify soil and vegetation types in a map correspond to the ID's in the default files. The format for variables in the template is as follows:

Variable_name Function Constant_Value/Map

A. Assign a constant value
Example: soil_default_ID value 3.0
(variable_name) (function) (constant_value)

Assigning a constant value of 3 (the default ID for sandyloam) to the variable soil_default_id within the _patch level would indicate a constant soil type (sandyloam) across the landscape.

B. Use a map to assign values
Example: soil_default_ID mode variable_soils
(variable_name) (function) (map)

The map variable_soils is a map of soils that vary across the landscape. The function mode
takes the modal values from the map used. There are different ways to use maps (mode,
averages, with an equation – see website for more information). Note that for map ID's with variables that should not be averaged, mode must be used.

3. Assigning default ID's and base-stations
The beginning (header) of the template file lists the default and climate station files that will be used to describe the parameters associated with the world objects. Each level of the spatial hierarchy (basin, hillslope, zone, patch, and stratum) has default files associated with it. A climate base station that links to the climate data files must also be listed. The template format lists the number of default files that correspond to a given variable (i.e. number of soil or vegetation types), as well as the number of climate base stations, followed by the location and name of the default file or base station file.

Climate inputs are linked to particular zones by the climate station ID affiliated with that zone. A single climate station (or base station) will typically serve multiple zones within the landscape.

See the attached annotated template at the end of this module for further description of the template structure and content (under construction – I will distribute soon!). It denotes the most commonly edited lines within the template.

The following exercises will take you through editing the fields most commonly edited in the template file, and creating a worldfile.

==Editing the Template==

If you have not already done so, copy the template file to your working directory (contained in grassdata/templates), then open it for editing:

'''unix> vi template'''

If necessary, edit the header by directing the default and climate base station files to the correct path and file names. For this exercise, change the default file patch.def to sandyloam.def to change the soil type default file that RHESSys will look for.

Note the format of the line: ../defs/patch.def
This is the format that will be listed at the top of the worldfile, after g2w uses the template information to create the expanded worldfile.
UNIX format is used to direct RHESSys back one directory relative to where it is being run
from (which will be the scripts directory), into the defs directory, and to read patch.def.

Edit each level of the spatial hierarchy (using the same process of vi commands described above) to correspond with the appropriate map you created in module I (don't worry about extent for now, for this exercise extent should be left at 1 for all layers). For example, if you are using the w8 mapset, you would edit as follows:
<pre>
_world w8basin 1
_basin w8basin 1
_hillslope h100.w8 1
_zone h100.w8 1
_patch w8dem.cl 1
_stratum w8dem.cl 1
</pre>
Within each of the basin, hillslope, zone, and patch levels, edit the z variable to correspond to the DEM map.
Template format: z aver hjadem (average of the DEM at that level)

Within the zone and patch levels, edit the slope variable to correspond to the slope map. Template format: slope aver slope (uses the average Slope)

Within the zone level edit the aspect variable to correspond to the aspect map. Template format: aspect spavg aspect slope (takes the spherical average)

For this exercise, you will only use single values for soil and vegetation across the landscape (i.e. homogeneous soil type). Within the patch level, edit the soil_default_id from 1.0 (default ID used for a general soil type) to 3.0 (default ID assigned to sandyloam).

Be sure to save your changes before quitting.

You can save the template with any extension name you choose. This should be something to identify it, such as template.w8.

Creating the worldfile
You are now ready to run Grass2World, which must be run from within GRASS. Start GRASS and make sure you have the correct LOCATION, MAPSET and DATABASE set.

Make sure you have the appropriate mask set for the watershed you are creating the worldfile for (i.e. w8 or the watershed you created)

'''grass> r.mask'''

At the GRASS prompt, type the command:

'''grass> g2w -w new_worldfile_name -t template_name'''

This will create a worldfile in your working directory (the directory you are currently in) with the output name you indicated on the gw2 command line. By convention, all worldfiles should begin with the prefix world to identify the file as a worldfile. You can use any name you want after the prefix world, however, it should be a name representative of its location, structure, etc... For this exercise I suggest calling it world.tutorial.

Move the worldfile into your worldfiles directory.

==Flowtables==
The flowtable is only necessary if routing is going to be incorporated into the model. The flowtable describes connectivity between patches within a hillslope. A GRASS interface program (cf9) generates the flowtable from the set of images that describe the landscape partitioning, which must correspond with the images used to generate the spatial object hierarchy in the worldfile. cf9 determines how each patch routes water and nutrients, and assigns an effective gradient and transmissivity for each patch, which is used to model subsurface throughflow and overland flow routing.

cf9 uses GRASS raster images to create the flowtable.

Start GRASS

To create the flowtable, at the GRASS prompt type the command:

'''grass> cf9 output=<output filename> template=<worldfile template name> stream=<> road=<> dem=<> slope=<>
'''

where the brackets are filled with the name of the appropriate raster map. cf9 has several additional options,
but these are the required ones. Note that cf9 will pull the name of the basin, hillslope, patch, and zone rasters from the template.
A file name <output>_flow_table.dat will be written to your working directory. Rename this file to prevent overwriting it by subsequent calls to cf9. By convention, flowtables should start with the prefix flow followed by a name representing the study area, ie. flow.w8.
For this exercise, I suggest calling it flow.tutorial.

Move the flowtable to your flowtables directory.

Open the flowtable to look at the structure. The very first line, which is one number, lists the number of patches in the landscape representation. The flow table format lists the patch, zone, and hillslope ID's, followed by X, Y, and Z centroid information, accumulated area, land type, a parameter that integrates the effect of slope boundary width and soil transmissivity, and the number of adjacent patches. Underneath each individual patch are the patch, zone, and hill ID's for the adjacent patches which that patch flow into and a number that indicates the proportion of flow that will be routed to that patch.

==Tecfiles==
RHESSys is structured as an event driven simulation, where most of the process modeling occurs between events. The TEC, or Temporal Event Control file, tells RHESSys when certain events occur. An event may be a redefinition of the strata (ie. removal of vegetation due to fire), or redefinition of the world (ie. in the event of development), or when to start generating output. For this basic exercise, the only temporal event will be a printing event. These events are used to specify printing at an hourly, daily, monthly, or yearly timestep. The tecfile does not specify the level of processing or spatial aggregation (ie. average basin conditions, or the condition of a single hillslope, patch, or stratum) for the output. These options are addressed when you run a simulation and will be explained in module 3. Rather, the tecfile tells RHESSys when something (ie. printing out results) should occur, and how often (ie. daily or monthly) it should occur.

RHESSys has more than 100 state variables that can be looked at. Different command line options in combination with different printing TEC events (tecfile) produce output files with specific variables aggregated to specific spatial/temporal scales. Be sure to consider what type of output you are interested in, as each combination of tecfile and command line options outputs different variables (a list of output file headings and their units is listed at [[Temporal Event Control files]]).

For example, if you are interested in average basin conditions, the outputs are different for daily basin, daily basin growth, monthly basin, and yearly basin output.

Tecfile formatting:
# The TEC file is created in a text editor (such as VI)
# Events must be listed in order of execution
# Only one event per line is allowed, no blank lines are allowed
# The format for events in the TEC file is as follows: Year Month Day Hour Printing_event
When executing several printing events that start on the same
day, the events must be sequential. Two events cannot be
scheduled to happen at the same time. Therfore, if you have
two printing events scheduled on the same day, make the first
printing event start on hour 1, the second on hour 2, etc...

Create a tecfile with the text editor VI
'''unix> vi tec.tutorial''' (insert the following text (i) and save it
to the new file (wq))

<pre>
1979 10 1 2 print_daily_growth_on
1979 10 1 3 print_monthly_on
<pre>
By convention, all tecfiles should begin with the prefix tec
followed by a name pertaining to your project or task.

A list of other TEC event options is available on the RHESSys website.

Generating RHESSys input files

2010-08-03T17:29:43Z

Dgroulx: /* Tecfiles */

==Default files==
The default files describe characteristics of the variables associated with each object (level) of the spatial hierarchy. The default parameters are assigned values that stay constant through time and describe the performance of the parameters associated with an object. For example, the patch object would have default files associated with it that describe the characteristics of the soil type identified in that patch. Such parameter files are associated with each level of the spatial hierarchy. A library of commonly used parameter files assigned to specific soil, vegetation, and land use types have been developed, based on extensive literature research.

The basin and hillslope default file structures contain no parameters beyond the default file identifier. The default identifier maintains consistency of every object from basin through strata that has that basin/hillslope default identifier.

The zone default file contains atmospheric parameters associated with zone objects. The values provided in the standard zone default file are likely to be reasonably invariant for many environments, therefore, is a good first source in the absence of atmospheric research specific to a study site.

The soil and land use default files associated with the patch object address the routing and input of water at the patch level. Soil default files describe characteristics of particular soil types. Land use default files account for additional nitrogen and water inputs from developed areas.

The stratum default files describe characteristics of different vegetation types and associated processes such as carbon allocation, radiation interception, respiration, stomatal physiology, phenology, etc...

A set of default files has been provided with the tutorial exercise data, which you should have copied into your defs directory. Open a few of these default files to see the structure and content.

'''unix> more veg_conifer.def''' 
'''unix> more sandyloam.def'''

Notice the first line for each default file assigns a default_ID. Every parameter type has a
numerical identification, which corresponds to the ID's assigned in the GIS spatial layers,
and is defined within the levels of the landscape representation. For details on the file
structure and variable descriptions, see the [[Default files]] page.

==Worldfiles==
The worldfile defines the landscape representation within RHESSys. It is based on the hierarchical structure that describes each spatial level containing progressively finer units. The worldfile is generated with a GRASS interface program that references the input maps and a text document defining initial state variables (starting point for each variable). Within the worldfile, each spatial level is associated with the following items:

Identifier: each instance within a level is assigned an ID based on the map used to partition that level.

State Variables: values for stores and fluxes organized at each spatial level are initialized at the start of the simulation, typically changing as the simulation runs (ie. saturation deficit within the patch level)

A link to a climate station: link between the zone level and a particular climate station and the climate time series input information.

Because the worldfile for a complex landscape may contain hundreds of lines, a program called grass2world (g2w) is used to automatically generate the worldfile from spatial data layers within GRASS GIS. To create a worldfile with g2w, you need a text file (by convention, beginning with the prefix template) to be in your home working directory. The template is essentially a set of instructions that tells the GRASS interface program (g2w) how to create the initial values for each of the state variables in a spatial object at each level of the spatial hierarchy. Within the template file are initial values for variables such as carbon and nitrogen stores, or references to images (maps) that hold those values. grass2world expands the template file to assign values for every basin, hillslope, zone, patch, and stratum within the geographic extent of your modeled landscape. grass2world must be run from inside the GRASS GIS system. The program will look for the template file you designate on the command line in the calling directory, along with the associated maps in the GRASS database.

===Template===
There are 3 things that need to be initialized in the template:

1. Definition of the spatial layers 
Spatial definition of the world objects (ie. basin, hillslope, zone, patch, and stratum) can be identified by looking at the lines beginning with an underscore (ie. _basin). Each level in the spatial hierarchy is defined using a raster map (which you created in GRASS in module I). A specific format must be used to define the various partitions as follows: 
spatial_level map_name extent
Spatial level indicates the level of the spatial heirarchy, and map_name identifies the GRASS raster map which defines the spatial partition. Extent specifies the number of vertical layers defined at that particular level of the spatial hierarchy. The extent parameter allows for non-spatial partitioning at a given level in the spatial hierarchy. The current version of RHESSys only allows non-spatial partitioning to occur at the stratum level (see special module for understory/overstory). Thus, for all levels other than canopy stratum, extent should be equal to 1.

2. Initialization of state variables 
Generally, there are two ways to initialize state variables: assign a constant value, or use a map to assign values. This allows soil or vegetation to either be of one homogenous coverage or vary throughout the landscape, in which case you would reference a map containing multiple ID's. The default ID's used to identify soil and vegetation types in a map correspond to the ID's in the default files. The format for variables in the template is as follows:

Variable_name Function Constant_Value/Map

A. Assign a constant value
Example: soil_default_ID value 3.0
(variable_name) (function) (constant_value)

Assigning a constant value of 3 (the default ID for sandyloam) to the variable soil_default_id within the _patch level would indicate a constant soil type (sandyloam) across the landscape.

B. Use a map to assign values
Example: soil_default_ID mode variable_soils
(variable_name) (function) (map)

The map variable_soils is a map of soils that vary across the landscape. The function mode
takes the modal values from the map used. There are different ways to use maps (mode,
averages, with an equation – see website for more information). Note that for map ID's with variables that should not be averaged, mode must be used.

3. Assigning default ID's and base-stations
The beginning (header) of the template file lists the default and climate station files that will be used to describe the parameters associated with the world objects. Each level of the spatial hierarchy (basin, hillslope, zone, patch, and stratum) has default files associated with it. A climate base station that links to the climate data files must also be listed. The template format lists the number of default files that correspond to a given variable (i.e. number of soil or vegetation types), as well as the number of climate base stations, followed by the location and name of the default file or base station file.

Climate inputs are linked to particular zones by the climate station ID affiliated with that zone. A single climate station (or base station) will typically serve multiple zones within the landscape.

See the attached annotated template at the end of this module for further description of the template structure and content (under construction – I will distribute soon!). It denotes the most commonly edited lines within the template.

The following exercises will take you through editing the fields most commonly edited in the template file, and creating a worldfile.

==Editing the Template==

If you have not already done so, copy the template file to your working directory (contained in grassdata/templates), then open it for editing:

'''unix> vi template'''

If necessary, edit the header by directing the default and climate base station files to the correct path and file names. For this exercise, change the default file patch.def to sandyloam.def to change the soil type default file that RHESSys will look for.

Note the format of the line: ../defs/patch.def
This is the format that will be listed at the top of the worldfile, after g2w uses the template information to create the expanded worldfile.
UNIX format is used to direct RHESSys back one directory relative to where it is being run
from (which will be the scripts directory), into the defs directory, and to read patch.def.

Edit each level of the spatial hierarchy (using the same process of vi commands described above) to correspond with the appropriate map you created in module I (don't worry about extent for now, for this exercise extent should be left at 1 for all layers). For example, if you are using the w8 mapset, you would edit as follows:
<pre>
_world w8basin 1
_basin w8basin 1
_hillslope h100.w8 1
_zone h100.w8 1
_patch w8dem.cl 1
_stratum w8dem.cl 1
</pre>
Within each of the basin, hillslope, zone, and patch levels, edit the z variable to correspond to the DEM map.
Template format: z aver hjadem (average of the DEM at that level)

Within the zone and patch levels, edit the slope variable to correspond to the slope map. Template format: slope aver slope (uses the average Slope)

Within the zone level edit the aspect variable to correspond to the aspect map. Template format: aspect spavg aspect slope (takes the spherical average)

For this exercise, you will only use single values for soil and vegetation across the landscape (i.e. homogeneous soil type). Within the patch level, edit the soil_default_id from 1.0 (default ID used for a general soil type) to 3.0 (default ID assigned to sandyloam).

Be sure to save your changes before quitting.

You can save the template with any extension name you choose. This should be something to identify it, such as template.w8.

Creating the worldfile
You are now ready to run Grass2World, which must be run from within GRASS. Start GRASS and make sure you have the correct LOCATION, MAPSET and DATABASE set.

Make sure you have the appropriate mask set for the watershed you are creating the worldfile for (i.e. w8 or the watershed you created)

'''grass> r.mask'''

At the GRASS prompt, type the command:

'''grass> g2w -w new_worldfile_name -t template_name'''

This will create a worldfile in your working directory (the directory you are currently in) with the output name you indicated on the gw2 command line. By convention, all worldfiles should begin with the prefix world to identify the file as a worldfile. You can use any name you want after the prefix world, however, it should be a name representative of its location, structure, etc... For this exercise I suggest calling it world.tutorial.

Move the worldfile into your worldfiles directory.

==Flowtables==
The flowtable is only necessary if routing is going to be incorporated into the model. The flowtable describes connectivity between patches within a hillslope. A GRASS interface program (cf9) generates the flowtable from the set of images that describe the landscape partitioning, which must correspond with the images used to generate the spatial object hierarchy in the worldfile. cf9 determines how each patch routes water and nutrients, and assigns an effective gradient and transmissivity for each patch, which is used to model subsurface throughflow and overland flow routing.

cf9 uses GRASS raster images to create the flowtable.

Start GRASS

To create the flowtable, at the GRASS prompt type the command:

'''grass> cf9 output=<output filename> template=<worldfile template name> stream=<> road=<> dem=<> slope=<>
'''

where the brackets are filled with the name of the appropriate raster map. cf9 has several additional options,
but these are the required ones. Note that cf9 will pull the name of the basin, hillslope, patch, and zone rasters from the template.
A file name <output>_flow_table.dat will be written to your working directory. Rename this file to prevent overwriting it by subsequent calls to cf9. By convention, flowtables should start with the prefix flow followed by a name representing the study area, ie. flow.w8.
For this exercise, I suggest calling it flow.tutorial.

Move the flowtable to your flowtables directory.

Open the flowtable to look at the structure. The very first line, which is one number, lists the number of patches in the landscape representation. The flow table format lists the patch, zone, and hillslope ID's, followed by X, Y, and Z centroid information, accumulated area, land type, a parameter that integrates the effect of slope boundary width and soil transmissivity, and the number of adjacent patches. Underneath each individual patch are the patch, zone, and hill ID's for the adjacent patches which that patch flow into and a number that indicates the proportion of flow that will be routed to that patch.

==Tecfiles==
RHESSys is structured as an event driven simulation, where most of the process modeling occurs between events. The TEC, or Temporal Event Control file, tells RHESSys when certain events occur. An event may be a redefinition of the strata (ie. removal of vegetation due to fire), or redefinition of the world (ie. in the event of development), or when to start generating output. For this basic exercise, the only temporal event will be a printing event. These events are used to specify printing at an hourly, daily, monthly, or yearly timestep. The tecfile does not specify the level of processing or spatial aggregation (ie. average basin conditions, or the condition of a single hillslope, patch, or stratum) for the output. These options are addressed when you run a simulation and will be explained in module 3. Rather, the tecfile tells RHESSys when something (ie. printing out results) should occur, and how often (ie. daily or monthly) it should occur.

RHESSys has more than 100 state variables that can be looked at. Different command line options in combination with different printing TEC events (tecfile) produce output files with specific variables aggregated to specific spatial/temporal scales. Be sure to consider what type of output you are interested in, as each combination of tecfile and command line options outputs different variables (a list of output file headings and their units is listed at [[Temporal Event Control files]]).

For example, if you are interested in average basin conditions, the outputs are different for daily basin, daily basin growth, monthly basin, and yearly basin output.

Tecfile formatting:
# The TEC file is created in a text editor (such as VI)
# Events must be listed in order of execution
# Only one event per line is allowed, no blank lines are allowed
# The format for events in the TEC file is as follows:
Year Month Day Hour Printing_event
When executing several printing events that start on the same
day, the events must be sequential. Two events cannot be
scheduled to happen at the same time. Therfore, if you have
two printing events scheduled on the same day, make the first
printing event start on hour 1, the second on hour 2, etc...

Create a tecfile with the text editor VI
'''unix> vi tec.tutorial''' (insert the following text (i) and save it
to the new file (wq))

<pre>
1979 10 1 2 print_daily_growth_on
1979 10 1 3 print_monthly_on
<pre>
By convention, all tecfiles should begin with the prefix tec
followed by a name pertaining to your project or task.

A list of other TEC event options is available on the RHESSys website.

Generating RHESSys input files

2010-08-03T17:08:10Z

Dgroulx: /* Tecfiles */

==Default files==
The default files describe characteristics of the variables associated with each object (level) of the spatial hierarchy. The default parameters are assigned values that stay constant through time and describe the performance of the parameters associated with an object. For example, the patch object would have default files associated with it that describe the characteristics of the soil type identified in that patch. Such parameter files are associated with each level of the spatial hierarchy. A library of commonly used parameter files assigned to specific soil, vegetation, and land use types have been developed, based on extensive literature research.

The basin and hillslope default file structures contain no parameters beyond the default file identifier. The default identifier maintains consistency of every object from basin through strata that has that basin/hillslope default identifier.

The zone default file contains atmospheric parameters associated with zone objects. The values provided in the standard zone default file are likely to be reasonably invariant for many environments, therefore, is a good first source in the absence of atmospheric research specific to a study site.

The soil and land use default files associated with the patch object address the routing and input of water at the patch level. Soil default files describe characteristics of particular soil types. Land use default files account for additional nitrogen and water inputs from developed areas.

The stratum default files describe characteristics of different vegetation types and associated processes such as carbon allocation, radiation interception, respiration, stomatal physiology, phenology, etc...

A set of default files has been provided with the tutorial exercise data, which you should have copied into your defs directory. Open a few of these default files to see the structure and content.

'''unix> more veg_conifer.def''' 
'''unix> more sandyloam.def'''

Notice the first line for each default file assigns a default_ID. Every parameter type has a
numerical identification, which corresponds to the ID's assigned in the GIS spatial layers,
and is defined within the levels of the landscape representation. For details on the file
structure and variable descriptions, see the [[Default files]] page.

==Worldfiles==
The worldfile defines the landscape representation within RHESSys. It is based on the hierarchical structure that describes each spatial level containing progressively finer units. The worldfile is generated with a GRASS interface program that references the input maps and a text document defining initial state variables (starting point for each variable). Within the worldfile, each spatial level is associated with the following items:

Identifier: each instance within a level is assigned an ID based on the map used to partition that level.

State Variables: values for stores and fluxes organized at each spatial level are initialized at the start of the simulation, typically changing as the simulation runs (ie. saturation deficit within the patch level)

A link to a climate station: link between the zone level and a particular climate station and the climate time series input information.

Because the worldfile for a complex landscape may contain hundreds of lines, a program called grass2world (g2w) is used to automatically generate the worldfile from spatial data layers within GRASS GIS. To create a worldfile with g2w, you need a text file (by convention, beginning with the prefix template) to be in your home working directory. The template is essentially a set of instructions that tells the GRASS interface program (g2w) how to create the initial values for each of the state variables in a spatial object at each level of the spatial hierarchy. Within the template file are initial values for variables such as carbon and nitrogen stores, or references to images (maps) that hold those values. grass2world expands the template file to assign values for every basin, hillslope, zone, patch, and stratum within the geographic extent of your modeled landscape. grass2world must be run from inside the GRASS GIS system. The program will look for the template file you designate on the command line in the calling directory, along with the associated maps in the GRASS database.

===Template===
There are 3 things that need to be initialized in the template:

1. Definition of the spatial layers 
Spatial definition of the world objects (ie. basin, hillslope, zone, patch, and stratum) can be identified by looking at the lines beginning with an underscore (ie. _basin). Each level in the spatial hierarchy is defined using a raster map (which you created in GRASS in module I). A specific format must be used to define the various partitions as follows: 
spatial_level map_name extent
Spatial level indicates the level of the spatial heirarchy, and map_name identifies the GRASS raster map which defines the spatial partition. Extent specifies the number of vertical layers defined at that particular level of the spatial hierarchy. The extent parameter allows for non-spatial partitioning at a given level in the spatial hierarchy. The current version of RHESSys only allows non-spatial partitioning to occur at the stratum level (see special module for understory/overstory). Thus, for all levels other than canopy stratum, extent should be equal to 1.

2. Initialization of state variables 
Generally, there are two ways to initialize state variables: assign a constant value, or use a map to assign values. This allows soil or vegetation to either be of one homogenous coverage or vary throughout the landscape, in which case you would reference a map containing multiple ID's. The default ID's used to identify soil and vegetation types in a map correspond to the ID's in the default files. The format for variables in the template is as follows:

Variable_name Function Constant_Value/Map

A. Assign a constant value
Example: soil_default_ID value 3.0
(variable_name) (function) (constant_value)

Assigning a constant value of 3 (the default ID for sandyloam) to the variable soil_default_id within the _patch level would indicate a constant soil type (sandyloam) across the landscape.

B. Use a map to assign values
Example: soil_default_ID mode variable_soils
(variable_name) (function) (map)

The map variable_soils is a map of soils that vary across the landscape. The function mode
takes the modal values from the map used. There are different ways to use maps (mode,
averages, with an equation – see website for more information). Note that for map ID's with variables that should not be averaged, mode must be used.

3. Assigning default ID's and base-stations
The beginning (header) of the template file lists the default and climate station files that will be used to describe the parameters associated with the world objects. Each level of the spatial hierarchy (basin, hillslope, zone, patch, and stratum) has default files associated with it. A climate base station that links to the climate data files must also be listed. The template format lists the number of default files that correspond to a given variable (i.e. number of soil or vegetation types), as well as the number of climate base stations, followed by the location and name of the default file or base station file.

Climate inputs are linked to particular zones by the climate station ID affiliated with that zone. A single climate station (or base station) will typically serve multiple zones within the landscape.

See the attached annotated template at the end of this module for further description of the template structure and content (under construction – I will distribute soon!). It denotes the most commonly edited lines within the template.

The following exercises will take you through editing the fields most commonly edited in the template file, and creating a worldfile.

==Editing the Template==

If you have not already done so, copy the template file to your working directory (contained in grassdata/templates), then open it for editing:

'''unix> vi template'''

If necessary, edit the header by directing the default and climate base station files to the correct path and file names. For this exercise, change the default file patch.def to sandyloam.def to change the soil type default file that RHESSys will look for.

Note the format of the line: ../defs/patch.def
This is the format that will be listed at the top of the worldfile, after g2w uses the template information to create the expanded worldfile.
UNIX format is used to direct RHESSys back one directory relative to where it is being run
from (which will be the scripts directory), into the defs directory, and to read patch.def.

Edit each level of the spatial hierarchy (using the same process of vi commands described above) to correspond with the appropriate map you created in module I (don't worry about extent for now, for this exercise extent should be left at 1 for all layers). For example, if you are using the w8 mapset, you would edit as follows:
<pre>
_world w8basin 1
_basin w8basin 1
_hillslope h100.w8 1
_zone h100.w8 1
_patch w8dem.cl 1
_stratum w8dem.cl 1
</pre>
Within each of the basin, hillslope, zone, and patch levels, edit the z variable to correspond to the DEM map.
Template format: z aver hjadem (average of the DEM at that level)

Within the zone and patch levels, edit the slope variable to correspond to the slope map. Template format: slope aver slope (uses the average Slope)

Within the zone level edit the aspect variable to correspond to the aspect map. Template format: aspect spavg aspect slope (takes the spherical average)

For this exercise, you will only use single values for soil and vegetation across the landscape (i.e. homogeneous soil type). Within the patch level, edit the soil_default_id from 1.0 (default ID used for a general soil type) to 3.0 (default ID assigned to sandyloam).

Be sure to save your changes before quitting.

You can save the template with any extension name you choose. This should be something to identify it, such as template.w8.

Creating the worldfile
You are now ready to run Grass2World, which must be run from within GRASS. Start GRASS and make sure you have the correct LOCATION, MAPSET and DATABASE set.

Make sure you have the appropriate mask set for the watershed you are creating the worldfile for (i.e. w8 or the watershed you created)

'''grass> r.mask'''

At the GRASS prompt, type the command:

'''grass> g2w -w new_worldfile_name -t template_name'''

This will create a worldfile in your working directory (the directory you are currently in) with the output name you indicated on the gw2 command line. By convention, all worldfiles should begin with the prefix world to identify the file as a worldfile. You can use any name you want after the prefix world, however, it should be a name representative of its location, structure, etc... For this exercise I suggest calling it world.tutorial.

Move the worldfile into your worldfiles directory.

==Flowtables==
The flowtable is only necessary if routing is going to be incorporated into the model. The flowtable describes connectivity between patches within a hillslope. A GRASS interface program (cf9) generates the flowtable from the set of images that describe the landscape partitioning, which must correspond with the images used to generate the spatial object hierarchy in the worldfile. cf9 determines how each patch routes water and nutrients, and assigns an effective gradient and transmissivity for each patch, which is used to model subsurface throughflow and overland flow routing.

cf9 uses GRASS raster images to create the flowtable.

Start GRASS

To create the flowtable, at the GRASS prompt type the command:

'''grass> cf9 output=<output filename> template=<worldfile template name> stream=<> road=<> dem=<> slope=<>
'''

where the brackets are filled with the name of the appropriate raster map. cf9 has several additional options,
but these are the required ones. Note that cf9 will pull the name of the basin, hillslope, patch, and zone rasters from the template.
A file name <output>_flow_table.dat will be written to your working directory. Rename this file to prevent overwriting it by subsequent calls to cf9. By convention, flowtables should start with the prefix flow followed by a name representing the study area, ie. flow.w8.
For this exercise, I suggest calling it flow.tutorial.

Move the flowtable to your flowtables directory.

Open the flowtable to look at the structure. The very first line, which is one number, lists the number of patches in the landscape representation. The flow table format lists the patch, zone, and hillslope ID's, followed by X, Y, and Z centroid information, accumulated area, land type, a parameter that integrates the effect of slope boundary width and soil transmissivity, and the number of adjacent patches. Underneath each individual patch are the patch, zone, and hill ID's for the adjacent patches which that patch flow into and a number that indicates the proportion of flow that will be routed to that patch.

==Tecfiles==
RHESSys is structured as an event driven simulation, where most of the process modeling occurs between events. The TEC, or Temporal Event Control file, tells RHESSys when certain events occur. An event may be a redefinition of the strata (ie. removal of vegetation due to fire), or redefinition of the world (ie. in the event of development), or when to start generating output. For this basic exercise, the only temporal event will be a printing event. These events are used to specify printing at an hourly, daily, monthly, or yearly timestep. The tecfile does not specify the level of processing or spatial aggregation (ie. average basin conditions, or the condition of a single hillslope, patch, or stratum) for the output. These options are addressed when you run a simulation and will be explained in module 3. Rather, the tecfile tells RHESSys when something (ie. printing out results) should occur, and how often (ie. daily or monthly) it should occur.

RHESSys has more than 100 state variables that can be looked at. Different command line options in combination with different printing TEC events (tecfile) produce output files with specific variables aggregated to specific spatial/temporal scales. Be sure to consider what type of output you are interested in, as each combination of tecfile and command line options outputs different variables (a list of output file headings and their units is listed at [[Temporal Event Control files]]).

For example, if you are interested in average basin conditions, the outputs are different for daily basin, daily basin growth, monthly basin, and yearly basin output.

Tecfile formatting:
1. The TEC file is created in a text editor (such as VI)
2. Events must be listed in order of execution
3. Only one event per line is allowed, no blank lines are allowed
4. The format for events in the TEC file is as follows:
Year Month Day Hour Printing_event
When executing several printing events that start on the same
day, the events must be sequential. Two events cannot be
scheduled to happen at the same time. Therfore, if you have
two printing events scheduled on the same day, make the first
printing event start on hour 1, the second on hour 2, etc...

Create a tecfile with the text editor VI
'''unix> vi tec.tutorial''' (insert the following text (i) and save it
to the new file (wq))

<pre>
1979 10 1 2 print_daily_growth_on
1979 10 1 3 print_monthly_on
<pre>
By convention, all tecfiles should begin with the prefix tec
followed by a name pertaining to your project or task.

A list of other TEC event options is available on the RHESSys website.

Generating RHESSys input files

2010-08-03T17:07:41Z

Dgroulx: /* Tecfiles */

==Default files==
The default files describe characteristics of the variables associated with each object (level) of the spatial hierarchy. The default parameters are assigned values that stay constant through time and describe the performance of the parameters associated with an object. For example, the patch object would have default files associated with it that describe the characteristics of the soil type identified in that patch. Such parameter files are associated with each level of the spatial hierarchy. A library of commonly used parameter files assigned to specific soil, vegetation, and land use types have been developed, based on extensive literature research.

The basin and hillslope default file structures contain no parameters beyond the default file identifier. The default identifier maintains consistency of every object from basin through strata that has that basin/hillslope default identifier.

The zone default file contains atmospheric parameters associated with zone objects. The values provided in the standard zone default file are likely to be reasonably invariant for many environments, therefore, is a good first source in the absence of atmospheric research specific to a study site.

The soil and land use default files associated with the patch object address the routing and input of water at the patch level. Soil default files describe characteristics of particular soil types. Land use default files account for additional nitrogen and water inputs from developed areas.

The stratum default files describe characteristics of different vegetation types and associated processes such as carbon allocation, radiation interception, respiration, stomatal physiology, phenology, etc...

A set of default files has been provided with the tutorial exercise data, which you should have copied into your defs directory. Open a few of these default files to see the structure and content.

'''unix> more veg_conifer.def''' 
'''unix> more sandyloam.def'''

Notice the first line for each default file assigns a default_ID. Every parameter type has a
numerical identification, which corresponds to the ID's assigned in the GIS spatial layers,
and is defined within the levels of the landscape representation. For details on the file
structure and variable descriptions, see the [[Default files]] page.

==Worldfiles==
The worldfile defines the landscape representation within RHESSys. It is based on the hierarchical structure that describes each spatial level containing progressively finer units. The worldfile is generated with a GRASS interface program that references the input maps and a text document defining initial state variables (starting point for each variable). Within the worldfile, each spatial level is associated with the following items:

Identifier: each instance within a level is assigned an ID based on the map used to partition that level.

State Variables: values for stores and fluxes organized at each spatial level are initialized at the start of the simulation, typically changing as the simulation runs (ie. saturation deficit within the patch level)

A link to a climate station: link between the zone level and a particular climate station and the climate time series input information.

Because the worldfile for a complex landscape may contain hundreds of lines, a program called grass2world (g2w) is used to automatically generate the worldfile from spatial data layers within GRASS GIS. To create a worldfile with g2w, you need a text file (by convention, beginning with the prefix template) to be in your home working directory. The template is essentially a set of instructions that tells the GRASS interface program (g2w) how to create the initial values for each of the state variables in a spatial object at each level of the spatial hierarchy. Within the template file are initial values for variables such as carbon and nitrogen stores, or references to images (maps) that hold those values. grass2world expands the template file to assign values for every basin, hillslope, zone, patch, and stratum within the geographic extent of your modeled landscape. grass2world must be run from inside the GRASS GIS system. The program will look for the template file you designate on the command line in the calling directory, along with the associated maps in the GRASS database.

===Template===
There are 3 things that need to be initialized in the template:

1. Definition of the spatial layers 
Spatial definition of the world objects (ie. basin, hillslope, zone, patch, and stratum) can be identified by looking at the lines beginning with an underscore (ie. _basin). Each level in the spatial hierarchy is defined using a raster map (which you created in GRASS in module I). A specific format must be used to define the various partitions as follows: 
spatial_level map_name extent
Spatial level indicates the level of the spatial heirarchy, and map_name identifies the GRASS raster map which defines the spatial partition. Extent specifies the number of vertical layers defined at that particular level of the spatial hierarchy. The extent parameter allows for non-spatial partitioning at a given level in the spatial hierarchy. The current version of RHESSys only allows non-spatial partitioning to occur at the stratum level (see special module for understory/overstory). Thus, for all levels other than canopy stratum, extent should be equal to 1.

2. Initialization of state variables 
Generally, there are two ways to initialize state variables: assign a constant value, or use a map to assign values. This allows soil or vegetation to either be of one homogenous coverage or vary throughout the landscape, in which case you would reference a map containing multiple ID's. The default ID's used to identify soil and vegetation types in a map correspond to the ID's in the default files. The format for variables in the template is as follows:

Variable_name Function Constant_Value/Map

A. Assign a constant value
Example: soil_default_ID value 3.0
(variable_name) (function) (constant_value)

Assigning a constant value of 3 (the default ID for sandyloam) to the variable soil_default_id within the _patch level would indicate a constant soil type (sandyloam) across the landscape.

B. Use a map to assign values
Example: soil_default_ID mode variable_soils
(variable_name) (function) (map)

The map variable_soils is a map of soils that vary across the landscape. The function mode
takes the modal values from the map used. There are different ways to use maps (mode,
averages, with an equation – see website for more information). Note that for map ID's with variables that should not be averaged, mode must be used.

3. Assigning default ID's and base-stations
The beginning (header) of the template file lists the default and climate station files that will be used to describe the parameters associated with the world objects. Each level of the spatial hierarchy (basin, hillslope, zone, patch, and stratum) has default files associated with it. A climate base station that links to the climate data files must also be listed. The template format lists the number of default files that correspond to a given variable (i.e. number of soil or vegetation types), as well as the number of climate base stations, followed by the location and name of the default file or base station file.

Climate inputs are linked to particular zones by the climate station ID affiliated with that zone. A single climate station (or base station) will typically serve multiple zones within the landscape.

See the attached annotated template at the end of this module for further description of the template structure and content (under construction – I will distribute soon!). It denotes the most commonly edited lines within the template.

The following exercises will take you through editing the fields most commonly edited in the template file, and creating a worldfile.

==Editing the Template==

If you have not already done so, copy the template file to your working directory (contained in grassdata/templates), then open it for editing:

'''unix> vi template'''

If necessary, edit the header by directing the default and climate base station files to the correct path and file names. For this exercise, change the default file patch.def to sandyloam.def to change the soil type default file that RHESSys will look for.

Note the format of the line: ../defs/patch.def
This is the format that will be listed at the top of the worldfile, after g2w uses the template information to create the expanded worldfile.
UNIX format is used to direct RHESSys back one directory relative to where it is being run
from (which will be the scripts directory), into the defs directory, and to read patch.def.

Edit each level of the spatial hierarchy (using the same process of vi commands described above) to correspond with the appropriate map you created in module I (don't worry about extent for now, for this exercise extent should be left at 1 for all layers). For example, if you are using the w8 mapset, you would edit as follows:
<pre>
_world w8basin 1
_basin w8basin 1
_hillslope h100.w8 1
_zone h100.w8 1
_patch w8dem.cl 1
_stratum w8dem.cl 1
</pre>
Within each of the basin, hillslope, zone, and patch levels, edit the z variable to correspond to the DEM map.
Template format: z aver hjadem (average of the DEM at that level)

Within the zone and patch levels, edit the slope variable to correspond to the slope map. Template format: slope aver slope (uses the average Slope)

Within the zone level edit the aspect variable to correspond to the aspect map. Template format: aspect spavg aspect slope (takes the spherical average)

For this exercise, you will only use single values for soil and vegetation across the landscape (i.e. homogeneous soil type). Within the patch level, edit the soil_default_id from 1.0 (default ID used for a general soil type) to 3.0 (default ID assigned to sandyloam).

Be sure to save your changes before quitting.

You can save the template with any extension name you choose. This should be something to identify it, such as template.w8.

Creating the worldfile
You are now ready to run Grass2World, which must be run from within GRASS. Start GRASS and make sure you have the correct LOCATION, MAPSET and DATABASE set.

Make sure you have the appropriate mask set for the watershed you are creating the worldfile for (i.e. w8 or the watershed you created)

'''grass> r.mask'''

At the GRASS prompt, type the command:

'''grass> g2w -w new_worldfile_name -t template_name'''

This will create a worldfile in your working directory (the directory you are currently in) with the output name you indicated on the gw2 command line. By convention, all worldfiles should begin with the prefix world to identify the file as a worldfile. You can use any name you want after the prefix world, however, it should be a name representative of its location, structure, etc... For this exercise I suggest calling it world.tutorial.

Move the worldfile into your worldfiles directory.

==Flowtables==
The flowtable is only necessary if routing is going to be incorporated into the model. The flowtable describes connectivity between patches within a hillslope. A GRASS interface program (cf9) generates the flowtable from the set of images that describe the landscape partitioning, which must correspond with the images used to generate the spatial object hierarchy in the worldfile. cf9 determines how each patch routes water and nutrients, and assigns an effective gradient and transmissivity for each patch, which is used to model subsurface throughflow and overland flow routing.

cf9 uses GRASS raster images to create the flowtable.

Start GRASS

To create the flowtable, at the GRASS prompt type the command:

'''grass> cf9 output=<output filename> template=<worldfile template name> stream=<> road=<> dem=<> slope=<>
'''

where the brackets are filled with the name of the appropriate raster map. cf9 has several additional options,
but these are the required ones. Note that cf9 will pull the name of the basin, hillslope, patch, and zone rasters from the template.
A file name <output>_flow_table.dat will be written to your working directory. Rename this file to prevent overwriting it by subsequent calls to cf9. By convention, flowtables should start with the prefix flow followed by a name representing the study area, ie. flow.w8.
For this exercise, I suggest calling it flow.tutorial.

Move the flowtable to your flowtables directory.

Open the flowtable to look at the structure. The very first line, which is one number, lists the number of patches in the landscape representation. The flow table format lists the patch, zone, and hillslope ID's, followed by X, Y, and Z centroid information, accumulated area, land type, a parameter that integrates the effect of slope boundary width and soil transmissivity, and the number of adjacent patches. Underneath each individual patch are the patch, zone, and hill ID's for the adjacent patches which that patch flow into and a number that indicates the proportion of flow that will be routed to that patch.

==Tecfiles==
RHESSys is structured as an event driven simulation, where most of the process modeling occurs between events. The TEC, or Temporal Event Control file, tells RHESSys when certain events occur. An event may be a redefinition of the strata (ie. removal of vegetation due to fire), or redefinition of the world (ie. in the event of development), or when to start generating output. For this basic exercise, the only temporal event will be a printing event. These events are used to specify printing at an hourly, daily, monthly, or yearly timestep. The tecfile does not specify the level of processing or spatial aggregation (ie. average basin conditions, or the condition of a single hillslope, patch, or stratum) for the output. These options are addressed when you run a simulation and will be explained in module 3. Rather, the tecfile tells RHESSys when something (ie. printing out results) should occur, and how often (ie. daily or monthly) it should occur.

RHESSys has more than 100 state variables that can be looked at. Different command line options in combination with different printing TEC events (tecfile) produce output files with specific variables aggregated to specific spatial/temporal scales. Be sure to consider what type of output you are interested in, as each combination of tecfile and command line options outputs different variables (a list of output file headings and their units is listed on the RHESSys website in appendix C). [[Temporal Event Control files]]

For example, if you are interested in average basin conditions, the outputs are different for daily basin, daily basin growth, monthly basin, and yearly basin output.

Tecfile formatting:
1. The TEC file is created in a text editor (such as VI)
2. Events must be listed in order of execution
3. Only one event per line is allowed, no blank lines are allowed
4. The format for events in the TEC file is as follows:
Year Month Day Hour Printing_event
When executing several printing events that start on the same
day, the events must be sequential. Two events cannot be
scheduled to happen at the same time. Therfore, if you have
two printing events scheduled on the same day, make the first
printing event start on hour 1, the second on hour 2, etc...

Create a tecfile with the text editor VI
'''unix> vi tec.tutorial''' (insert the following text (i) and save it
to the new file (wq))

<pre>
1979 10 1 2 print_daily_growth_on
1979 10 1 3 print_monthly_on
<pre>
By convention, all tecfiles should begin with the prefix tec
followed by a name pertaining to your project or task.

A list of other TEC event options is available on the RHESSys website.

Soils

2010-07-22T22:49:29Z

Dgroulx:

Soils

2010-07-22T22:49:10Z

Dgroulx:

Soils

2010-07-22T22:48:56Z

Dgroulx:

Output Files

2010-07-16T18:53:33Z

Dgroulx: /* Stratum Yearly */

== Basin Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| || ||
|-
| 2||Month|| || ||
|-
| 3||Year|| || ||
|-
| 4||Basin ID|| || ||
|-
| 5||Rain Throughfall||mm||pot_surface_infil||
|-
| 6||Snow Throughfall||mm||snow_thr||
|-
| 7||Saturation Deficit-depth||mm of depth||sat_def_z||
|-
| 8||Saturation Deficit-volume||mm of water||sat_def||
|-
| 8||Rooting Zone Storage||mm of water||rz_storage||
|-
| 9||Unsaturated Storage||mm||unsat_stor||
|-
| 10||Unsaturated Drainage||mm||unsat_drain||
|-
| 11||Capillary Rise||mm||cap||
|-
| 12||Evaporation||mm||evap||
|-
| 13||Snowpack Depth||mm||snow||
|-
| 14||Transpiration||mm||trans||
|-
| 15||Baseflow||mm||baseflow||
|-
| 20||Return Flow||mm||return||
|-
| 17||Total Stream Outflow||mm||streamflow||
|-
| 18||Net Photosynthesis||kgC/m2||psn||
|-
| 19||Leaf Area Index||m2/m2||lai||
|-
| 20||Groundwater Output||mm||gw.Qout||
|-
| 21||Groundwater Nitrate Output||mm||gw.Nout||
|-
| 22||Groundwater Store||mm||gw.storage||rhessys5.10.5
|-
| 23||Groundwater Nitrate Store||mm||gw.NO3||rhessys5.10.5
|-
| 24||Detention Store||mm||detention_store||rhessys5.10.10
|-
| 25||Percent Saturated Area||m2/m2||%sat_area||rhessys5.10.10
|-
| 26||Litter Store||m2/m2||litter_store||rhessys5.10.12
|-
| 27||Percent Snow Cover||m2/m2||%snow_cover||rhessys5.10.12
|}

== Basin Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Gross Photosynthesis||gC/m2||gpsn
|-
| 6||Plant Maintenance Respiration||mC/m2||plant_resp
|-
| 7||Soil Respiration||gC/m2/day||soil_resp||rhessys5.10.11
|-
| 8||Nitrate N||gN/m2||nitrate
|-
| 9||Mineralized N||gN/m2||sminn
|-
| 10||Plant C||kgC/m2||plantc
|-
| 11||Plant N||kgN/m2||plantn
|-
| 12||Litter C||kgC/m2||litrc
|-
| 13||Litter N||kgN/m2||litrn
|-
| 14||Soil C||kgC/m2||soilc
|-
| 15||Soil N||kgN/m2||soiln
|-
| 16||Streamflow Nitrate||gN/m2/day||streamflow_NO3
|-
| 17||Denitrification||gN/m2/day||denitrif
|-
| 18||Nitrification||gN/m2/day||nitrif
|-
| 19||Dissolved Organic Carbon loss||gC/m2/day||DOC
|-
| 20||Dissolved Organic Nitrogen loss||gN/m2/day||DON
|}

== Basin Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Total Stream Outflow||mm||streamflow
|-
| 5||Nitrate to Stream||gN/m2||streamflow_NO3
|-
| 6||Denitrification||gN/m2||denitrif
|-
| 7||Dissolved Organic Carbon loss||gC/m2||DOC
|-
| 8||Dissolved Organic Nitrogen loss||gN/m2||DON
|-
| 9||Evapotranspiration||mm/m2||et
|-
| 10||Net Photosynthesis||gC/m2||psn
|-
| 11||Leaf Area Index||m2/m2||lai
|-
| 12||Nitrification||gN/m2||nitrif
|-
| 13||Mineralized Nitrate||gN/m2||mineralized
|-
| 14||Vegetation Nitrogen Uptake||gN/m2||uptake
|}

== Basin Yearly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Total Stream Outflow||mm||streamflow
|-
| 4||Nitrate to Stream||gN/m2||streamflow_NO3
|-
| 5||Denitrification||gN/m2||denitrif
|-
| 6||Dissolved Organic Carbon loss||gC/m2||DOC
|-
| 7||Dissolved Organic Nitrogen loss||gN/m2||DON
|-
| 8||Evapotranspiration||mm/m2||et
|-
| 9||Net Photosynthesis||gC/m2||psn
|-
| 10||Average Leaf Area Index||m2/m2||lai
|-
| 11||Nitrification||gN/m2||nitrif
|-
| 12||Mineralized N||gN/m2||mineralized
|-
| 13||Vegetation Uptake||gN/m2||uptake
|-
| 14||Number Threshold||?||num_thresh
|}

== Basin Yearly Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Year|| || ||rhessys5.10.5
|-
| 2||Basin ID|| || ||rhessys5.10.5
|-
| 3||Gross Photosynthesis||gC/m2||gpsn||rhessys5.10.5
|-
| 4||Plant Respiration||mC/m2||plantresp||rhessys5.10.5
|-
| 5||New Carbon||mC/m2||newC||rhessys5.10.5
|-
| 6||?Soilhr?||??||soilhr||rhessys5.10.5
|-
| 7||?Streamflow Nitrate?||??||strN||rhessys5.10.5
|-
| 8||Denitrification||gN/m2||denitrif||rhessys5.10.5
|-
|
|}

== Hillslope Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Rain Throughfall||mm||rain_thr
|-
| 7||Snow Throughfall||mm||snow_thr
|-
| 8||Saturation Deficit||mm of depth||sat_def_z
|-
| 9||Saturation Deficit||mm of water||sat_def
|-
| 10||Unsaturated Storage||mm||unsat_stor
|-
| 11||Unsaturated Drainage||mm||unsat_drain
|-
| 12||Capillary Rise||mm||cap
|-
| 13||Evaporation||mm||evap
|-
| 14||Snowpack Depth||mm||snow
|-
| 15||Transpiration||mm||trans
|-
| 16||Baseflow||mm||baseflow
|-
| 17||Return Flow||mm||return
|-
| 18||Total Stream Outflow||mm||streamflow
|-
| 19||Net Photosynthesis||kgC/m2||psn
|-
| 20||Leaf Area Index||m2/m2||lai
|-
| 21||Groundwater Output||mm||gw.Qout||rhessys5.10.5
|-
| 22||Groundwater Nitrate Output||mm||gw.Nout||rhessys5.10.5
|-
| 23||Groundwater Store||mm||gw.storage||rhessys5.10.5
|-
| 24||Groundwater Nitrate Store||mm||gw.N03||rhessys5.10.5
|}

== Hillslope Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Gross Photosynthesis||gC/m2||gpsn
|-
| 7||Maint Respiration||mC/m2||resp
|-
| 8||Nitrate N||gN/m2||nitrate
|-
| 9||Mineralized N||gN/m2||sminn
|-
| 10||Plant C||kgC/m2||plantc
|-
| 11||Plant N||kgN/m2||plantn
|-
| 12||Litter C||kgC/m2||litrc
|-
| 13||Litter N||kgN/m2||litrn
|-
| 14||Soil C||kgC/m2||soilc
|-
| 15||Soil N||kgN/m2||soiln
|-
| 16||Streamflow Nitrate||gN/m2/day||streamflow_NO3
|-
| 17||Streamflow||mm/day||streamflow
|-
| 18||Denitrification||gN/m2/day||denitrif
|-
| 19||Nitrification||gN/m2/day||nitrif
|-
| 20||Dissolved Organic Carbon loss||gC/m2/day||DOC
|-
| 21||Dissolved Organic Nitrogen loss||gN/m2/day||DON
|-
|
|}

== Hillslope Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| || ||rhessys5.10.7
|-
| 2||Year|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Streamflow||mm||streamflow
|-
| 5||Streamflow Nitrate||gN/m2/day||streamflow_N03
|-
| 6||Denitrification||gN/m2/day||denitrif
|-
| 7||Dissolved Organic Carbon Loss||gC/m2/day||DOC
|-
| 8||Dissolved Organic Nitrogen Loss||gN/m2/day||DON
|-
| 9||Evapotranspiration||mm/m2||et
|-
| 10||Net Photosynthesis||gC/m2||psn
|-
| 11||Leaf Area Index||m2/m2||lai
|-
| 12||Nitrification||gN/m2||nitrif
|-
| 13||Mineralized N||gN/m2||mineralized
|-
| 14||Vegetation Uptake||gN/m2||uptake
|}

== Hillslope Yearly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| || ||rhessys5.10.7
|-
| 2||Hillslope ID|| ||
|-
| 3||Streamflow||mm||streamflow
|-
| 4||Nitrate to Stream||gN/m2||streamflow_N03
|-
| 5||Denitrification||gN/m2||denitrif
|-
| 6||Dissolved Organic Carbon loss||gC/m2||DOC
|-
| 7||Dissolved Organic Nitrogen loss||gN/m2||DON
|-
| 8||Evapotranspiration||mm/m2||et
|-
| 9||Net Photosynthesis||gC/m2||psn
|-
| 10||Mineralized N||gN/m2||mineralized
|-
| 11||Vegetation Uptake||gN/m2||uptake
|}

== Zone Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Rainfall||mm||rain
|-
| 8||Snowfall||mm||snow
|-
| 9||Daytime Mean Air Temperature||C||tday
|-
| 10||Average Daily Temperature||C||tavg
|-
| 11||Vapour Pressure Deficit||Pa||vpd
|-
| 12||Direct Radiation||KJ/m2||Kdown_direct
|-
| 13||Diffuse Radiation||KJ/m2||Kdown_diffuse
|-
| 14||Direct PAR Radiation||KJ/m2||PAR_direct
|-
| 15||Diffuse PAR Radiation||KJ/m2||PAR_diffuse
|}

== Zone Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Hillslope ID|| ||
|-
| 5||Zone ID|| ||
|-
| 6||Precipitation||mm||precip
|-
| 7||Direct Radiation||KJ/m2||K_direct
|-
| 8||Diffuse Radiation||KJ/m2||K_diffuse
|-
| 9||Average Max Daily Temperature||C||tmax
|-
| 10||Average Min Daily Temperature||C||tmin
|}

== Patch Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Rain Throughfall||mm||rain_thr
|-
| 9||Detention Store||mm||detention_store||rhessys5.10.10
|-
| 10||Saturation Deficit (depth)||mm of depth||sat_def_z
|-
| 11||Saturation Deficit (water)||mm of water||sat_def
|-
| 12||Unsaturated Storage||mm||unsat_stor
|-
| 13||Unsaturated Drainage||mm||unsat_drain
|-
| 14||Capillary Rise||mm||cap
|-
| 15||Return Flow||mm||return
|-
| 16||Evaporation||mm||evap
|-
| 17||Snowpack Depth||mm||snow
|-
| 18||Transpiration||mm||trans
|-
| 19||Subsurface Flow to Stream||mm||Qin||rhessys5.10.9
|-
| 20||Subsurface Flow to Stream||mm||Qout||rhessys5.10.9
|-
| 21||Net Photosynthesis||kgC/m2||psn
|-
| 22||Rooting Zone Saturation||?||root_zone.S
|-
| 23||Litter Rain Stored||mm||litter.rain_stor||rhessys5.10.10
|-
| 24||Litter Percent Saturation||m2/m2 ?||litter.S||rhessys5.10.9
|}

== Patch Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Leaf Area Index||m2/m2||lai
|-
| 9||Plant C||kgC/m2||plantc
|-
| 10||Net Photosynthesis||gC/m2||net_psn
|-
| 11||Plant Respiration||gC/m2/day||plant_resp||rhessys5.10.11
|-
| 12||Soil Respiration||gC/m2/day||soil_resp||rhessys5.10.11
|-
| 13||Labile Litter C||kgC/m2||litr1c
|-
| 14||Cellulose Litter C||kgC/m2||litr2c
|-
| 15||Shielded Cellulose Litter C||kgC/m2||litr3c
|-
| 16||Lignan Litter C||kgC/m2||litr4c
|-
| 17||Litter Rain Capacity||mm||lit.rain_cap||rhessys5.10.10
|-
| 18||Fast Soil C||kgC/m2||soil1c
|-
| 19||Medium Soil C||kgC/m2||soil2c
|-
| 20||Slow Soil C||kgC/m2||soil3c
|-
| 21||Recalcitrant Soil C||kgC/m2||soil4c
|-
| 22||Denitrification||gN/m2||denitrif
|-
| 23||Net Nitrate Flux (+in)||gN/m2||netleach
|-
| 24||Soil Nitrate||gN/m2||soilNO3
|-
| 25||Streamflow N||gN/m2||streamN03
|-
| 26||Surface N||gN/m2||surfaceN03
|-
| 27||Canopy Height||m||height
|-
| 28||Nitrogen Uptake||??||N-uptake
|-
| 29||Area||cells||area
|}

== Patch Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Hillslope ID|| ||
|-
| 5||Zone ID|| ||
|-
| 6||Patch ID|| ||
|-
| 7||Net Nitrate Flux (+in)||gN/m2||leach
|-
| 8||Denitrification||gN/m2/month||denitrif
|-
| 9||Average Soil Moisture Deficit||mm||soil_moist_deficit
|-
| 10||Evapotranspiration||mm/m2/month||et
|-
| 11||Net Photosynthesis||gC/m2/month||psn
|-
| 12||Dissolved Organic Carbon loss||gC/m2/month||DOC
|-
| 13||Dissolved Organic Nitrogen loss||gN/m2/month||DON
|-
| 14||Average LAI||m2/m2||lai
|-
| 15||Nitrification||gN/m2/month||nitrif
|-
| 16||Mineralized N||gN/m2/month||mineralized
|-
| 17||Vegetation Uptake||gN/m2/month||uptake
|-
| 18||Theta||0-100 percent||theta
|}

== Patch Yearly ==

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Zone ID|| ||
|-
| 5||Patch ID|| ||
|-
| 6||Number of Days Below Sat. Threshold|| ||num_threshold_sat_def
|-
| 7||Net Nitrate Flux (+in)||gN/m2/year||leach
|-
| 8||Denitrification||gN/m2/year||denitrif
|-
| 9||Dissolved Organic Carbon loss||gC/m2/year||DOC_loss
|-
| 10||Dissolved Organic Nitrogen loss||gN/m2/year||DON_loss
|-
| 11||Net Photosynthesis||gC/m2||psn
|-
| 12||Evapotranspiration||mm/m2/year||et
|-
| 13||Maximum Leaf Area Index||m2/m2/year||lai
|-
| 14||Nitrification||gN/m2/year||nitrif
|-
| 15||Mineralized N||gN/m2year||mineralized
|-
| 16||Vegetation Uptake||gN/m2/year||uptake
|-
| 17||Theta||0-100 percent||theta
|}

== Patch Yearly Growth ==

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Zone ID|| ||
|-
| 5||Patch ID|| ||
|-
| 6||Litter C||kgC/m2||litter_c
|-
| 7||Soil C||kgC/m2/year||soil_c
|-
| 8||Litter N||kgN/m2/year||litter_n
|-
| 9||Soil N||kgN/m2/year||soil_n
|-
| 10||Soil Nitrate||gN/m2/year||nitrate
|-
| 11||Mineralized N||gN/m2||Sminn
|}

== Stratum Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Stratum ID|| ||
|-
| 9||Leaf Area Index||m2/m2||lai
|-
| 10||Evaporation||mm||evap
|-
| 11||APAR Radiation||KJ/m2||APAR_direct
|-
| 12||APAR Radiation||KJ/m2||APAR_diffuse
|-
| 13||Sublimation||mm||sublim
|-
| 14||Transpiration||mm||trans
|-
| 15||Aerodynamic Conductance||mm/s||ga
|-
| 16||Surface (non-vascular) Conductance||m/s||gsurf
|-
| 17||Canopy Conductance||mm/s||gs
|-
| 18||??||??||?psi?||rhessys5.10.10
|-
| 19||Respiration||kgC/m2||leaf_day_mr
|-
| 20||Net Photosynthesis||gC/m2||psn_to_cpool
|-
| 21||Rain Interception Storage||mm||rain_stored
|-
| 22||Snow Interception Storage||mm||snow_stored
|-
| 23||Rooting Zone Saturation||??||rootzone.S
|}

== Stratum Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Stratum ID|| ||
|-
| 9||Leaf Area Index||m2/m2||proj_lai
|-
| 10||Leaf C||gN/m2||leafc
|-
| 11||Dead Leaf C||gN/m2||dead_leafc
|-
| 12||Fine Root C||gN/m2||frootc
|-
| 13||Live Stem C||gN/m2||live_stemc
|-
| 14||Leaf C Store||gN/m2||leafc_store
|-
| 15||Dead Stem C||gN/m2||dead_stemc
|-
| 16||Live Coarse Root C||gN/m2||live_crootc
|-
| 17||Dead Coarse Root C||gN/m2||dead_crootc
|-
| 18||Coarse Woody Debris C||gN/m2||cwdc
|-
| 19||Maint Respiration||gC/m2||mresp
|-
| 20||Growth Respiration||gC/m2||gresp
|-
| 21||Net Photosynthesis||gC/m2||psn_to_cpool
|-
| 22||Stand Age||days||age||rhessys5.10.9
|}

== Stratum Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Hillslope ID|| ||
|-
| 5||Zone ID|| ||
|-
| 6||Patch ID|| ||
|-
| 7||Stratum ID|| ||
|-
| 8||Leaf Area Index||m2/m2||lai
|-
| 9||Net Photosynthesis||gC/m2||psn
|-
| 10||Mean Leaf Water Potential||mPa||lwp
|}

== Stratum Yearly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Zone ID|| ||
|-
| 5||Patch ID|| ||
|-
| 6||Stratum ID|| ||
|-
| 7||Net Photosynthesis||kgC/m2||psn
|-
| 8||Mean Leaf Water Potential||mPa||lwp
|}

Output Files

2010-07-16T18:53:24Z

Dgroulx: /* Stratum Monthly */

== Basin Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| || ||
|-
| 2||Month|| || ||
|-
| 3||Year|| || ||
|-
| 4||Basin ID|| || ||
|-
| 5||Rain Throughfall||mm||pot_surface_infil||
|-
| 6||Snow Throughfall||mm||snow_thr||
|-
| 7||Saturation Deficit-depth||mm of depth||sat_def_z||
|-
| 8||Saturation Deficit-volume||mm of water||sat_def||
|-
| 8||Rooting Zone Storage||mm of water||rz_storage||
|-
| 9||Unsaturated Storage||mm||unsat_stor||
|-
| 10||Unsaturated Drainage||mm||unsat_drain||
|-
| 11||Capillary Rise||mm||cap||
|-
| 12||Evaporation||mm||evap||
|-
| 13||Snowpack Depth||mm||snow||
|-
| 14||Transpiration||mm||trans||
|-
| 15||Baseflow||mm||baseflow||
|-
| 20||Return Flow||mm||return||
|-
| 17||Total Stream Outflow||mm||streamflow||
|-
| 18||Net Photosynthesis||kgC/m2||psn||
|-
| 19||Leaf Area Index||m2/m2||lai||
|-
| 20||Groundwater Output||mm||gw.Qout||
|-
| 21||Groundwater Nitrate Output||mm||gw.Nout||
|-
| 22||Groundwater Store||mm||gw.storage||rhessys5.10.5
|-
| 23||Groundwater Nitrate Store||mm||gw.NO3||rhessys5.10.5
|-
| 24||Detention Store||mm||detention_store||rhessys5.10.10
|-
| 25||Percent Saturated Area||m2/m2||%sat_area||rhessys5.10.10
|-
| 26||Litter Store||m2/m2||litter_store||rhessys5.10.12
|-
| 27||Percent Snow Cover||m2/m2||%snow_cover||rhessys5.10.12
|}

== Basin Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Gross Photosynthesis||gC/m2||gpsn
|-
| 6||Plant Maintenance Respiration||mC/m2||plant_resp
|-
| 7||Soil Respiration||gC/m2/day||soil_resp||rhessys5.10.11
|-
| 8||Nitrate N||gN/m2||nitrate
|-
| 9||Mineralized N||gN/m2||sminn
|-
| 10||Plant C||kgC/m2||plantc
|-
| 11||Plant N||kgN/m2||plantn
|-
| 12||Litter C||kgC/m2||litrc
|-
| 13||Litter N||kgN/m2||litrn
|-
| 14||Soil C||kgC/m2||soilc
|-
| 15||Soil N||kgN/m2||soiln
|-
| 16||Streamflow Nitrate||gN/m2/day||streamflow_NO3
|-
| 17||Denitrification||gN/m2/day||denitrif
|-
| 18||Nitrification||gN/m2/day||nitrif
|-
| 19||Dissolved Organic Carbon loss||gC/m2/day||DOC
|-
| 20||Dissolved Organic Nitrogen loss||gN/m2/day||DON
|}

== Basin Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Total Stream Outflow||mm||streamflow
|-
| 5||Nitrate to Stream||gN/m2||streamflow_NO3
|-
| 6||Denitrification||gN/m2||denitrif
|-
| 7||Dissolved Organic Carbon loss||gC/m2||DOC
|-
| 8||Dissolved Organic Nitrogen loss||gN/m2||DON
|-
| 9||Evapotranspiration||mm/m2||et
|-
| 10||Net Photosynthesis||gC/m2||psn
|-
| 11||Leaf Area Index||m2/m2||lai
|-
| 12||Nitrification||gN/m2||nitrif
|-
| 13||Mineralized Nitrate||gN/m2||mineralized
|-
| 14||Vegetation Nitrogen Uptake||gN/m2||uptake
|}

== Basin Yearly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Total Stream Outflow||mm||streamflow
|-
| 4||Nitrate to Stream||gN/m2||streamflow_NO3
|-
| 5||Denitrification||gN/m2||denitrif
|-
| 6||Dissolved Organic Carbon loss||gC/m2||DOC
|-
| 7||Dissolved Organic Nitrogen loss||gN/m2||DON
|-
| 8||Evapotranspiration||mm/m2||et
|-
| 9||Net Photosynthesis||gC/m2||psn
|-
| 10||Average Leaf Area Index||m2/m2||lai
|-
| 11||Nitrification||gN/m2||nitrif
|-
| 12||Mineralized N||gN/m2||mineralized
|-
| 13||Vegetation Uptake||gN/m2||uptake
|-
| 14||Number Threshold||?||num_thresh
|}

== Basin Yearly Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Year|| || ||rhessys5.10.5
|-
| 2||Basin ID|| || ||rhessys5.10.5
|-
| 3||Gross Photosynthesis||gC/m2||gpsn||rhessys5.10.5
|-
| 4||Plant Respiration||mC/m2||plantresp||rhessys5.10.5
|-
| 5||New Carbon||mC/m2||newC||rhessys5.10.5
|-
| 6||?Soilhr?||??||soilhr||rhessys5.10.5
|-
| 7||?Streamflow Nitrate?||??||strN||rhessys5.10.5
|-
| 8||Denitrification||gN/m2||denitrif||rhessys5.10.5
|-
|
|}

== Hillslope Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Rain Throughfall||mm||rain_thr
|-
| 7||Snow Throughfall||mm||snow_thr
|-
| 8||Saturation Deficit||mm of depth||sat_def_z
|-
| 9||Saturation Deficit||mm of water||sat_def
|-
| 10||Unsaturated Storage||mm||unsat_stor
|-
| 11||Unsaturated Drainage||mm||unsat_drain
|-
| 12||Capillary Rise||mm||cap
|-
| 13||Evaporation||mm||evap
|-
| 14||Snowpack Depth||mm||snow
|-
| 15||Transpiration||mm||trans
|-
| 16||Baseflow||mm||baseflow
|-
| 17||Return Flow||mm||return
|-
| 18||Total Stream Outflow||mm||streamflow
|-
| 19||Net Photosynthesis||kgC/m2||psn
|-
| 20||Leaf Area Index||m2/m2||lai
|-
| 21||Groundwater Output||mm||gw.Qout||rhessys5.10.5
|-
| 22||Groundwater Nitrate Output||mm||gw.Nout||rhessys5.10.5
|-
| 23||Groundwater Store||mm||gw.storage||rhessys5.10.5
|-
| 24||Groundwater Nitrate Store||mm||gw.N03||rhessys5.10.5
|}

== Hillslope Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Gross Photosynthesis||gC/m2||gpsn
|-
| 7||Maint Respiration||mC/m2||resp
|-
| 8||Nitrate N||gN/m2||nitrate
|-
| 9||Mineralized N||gN/m2||sminn
|-
| 10||Plant C||kgC/m2||plantc
|-
| 11||Plant N||kgN/m2||plantn
|-
| 12||Litter C||kgC/m2||litrc
|-
| 13||Litter N||kgN/m2||litrn
|-
| 14||Soil C||kgC/m2||soilc
|-
| 15||Soil N||kgN/m2||soiln
|-
| 16||Streamflow Nitrate||gN/m2/day||streamflow_NO3
|-
| 17||Streamflow||mm/day||streamflow
|-
| 18||Denitrification||gN/m2/day||denitrif
|-
| 19||Nitrification||gN/m2/day||nitrif
|-
| 20||Dissolved Organic Carbon loss||gC/m2/day||DOC
|-
| 21||Dissolved Organic Nitrogen loss||gN/m2/day||DON
|-
|
|}

== Hillslope Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| || ||rhessys5.10.7
|-
| 2||Year|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Streamflow||mm||streamflow
|-
| 5||Streamflow Nitrate||gN/m2/day||streamflow_N03
|-
| 6||Denitrification||gN/m2/day||denitrif
|-
| 7||Dissolved Organic Carbon Loss||gC/m2/day||DOC
|-
| 8||Dissolved Organic Nitrogen Loss||gN/m2/day||DON
|-
| 9||Evapotranspiration||mm/m2||et
|-
| 10||Net Photosynthesis||gC/m2||psn
|-
| 11||Leaf Area Index||m2/m2||lai
|-
| 12||Nitrification||gN/m2||nitrif
|-
| 13||Mineralized N||gN/m2||mineralized
|-
| 14||Vegetation Uptake||gN/m2||uptake
|}

== Hillslope Yearly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| || ||rhessys5.10.7
|-
| 2||Hillslope ID|| ||
|-
| 3||Streamflow||mm||streamflow
|-
| 4||Nitrate to Stream||gN/m2||streamflow_N03
|-
| 5||Denitrification||gN/m2||denitrif
|-
| 6||Dissolved Organic Carbon loss||gC/m2||DOC
|-
| 7||Dissolved Organic Nitrogen loss||gN/m2||DON
|-
| 8||Evapotranspiration||mm/m2||et
|-
| 9||Net Photosynthesis||gC/m2||psn
|-
| 10||Mineralized N||gN/m2||mineralized
|-
| 11||Vegetation Uptake||gN/m2||uptake
|}

== Zone Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Rainfall||mm||rain
|-
| 8||Snowfall||mm||snow
|-
| 9||Daytime Mean Air Temperature||C||tday
|-
| 10||Average Daily Temperature||C||tavg
|-
| 11||Vapour Pressure Deficit||Pa||vpd
|-
| 12||Direct Radiation||KJ/m2||Kdown_direct
|-
| 13||Diffuse Radiation||KJ/m2||Kdown_diffuse
|-
| 14||Direct PAR Radiation||KJ/m2||PAR_direct
|-
| 15||Diffuse PAR Radiation||KJ/m2||PAR_diffuse
|}

== Zone Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Hillslope ID|| ||
|-
| 5||Zone ID|| ||
|-
| 6||Precipitation||mm||precip
|-
| 7||Direct Radiation||KJ/m2||K_direct
|-
| 8||Diffuse Radiation||KJ/m2||K_diffuse
|-
| 9||Average Max Daily Temperature||C||tmax
|-
| 10||Average Min Daily Temperature||C||tmin
|}

== Patch Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Rain Throughfall||mm||rain_thr
|-
| 9||Detention Store||mm||detention_store||rhessys5.10.10
|-
| 10||Saturation Deficit (depth)||mm of depth||sat_def_z
|-
| 11||Saturation Deficit (water)||mm of water||sat_def
|-
| 12||Unsaturated Storage||mm||unsat_stor
|-
| 13||Unsaturated Drainage||mm||unsat_drain
|-
| 14||Capillary Rise||mm||cap
|-
| 15||Return Flow||mm||return
|-
| 16||Evaporation||mm||evap
|-
| 17||Snowpack Depth||mm||snow
|-
| 18||Transpiration||mm||trans
|-
| 19||Subsurface Flow to Stream||mm||Qin||rhessys5.10.9
|-
| 20||Subsurface Flow to Stream||mm||Qout||rhessys5.10.9
|-
| 21||Net Photosynthesis||kgC/m2||psn
|-
| 22||Rooting Zone Saturation||?||root_zone.S
|-
| 23||Litter Rain Stored||mm||litter.rain_stor||rhessys5.10.10
|-
| 24||Litter Percent Saturation||m2/m2 ?||litter.S||rhessys5.10.9
|}

== Patch Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Leaf Area Index||m2/m2||lai
|-
| 9||Plant C||kgC/m2||plantc
|-
| 10||Net Photosynthesis||gC/m2||net_psn
|-
| 11||Plant Respiration||gC/m2/day||plant_resp||rhessys5.10.11
|-
| 12||Soil Respiration||gC/m2/day||soil_resp||rhessys5.10.11
|-
| 13||Labile Litter C||kgC/m2||litr1c
|-
| 14||Cellulose Litter C||kgC/m2||litr2c
|-
| 15||Shielded Cellulose Litter C||kgC/m2||litr3c
|-
| 16||Lignan Litter C||kgC/m2||litr4c
|-
| 17||Litter Rain Capacity||mm||lit.rain_cap||rhessys5.10.10
|-
| 18||Fast Soil C||kgC/m2||soil1c
|-
| 19||Medium Soil C||kgC/m2||soil2c
|-
| 20||Slow Soil C||kgC/m2||soil3c
|-
| 21||Recalcitrant Soil C||kgC/m2||soil4c
|-
| 22||Denitrification||gN/m2||denitrif
|-
| 23||Net Nitrate Flux (+in)||gN/m2||netleach
|-
| 24||Soil Nitrate||gN/m2||soilNO3
|-
| 25||Streamflow N||gN/m2||streamN03
|-
| 26||Surface N||gN/m2||surfaceN03
|-
| 27||Canopy Height||m||height
|-
| 28||Nitrogen Uptake||??||N-uptake
|-
| 29||Area||cells||area
|}

== Patch Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Hillslope ID|| ||
|-
| 5||Zone ID|| ||
|-
| 6||Patch ID|| ||
|-
| 7||Net Nitrate Flux (+in)||gN/m2||leach
|-
| 8||Denitrification||gN/m2/month||denitrif
|-
| 9||Average Soil Moisture Deficit||mm||soil_moist_deficit
|-
| 10||Evapotranspiration||mm/m2/month||et
|-
| 11||Net Photosynthesis||gC/m2/month||psn
|-
| 12||Dissolved Organic Carbon loss||gC/m2/month||DOC
|-
| 13||Dissolved Organic Nitrogen loss||gN/m2/month||DON
|-
| 14||Average LAI||m2/m2||lai
|-
| 15||Nitrification||gN/m2/month||nitrif
|-
| 16||Mineralized N||gN/m2/month||mineralized
|-
| 17||Vegetation Uptake||gN/m2/month||uptake
|-
| 18||Theta||0-100 percent||theta
|}

== Patch Yearly ==

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Zone ID|| ||
|-
| 5||Patch ID|| ||
|-
| 6||Number of Days Below Sat. Threshold|| ||num_threshold_sat_def
|-
| 7||Net Nitrate Flux (+in)||gN/m2/year||leach
|-
| 8||Denitrification||gN/m2/year||denitrif
|-
| 9||Dissolved Organic Carbon loss||gC/m2/year||DOC_loss
|-
| 10||Dissolved Organic Nitrogen loss||gN/m2/year||DON_loss
|-
| 11||Net Photosynthesis||gC/m2||psn
|-
| 12||Evapotranspiration||mm/m2/year||et
|-
| 13||Maximum Leaf Area Index||m2/m2/year||lai
|-
| 14||Nitrification||gN/m2/year||nitrif
|-
| 15||Mineralized N||gN/m2year||mineralized
|-
| 16||Vegetation Uptake||gN/m2/year||uptake
|-
| 17||Theta||0-100 percent||theta
|}

== Patch Yearly Growth ==

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Zone ID|| ||
|-
| 5||Patch ID|| ||
|-
| 6||Litter C||kgC/m2||litter_c
|-
| 7||Soil C||kgC/m2/year||soil_c
|-
| 8||Litter N||kgN/m2/year||litter_n
|-
| 9||Soil N||kgN/m2/year||soil_n
|-
| 10||Soil Nitrate||gN/m2/year||nitrate
|-
| 11||Mineralized N||gN/m2||Sminn
|}

== Stratum Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Stratum ID|| ||
|-
| 9||Leaf Area Index||m2/m2||lai
|-
| 10||Evaporation||mm||evap
|-
| 11||APAR Radiation||KJ/m2||APAR_direct
|-
| 12||APAR Radiation||KJ/m2||APAR_diffuse
|-
| 13||Sublimation||mm||sublim
|-
| 14||Transpiration||mm||trans
|-
| 15||Aerodynamic Conductance||mm/s||ga
|-
| 16||Surface (non-vascular) Conductance||m/s||gsurf
|-
| 17||Canopy Conductance||mm/s||gs
|-
| 18||??||??||?psi?||rhessys5.10.10
|-
| 19||Respiration||kgC/m2||leaf_day_mr
|-
| 20||Net Photosynthesis||gC/m2||psn_to_cpool
|-
| 21||Rain Interception Storage||mm||rain_stored
|-
| 22||Snow Interception Storage||mm||snow_stored
|-
| 23||Rooting Zone Saturation||??||rootzone.S
|}

== Stratum Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Stratum ID|| ||
|-
| 9||Leaf Area Index||m2/m2||proj_lai
|-
| 10||Leaf C||gN/m2||leafc
|-
| 11||Dead Leaf C||gN/m2||dead_leafc
|-
| 12||Fine Root C||gN/m2||frootc
|-
| 13||Live Stem C||gN/m2||live_stemc
|-
| 14||Leaf C Store||gN/m2||leafc_store
|-
| 15||Dead Stem C||gN/m2||dead_stemc
|-
| 16||Live Coarse Root C||gN/m2||live_crootc
|-
| 17||Dead Coarse Root C||gN/m2||dead_crootc
|-
| 18||Coarse Woody Debris C||gN/m2||cwdc
|-
| 19||Maint Respiration||gC/m2||mresp
|-
| 20||Growth Respiration||gC/m2||gresp
|-
| 21||Net Photosynthesis||gC/m2||psn_to_cpool
|-
| 22||Stand Age||days||age||rhessys5.10.9
|}

== Stratum Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Hillslope ID|| ||
|-
| 5||Zone ID|| ||
|-
| 6||Patch ID|| ||
|-
| 7||Stratum ID|| ||
|-
| 8||Leaf Area Index||m2/m2||lai
|-
| 9||Net Photosynthesis||gC/m2||psn
|-
| 10||Mean Leaf Water Potential||mPa||lwp
|}

== Stratum Yearly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Zone ID|| ||
|-
| 5||Patch ID|| ||
|-
| 6||Stratum ID|| ||
|-
| 7||Net Photosynthesis||kgC/m2||psn
|-
| 8||Mean Leaf Water Potential||mPa||lwp
|}

Output Files

2010-07-16T18:53:14Z

Dgroulx: /* Stratum Daily Growth */

== Basin Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| || ||
|-
| 2||Month|| || ||
|-
| 3||Year|| || ||
|-
| 4||Basin ID|| || ||
|-
| 5||Rain Throughfall||mm||pot_surface_infil||
|-
| 6||Snow Throughfall||mm||snow_thr||
|-
| 7||Saturation Deficit-depth||mm of depth||sat_def_z||
|-
| 8||Saturation Deficit-volume||mm of water||sat_def||
|-
| 8||Rooting Zone Storage||mm of water||rz_storage||
|-
| 9||Unsaturated Storage||mm||unsat_stor||
|-
| 10||Unsaturated Drainage||mm||unsat_drain||
|-
| 11||Capillary Rise||mm||cap||
|-
| 12||Evaporation||mm||evap||
|-
| 13||Snowpack Depth||mm||snow||
|-
| 14||Transpiration||mm||trans||
|-
| 15||Baseflow||mm||baseflow||
|-
| 20||Return Flow||mm||return||
|-
| 17||Total Stream Outflow||mm||streamflow||
|-
| 18||Net Photosynthesis||kgC/m2||psn||
|-
| 19||Leaf Area Index||m2/m2||lai||
|-
| 20||Groundwater Output||mm||gw.Qout||
|-
| 21||Groundwater Nitrate Output||mm||gw.Nout||
|-
| 22||Groundwater Store||mm||gw.storage||rhessys5.10.5
|-
| 23||Groundwater Nitrate Store||mm||gw.NO3||rhessys5.10.5
|-
| 24||Detention Store||mm||detention_store||rhessys5.10.10
|-
| 25||Percent Saturated Area||m2/m2||%sat_area||rhessys5.10.10
|-
| 26||Litter Store||m2/m2||litter_store||rhessys5.10.12
|-
| 27||Percent Snow Cover||m2/m2||%snow_cover||rhessys5.10.12
|}

== Basin Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Gross Photosynthesis||gC/m2||gpsn
|-
| 6||Plant Maintenance Respiration||mC/m2||plant_resp
|-
| 7||Soil Respiration||gC/m2/day||soil_resp||rhessys5.10.11
|-
| 8||Nitrate N||gN/m2||nitrate
|-
| 9||Mineralized N||gN/m2||sminn
|-
| 10||Plant C||kgC/m2||plantc
|-
| 11||Plant N||kgN/m2||plantn
|-
| 12||Litter C||kgC/m2||litrc
|-
| 13||Litter N||kgN/m2||litrn
|-
| 14||Soil C||kgC/m2||soilc
|-
| 15||Soil N||kgN/m2||soiln
|-
| 16||Streamflow Nitrate||gN/m2/day||streamflow_NO3
|-
| 17||Denitrification||gN/m2/day||denitrif
|-
| 18||Nitrification||gN/m2/day||nitrif
|-
| 19||Dissolved Organic Carbon loss||gC/m2/day||DOC
|-
| 20||Dissolved Organic Nitrogen loss||gN/m2/day||DON
|}

== Basin Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Total Stream Outflow||mm||streamflow
|-
| 5||Nitrate to Stream||gN/m2||streamflow_NO3
|-
| 6||Denitrification||gN/m2||denitrif
|-
| 7||Dissolved Organic Carbon loss||gC/m2||DOC
|-
| 8||Dissolved Organic Nitrogen loss||gN/m2||DON
|-
| 9||Evapotranspiration||mm/m2||et
|-
| 10||Net Photosynthesis||gC/m2||psn
|-
| 11||Leaf Area Index||m2/m2||lai
|-
| 12||Nitrification||gN/m2||nitrif
|-
| 13||Mineralized Nitrate||gN/m2||mineralized
|-
| 14||Vegetation Nitrogen Uptake||gN/m2||uptake
|}

== Basin Yearly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Total Stream Outflow||mm||streamflow
|-
| 4||Nitrate to Stream||gN/m2||streamflow_NO3
|-
| 5||Denitrification||gN/m2||denitrif
|-
| 6||Dissolved Organic Carbon loss||gC/m2||DOC
|-
| 7||Dissolved Organic Nitrogen loss||gN/m2||DON
|-
| 8||Evapotranspiration||mm/m2||et
|-
| 9||Net Photosynthesis||gC/m2||psn
|-
| 10||Average Leaf Area Index||m2/m2||lai
|-
| 11||Nitrification||gN/m2||nitrif
|-
| 12||Mineralized N||gN/m2||mineralized
|-
| 13||Vegetation Uptake||gN/m2||uptake
|-
| 14||Number Threshold||?||num_thresh
|}

== Basin Yearly Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Year|| || ||rhessys5.10.5
|-
| 2||Basin ID|| || ||rhessys5.10.5
|-
| 3||Gross Photosynthesis||gC/m2||gpsn||rhessys5.10.5
|-
| 4||Plant Respiration||mC/m2||plantresp||rhessys5.10.5
|-
| 5||New Carbon||mC/m2||newC||rhessys5.10.5
|-
| 6||?Soilhr?||??||soilhr||rhessys5.10.5
|-
| 7||?Streamflow Nitrate?||??||strN||rhessys5.10.5
|-
| 8||Denitrification||gN/m2||denitrif||rhessys5.10.5
|-
|
|}

== Hillslope Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Rain Throughfall||mm||rain_thr
|-
| 7||Snow Throughfall||mm||snow_thr
|-
| 8||Saturation Deficit||mm of depth||sat_def_z
|-
| 9||Saturation Deficit||mm of water||sat_def
|-
| 10||Unsaturated Storage||mm||unsat_stor
|-
| 11||Unsaturated Drainage||mm||unsat_drain
|-
| 12||Capillary Rise||mm||cap
|-
| 13||Evaporation||mm||evap
|-
| 14||Snowpack Depth||mm||snow
|-
| 15||Transpiration||mm||trans
|-
| 16||Baseflow||mm||baseflow
|-
| 17||Return Flow||mm||return
|-
| 18||Total Stream Outflow||mm||streamflow
|-
| 19||Net Photosynthesis||kgC/m2||psn
|-
| 20||Leaf Area Index||m2/m2||lai
|-
| 21||Groundwater Output||mm||gw.Qout||rhessys5.10.5
|-
| 22||Groundwater Nitrate Output||mm||gw.Nout||rhessys5.10.5
|-
| 23||Groundwater Store||mm||gw.storage||rhessys5.10.5
|-
| 24||Groundwater Nitrate Store||mm||gw.N03||rhessys5.10.5
|}

== Hillslope Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Gross Photosynthesis||gC/m2||gpsn
|-
| 7||Maint Respiration||mC/m2||resp
|-
| 8||Nitrate N||gN/m2||nitrate
|-
| 9||Mineralized N||gN/m2||sminn
|-
| 10||Plant C||kgC/m2||plantc
|-
| 11||Plant N||kgN/m2||plantn
|-
| 12||Litter C||kgC/m2||litrc
|-
| 13||Litter N||kgN/m2||litrn
|-
| 14||Soil C||kgC/m2||soilc
|-
| 15||Soil N||kgN/m2||soiln
|-
| 16||Streamflow Nitrate||gN/m2/day||streamflow_NO3
|-
| 17||Streamflow||mm/day||streamflow
|-
| 18||Denitrification||gN/m2/day||denitrif
|-
| 19||Nitrification||gN/m2/day||nitrif
|-
| 20||Dissolved Organic Carbon loss||gC/m2/day||DOC
|-
| 21||Dissolved Organic Nitrogen loss||gN/m2/day||DON
|-
|
|}

== Hillslope Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| || ||rhessys5.10.7
|-
| 2||Year|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Streamflow||mm||streamflow
|-
| 5||Streamflow Nitrate||gN/m2/day||streamflow_N03
|-
| 6||Denitrification||gN/m2/day||denitrif
|-
| 7||Dissolved Organic Carbon Loss||gC/m2/day||DOC
|-
| 8||Dissolved Organic Nitrogen Loss||gN/m2/day||DON
|-
| 9||Evapotranspiration||mm/m2||et
|-
| 10||Net Photosynthesis||gC/m2||psn
|-
| 11||Leaf Area Index||m2/m2||lai
|-
| 12||Nitrification||gN/m2||nitrif
|-
| 13||Mineralized N||gN/m2||mineralized
|-
| 14||Vegetation Uptake||gN/m2||uptake
|}

== Hillslope Yearly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| || ||rhessys5.10.7
|-
| 2||Hillslope ID|| ||
|-
| 3||Streamflow||mm||streamflow
|-
| 4||Nitrate to Stream||gN/m2||streamflow_N03
|-
| 5||Denitrification||gN/m2||denitrif
|-
| 6||Dissolved Organic Carbon loss||gC/m2||DOC
|-
| 7||Dissolved Organic Nitrogen loss||gN/m2||DON
|-
| 8||Evapotranspiration||mm/m2||et
|-
| 9||Net Photosynthesis||gC/m2||psn
|-
| 10||Mineralized N||gN/m2||mineralized
|-
| 11||Vegetation Uptake||gN/m2||uptake
|}

== Zone Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Rainfall||mm||rain
|-
| 8||Snowfall||mm||snow
|-
| 9||Daytime Mean Air Temperature||C||tday
|-
| 10||Average Daily Temperature||C||tavg
|-
| 11||Vapour Pressure Deficit||Pa||vpd
|-
| 12||Direct Radiation||KJ/m2||Kdown_direct
|-
| 13||Diffuse Radiation||KJ/m2||Kdown_diffuse
|-
| 14||Direct PAR Radiation||KJ/m2||PAR_direct
|-
| 15||Diffuse PAR Radiation||KJ/m2||PAR_diffuse
|}

== Zone Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Hillslope ID|| ||
|-
| 5||Zone ID|| ||
|-
| 6||Precipitation||mm||precip
|-
| 7||Direct Radiation||KJ/m2||K_direct
|-
| 8||Diffuse Radiation||KJ/m2||K_diffuse
|-
| 9||Average Max Daily Temperature||C||tmax
|-
| 10||Average Min Daily Temperature||C||tmin
|}

== Patch Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Rain Throughfall||mm||rain_thr
|-
| 9||Detention Store||mm||detention_store||rhessys5.10.10
|-
| 10||Saturation Deficit (depth)||mm of depth||sat_def_z
|-
| 11||Saturation Deficit (water)||mm of water||sat_def
|-
| 12||Unsaturated Storage||mm||unsat_stor
|-
| 13||Unsaturated Drainage||mm||unsat_drain
|-
| 14||Capillary Rise||mm||cap
|-
| 15||Return Flow||mm||return
|-
| 16||Evaporation||mm||evap
|-
| 17||Snowpack Depth||mm||snow
|-
| 18||Transpiration||mm||trans
|-
| 19||Subsurface Flow to Stream||mm||Qin||rhessys5.10.9
|-
| 20||Subsurface Flow to Stream||mm||Qout||rhessys5.10.9
|-
| 21||Net Photosynthesis||kgC/m2||psn
|-
| 22||Rooting Zone Saturation||?||root_zone.S
|-
| 23||Litter Rain Stored||mm||litter.rain_stor||rhessys5.10.10
|-
| 24||Litter Percent Saturation||m2/m2 ?||litter.S||rhessys5.10.9
|}

== Patch Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Leaf Area Index||m2/m2||lai
|-
| 9||Plant C||kgC/m2||plantc
|-
| 10||Net Photosynthesis||gC/m2||net_psn
|-
| 11||Plant Respiration||gC/m2/day||plant_resp||rhessys5.10.11
|-
| 12||Soil Respiration||gC/m2/day||soil_resp||rhessys5.10.11
|-
| 13||Labile Litter C||kgC/m2||litr1c
|-
| 14||Cellulose Litter C||kgC/m2||litr2c
|-
| 15||Shielded Cellulose Litter C||kgC/m2||litr3c
|-
| 16||Lignan Litter C||kgC/m2||litr4c
|-
| 17||Litter Rain Capacity||mm||lit.rain_cap||rhessys5.10.10
|-
| 18||Fast Soil C||kgC/m2||soil1c
|-
| 19||Medium Soil C||kgC/m2||soil2c
|-
| 20||Slow Soil C||kgC/m2||soil3c
|-
| 21||Recalcitrant Soil C||kgC/m2||soil4c
|-
| 22||Denitrification||gN/m2||denitrif
|-
| 23||Net Nitrate Flux (+in)||gN/m2||netleach
|-
| 24||Soil Nitrate||gN/m2||soilNO3
|-
| 25||Streamflow N||gN/m2||streamN03
|-
| 26||Surface N||gN/m2||surfaceN03
|-
| 27||Canopy Height||m||height
|-
| 28||Nitrogen Uptake||??||N-uptake
|-
| 29||Area||cells||area
|}

== Patch Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Hillslope ID|| ||
|-
| 5||Zone ID|| ||
|-
| 6||Patch ID|| ||
|-
| 7||Net Nitrate Flux (+in)||gN/m2||leach
|-
| 8||Denitrification||gN/m2/month||denitrif
|-
| 9||Average Soil Moisture Deficit||mm||soil_moist_deficit
|-
| 10||Evapotranspiration||mm/m2/month||et
|-
| 11||Net Photosynthesis||gC/m2/month||psn
|-
| 12||Dissolved Organic Carbon loss||gC/m2/month||DOC
|-
| 13||Dissolved Organic Nitrogen loss||gN/m2/month||DON
|-
| 14||Average LAI||m2/m2||lai
|-
| 15||Nitrification||gN/m2/month||nitrif
|-
| 16||Mineralized N||gN/m2/month||mineralized
|-
| 17||Vegetation Uptake||gN/m2/month||uptake
|-
| 18||Theta||0-100 percent||theta
|}

== Patch Yearly ==

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Zone ID|| ||
|-
| 5||Patch ID|| ||
|-
| 6||Number of Days Below Sat. Threshold|| ||num_threshold_sat_def
|-
| 7||Net Nitrate Flux (+in)||gN/m2/year||leach
|-
| 8||Denitrification||gN/m2/year||denitrif
|-
| 9||Dissolved Organic Carbon loss||gC/m2/year||DOC_loss
|-
| 10||Dissolved Organic Nitrogen loss||gN/m2/year||DON_loss
|-
| 11||Net Photosynthesis||gC/m2||psn
|-
| 12||Evapotranspiration||mm/m2/year||et
|-
| 13||Maximum Leaf Area Index||m2/m2/year||lai
|-
| 14||Nitrification||gN/m2/year||nitrif
|-
| 15||Mineralized N||gN/m2year||mineralized
|-
| 16||Vegetation Uptake||gN/m2/year||uptake
|-
| 17||Theta||0-100 percent||theta
|}

== Patch Yearly Growth ==

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Zone ID|| ||
|-
| 5||Patch ID|| ||
|-
| 6||Litter C||kgC/m2||litter_c
|-
| 7||Soil C||kgC/m2/year||soil_c
|-
| 8||Litter N||kgN/m2/year||litter_n
|-
| 9||Soil N||kgN/m2/year||soil_n
|-
| 10||Soil Nitrate||gN/m2/year||nitrate
|-
| 11||Mineralized N||gN/m2||Sminn
|}

== Stratum Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Stratum ID|| ||
|-
| 9||Leaf Area Index||m2/m2||lai
|-
| 10||Evaporation||mm||evap
|-
| 11||APAR Radiation||KJ/m2||APAR_direct
|-
| 12||APAR Radiation||KJ/m2||APAR_diffuse
|-
| 13||Sublimation||mm||sublim
|-
| 14||Transpiration||mm||trans
|-
| 15||Aerodynamic Conductance||mm/s||ga
|-
| 16||Surface (non-vascular) Conductance||m/s||gsurf
|-
| 17||Canopy Conductance||mm/s||gs
|-
| 18||??||??||?psi?||rhessys5.10.10
|-
| 19||Respiration||kgC/m2||leaf_day_mr
|-
| 20||Net Photosynthesis||gC/m2||psn_to_cpool
|-
| 21||Rain Interception Storage||mm||rain_stored
|-
| 22||Snow Interception Storage||mm||snow_stored
|-
| 23||Rooting Zone Saturation||??||rootzone.S
|}

== Stratum Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Stratum ID|| ||
|-
| 9||Leaf Area Index||m2/m2||proj_lai
|-
| 10||Leaf C||gN/m2||leafc
|-
| 11||Dead Leaf C||gN/m2||dead_leafc
|-
| 12||Fine Root C||gN/m2||frootc
|-
| 13||Live Stem C||gN/m2||live_stemc
|-
| 14||Leaf C Store||gN/m2||leafc_store
|-
| 15||Dead Stem C||gN/m2||dead_stemc
|-
| 16||Live Coarse Root C||gN/m2||live_crootc
|-
| 17||Dead Coarse Root C||gN/m2||dead_crootc
|-
| 18||Coarse Woody Debris C||gN/m2||cwdc
|-
| 19||Maint Respiration||gC/m2||mresp
|-
| 20||Growth Respiration||gC/m2||gresp
|-
| 21||Net Photosynthesis||gC/m2||psn_to_cpool
|-
| 22||Stand Age||days||age||rhessys5.10.9
|}

== Stratum Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Hillslope ID|| ||
|-
| 5||Zone ID|| ||
|-
| 6||Patch ID|| ||
|-
| 7||Stratum ID|| ||
|-
| 8||Leaf Area Index||m2/m2||lai
|-
| 9||Net Photosynthesis||gC/m2||psn
|-
| 10||Mean Leaf Water Potential||mPa||lwp
|}

== Stratum Yearly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Zone ID|| ||
|-
| 5||Patch ID|| ||
|-
| 6||Stratum ID|| ||
|-
| 7||Net Photosynthesis||kgC/m2||psn
|-
| 8||Mean Leaf Water Potential||mPa||lwp
|}

Output Files

2010-07-16T18:53:06Z

Dgroulx: /* Stratum Daily */

== Basin Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| || ||
|-
| 2||Month|| || ||
|-
| 3||Year|| || ||
|-
| 4||Basin ID|| || ||
|-
| 5||Rain Throughfall||mm||pot_surface_infil||
|-
| 6||Snow Throughfall||mm||snow_thr||
|-
| 7||Saturation Deficit-depth||mm of depth||sat_def_z||
|-
| 8||Saturation Deficit-volume||mm of water||sat_def||
|-
| 8||Rooting Zone Storage||mm of water||rz_storage||
|-
| 9||Unsaturated Storage||mm||unsat_stor||
|-
| 10||Unsaturated Drainage||mm||unsat_drain||
|-
| 11||Capillary Rise||mm||cap||
|-
| 12||Evaporation||mm||evap||
|-
| 13||Snowpack Depth||mm||snow||
|-
| 14||Transpiration||mm||trans||
|-
| 15||Baseflow||mm||baseflow||
|-
| 20||Return Flow||mm||return||
|-
| 17||Total Stream Outflow||mm||streamflow||
|-
| 18||Net Photosynthesis||kgC/m2||psn||
|-
| 19||Leaf Area Index||m2/m2||lai||
|-
| 20||Groundwater Output||mm||gw.Qout||
|-
| 21||Groundwater Nitrate Output||mm||gw.Nout||
|-
| 22||Groundwater Store||mm||gw.storage||rhessys5.10.5
|-
| 23||Groundwater Nitrate Store||mm||gw.NO3||rhessys5.10.5
|-
| 24||Detention Store||mm||detention_store||rhessys5.10.10
|-
| 25||Percent Saturated Area||m2/m2||%sat_area||rhessys5.10.10
|-
| 26||Litter Store||m2/m2||litter_store||rhessys5.10.12
|-
| 27||Percent Snow Cover||m2/m2||%snow_cover||rhessys5.10.12
|}

== Basin Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Gross Photosynthesis||gC/m2||gpsn
|-
| 6||Plant Maintenance Respiration||mC/m2||plant_resp
|-
| 7||Soil Respiration||gC/m2/day||soil_resp||rhessys5.10.11
|-
| 8||Nitrate N||gN/m2||nitrate
|-
| 9||Mineralized N||gN/m2||sminn
|-
| 10||Plant C||kgC/m2||plantc
|-
| 11||Plant N||kgN/m2||plantn
|-
| 12||Litter C||kgC/m2||litrc
|-
| 13||Litter N||kgN/m2||litrn
|-
| 14||Soil C||kgC/m2||soilc
|-
| 15||Soil N||kgN/m2||soiln
|-
| 16||Streamflow Nitrate||gN/m2/day||streamflow_NO3
|-
| 17||Denitrification||gN/m2/day||denitrif
|-
| 18||Nitrification||gN/m2/day||nitrif
|-
| 19||Dissolved Organic Carbon loss||gC/m2/day||DOC
|-
| 20||Dissolved Organic Nitrogen loss||gN/m2/day||DON
|}

== Basin Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Total Stream Outflow||mm||streamflow
|-
| 5||Nitrate to Stream||gN/m2||streamflow_NO3
|-
| 6||Denitrification||gN/m2||denitrif
|-
| 7||Dissolved Organic Carbon loss||gC/m2||DOC
|-
| 8||Dissolved Organic Nitrogen loss||gN/m2||DON
|-
| 9||Evapotranspiration||mm/m2||et
|-
| 10||Net Photosynthesis||gC/m2||psn
|-
| 11||Leaf Area Index||m2/m2||lai
|-
| 12||Nitrification||gN/m2||nitrif
|-
| 13||Mineralized Nitrate||gN/m2||mineralized
|-
| 14||Vegetation Nitrogen Uptake||gN/m2||uptake
|}

== Basin Yearly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Total Stream Outflow||mm||streamflow
|-
| 4||Nitrate to Stream||gN/m2||streamflow_NO3
|-
| 5||Denitrification||gN/m2||denitrif
|-
| 6||Dissolved Organic Carbon loss||gC/m2||DOC
|-
| 7||Dissolved Organic Nitrogen loss||gN/m2||DON
|-
| 8||Evapotranspiration||mm/m2||et
|-
| 9||Net Photosynthesis||gC/m2||psn
|-
| 10||Average Leaf Area Index||m2/m2||lai
|-
| 11||Nitrification||gN/m2||nitrif
|-
| 12||Mineralized N||gN/m2||mineralized
|-
| 13||Vegetation Uptake||gN/m2||uptake
|-
| 14||Number Threshold||?||num_thresh
|}

== Basin Yearly Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Year|| || ||rhessys5.10.5
|-
| 2||Basin ID|| || ||rhessys5.10.5
|-
| 3||Gross Photosynthesis||gC/m2||gpsn||rhessys5.10.5
|-
| 4||Plant Respiration||mC/m2||plantresp||rhessys5.10.5
|-
| 5||New Carbon||mC/m2||newC||rhessys5.10.5
|-
| 6||?Soilhr?||??||soilhr||rhessys5.10.5
|-
| 7||?Streamflow Nitrate?||??||strN||rhessys5.10.5
|-
| 8||Denitrification||gN/m2||denitrif||rhessys5.10.5
|-
|
|}

== Hillslope Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Rain Throughfall||mm||rain_thr
|-
| 7||Snow Throughfall||mm||snow_thr
|-
| 8||Saturation Deficit||mm of depth||sat_def_z
|-
| 9||Saturation Deficit||mm of water||sat_def
|-
| 10||Unsaturated Storage||mm||unsat_stor
|-
| 11||Unsaturated Drainage||mm||unsat_drain
|-
| 12||Capillary Rise||mm||cap
|-
| 13||Evaporation||mm||evap
|-
| 14||Snowpack Depth||mm||snow
|-
| 15||Transpiration||mm||trans
|-
| 16||Baseflow||mm||baseflow
|-
| 17||Return Flow||mm||return
|-
| 18||Total Stream Outflow||mm||streamflow
|-
| 19||Net Photosynthesis||kgC/m2||psn
|-
| 20||Leaf Area Index||m2/m2||lai
|-
| 21||Groundwater Output||mm||gw.Qout||rhessys5.10.5
|-
| 22||Groundwater Nitrate Output||mm||gw.Nout||rhessys5.10.5
|-
| 23||Groundwater Store||mm||gw.storage||rhessys5.10.5
|-
| 24||Groundwater Nitrate Store||mm||gw.N03||rhessys5.10.5
|}

== Hillslope Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Gross Photosynthesis||gC/m2||gpsn
|-
| 7||Maint Respiration||mC/m2||resp
|-
| 8||Nitrate N||gN/m2||nitrate
|-
| 9||Mineralized N||gN/m2||sminn
|-
| 10||Plant C||kgC/m2||plantc
|-
| 11||Plant N||kgN/m2||plantn
|-
| 12||Litter C||kgC/m2||litrc
|-
| 13||Litter N||kgN/m2||litrn
|-
| 14||Soil C||kgC/m2||soilc
|-
| 15||Soil N||kgN/m2||soiln
|-
| 16||Streamflow Nitrate||gN/m2/day||streamflow_NO3
|-
| 17||Streamflow||mm/day||streamflow
|-
| 18||Denitrification||gN/m2/day||denitrif
|-
| 19||Nitrification||gN/m2/day||nitrif
|-
| 20||Dissolved Organic Carbon loss||gC/m2/day||DOC
|-
| 21||Dissolved Organic Nitrogen loss||gN/m2/day||DON
|-
|
|}

== Hillslope Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| || ||rhessys5.10.7
|-
| 2||Year|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Streamflow||mm||streamflow
|-
| 5||Streamflow Nitrate||gN/m2/day||streamflow_N03
|-
| 6||Denitrification||gN/m2/day||denitrif
|-
| 7||Dissolved Organic Carbon Loss||gC/m2/day||DOC
|-
| 8||Dissolved Organic Nitrogen Loss||gN/m2/day||DON
|-
| 9||Evapotranspiration||mm/m2||et
|-
| 10||Net Photosynthesis||gC/m2||psn
|-
| 11||Leaf Area Index||m2/m2||lai
|-
| 12||Nitrification||gN/m2||nitrif
|-
| 13||Mineralized N||gN/m2||mineralized
|-
| 14||Vegetation Uptake||gN/m2||uptake
|}

== Hillslope Yearly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| || ||rhessys5.10.7
|-
| 2||Hillslope ID|| ||
|-
| 3||Streamflow||mm||streamflow
|-
| 4||Nitrate to Stream||gN/m2||streamflow_N03
|-
| 5||Denitrification||gN/m2||denitrif
|-
| 6||Dissolved Organic Carbon loss||gC/m2||DOC
|-
| 7||Dissolved Organic Nitrogen loss||gN/m2||DON
|-
| 8||Evapotranspiration||mm/m2||et
|-
| 9||Net Photosynthesis||gC/m2||psn
|-
| 10||Mineralized N||gN/m2||mineralized
|-
| 11||Vegetation Uptake||gN/m2||uptake
|}

== Zone Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Rainfall||mm||rain
|-
| 8||Snowfall||mm||snow
|-
| 9||Daytime Mean Air Temperature||C||tday
|-
| 10||Average Daily Temperature||C||tavg
|-
| 11||Vapour Pressure Deficit||Pa||vpd
|-
| 12||Direct Radiation||KJ/m2||Kdown_direct
|-
| 13||Diffuse Radiation||KJ/m2||Kdown_diffuse
|-
| 14||Direct PAR Radiation||KJ/m2||PAR_direct
|-
| 15||Diffuse PAR Radiation||KJ/m2||PAR_diffuse
|}

== Zone Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Hillslope ID|| ||
|-
| 5||Zone ID|| ||
|-
| 6||Precipitation||mm||precip
|-
| 7||Direct Radiation||KJ/m2||K_direct
|-
| 8||Diffuse Radiation||KJ/m2||K_diffuse
|-
| 9||Average Max Daily Temperature||C||tmax
|-
| 10||Average Min Daily Temperature||C||tmin
|}

== Patch Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Rain Throughfall||mm||rain_thr
|-
| 9||Detention Store||mm||detention_store||rhessys5.10.10
|-
| 10||Saturation Deficit (depth)||mm of depth||sat_def_z
|-
| 11||Saturation Deficit (water)||mm of water||sat_def
|-
| 12||Unsaturated Storage||mm||unsat_stor
|-
| 13||Unsaturated Drainage||mm||unsat_drain
|-
| 14||Capillary Rise||mm||cap
|-
| 15||Return Flow||mm||return
|-
| 16||Evaporation||mm||evap
|-
| 17||Snowpack Depth||mm||snow
|-
| 18||Transpiration||mm||trans
|-
| 19||Subsurface Flow to Stream||mm||Qin||rhessys5.10.9
|-
| 20||Subsurface Flow to Stream||mm||Qout||rhessys5.10.9
|-
| 21||Net Photosynthesis||kgC/m2||psn
|-
| 22||Rooting Zone Saturation||?||root_zone.S
|-
| 23||Litter Rain Stored||mm||litter.rain_stor||rhessys5.10.10
|-
| 24||Litter Percent Saturation||m2/m2 ?||litter.S||rhessys5.10.9
|}

== Patch Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Leaf Area Index||m2/m2||lai
|-
| 9||Plant C||kgC/m2||plantc
|-
| 10||Net Photosynthesis||gC/m2||net_psn
|-
| 11||Plant Respiration||gC/m2/day||plant_resp||rhessys5.10.11
|-
| 12||Soil Respiration||gC/m2/day||soil_resp||rhessys5.10.11
|-
| 13||Labile Litter C||kgC/m2||litr1c
|-
| 14||Cellulose Litter C||kgC/m2||litr2c
|-
| 15||Shielded Cellulose Litter C||kgC/m2||litr3c
|-
| 16||Lignan Litter C||kgC/m2||litr4c
|-
| 17||Litter Rain Capacity||mm||lit.rain_cap||rhessys5.10.10
|-
| 18||Fast Soil C||kgC/m2||soil1c
|-
| 19||Medium Soil C||kgC/m2||soil2c
|-
| 20||Slow Soil C||kgC/m2||soil3c
|-
| 21||Recalcitrant Soil C||kgC/m2||soil4c
|-
| 22||Denitrification||gN/m2||denitrif
|-
| 23||Net Nitrate Flux (+in)||gN/m2||netleach
|-
| 24||Soil Nitrate||gN/m2||soilNO3
|-
| 25||Streamflow N||gN/m2||streamN03
|-
| 26||Surface N||gN/m2||surfaceN03
|-
| 27||Canopy Height||m||height
|-
| 28||Nitrogen Uptake||??||N-uptake
|-
| 29||Area||cells||area
|}

== Patch Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Hillslope ID|| ||
|-
| 5||Zone ID|| ||
|-
| 6||Patch ID|| ||
|-
| 7||Net Nitrate Flux (+in)||gN/m2||leach
|-
| 8||Denitrification||gN/m2/month||denitrif
|-
| 9||Average Soil Moisture Deficit||mm||soil_moist_deficit
|-
| 10||Evapotranspiration||mm/m2/month||et
|-
| 11||Net Photosynthesis||gC/m2/month||psn
|-
| 12||Dissolved Organic Carbon loss||gC/m2/month||DOC
|-
| 13||Dissolved Organic Nitrogen loss||gN/m2/month||DON
|-
| 14||Average LAI||m2/m2||lai
|-
| 15||Nitrification||gN/m2/month||nitrif
|-
| 16||Mineralized N||gN/m2/month||mineralized
|-
| 17||Vegetation Uptake||gN/m2/month||uptake
|-
| 18||Theta||0-100 percent||theta
|}

== Patch Yearly ==

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Zone ID|| ||
|-
| 5||Patch ID|| ||
|-
| 6||Number of Days Below Sat. Threshold|| ||num_threshold_sat_def
|-
| 7||Net Nitrate Flux (+in)||gN/m2/year||leach
|-
| 8||Denitrification||gN/m2/year||denitrif
|-
| 9||Dissolved Organic Carbon loss||gC/m2/year||DOC_loss
|-
| 10||Dissolved Organic Nitrogen loss||gN/m2/year||DON_loss
|-
| 11||Net Photosynthesis||gC/m2||psn
|-
| 12||Evapotranspiration||mm/m2/year||et
|-
| 13||Maximum Leaf Area Index||m2/m2/year||lai
|-
| 14||Nitrification||gN/m2/year||nitrif
|-
| 15||Mineralized N||gN/m2year||mineralized
|-
| 16||Vegetation Uptake||gN/m2/year||uptake
|-
| 17||Theta||0-100 percent||theta
|}

== Patch Yearly Growth ==

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Zone ID|| ||
|-
| 5||Patch ID|| ||
|-
| 6||Litter C||kgC/m2||litter_c
|-
| 7||Soil C||kgC/m2/year||soil_c
|-
| 8||Litter N||kgN/m2/year||litter_n
|-
| 9||Soil N||kgN/m2/year||soil_n
|-
| 10||Soil Nitrate||gN/m2/year||nitrate
|-
| 11||Mineralized N||gN/m2||Sminn
|}

== Stratum Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Stratum ID|| ||
|-
| 9||Leaf Area Index||m2/m2||lai
|-
| 10||Evaporation||mm||evap
|-
| 11||APAR Radiation||KJ/m2||APAR_direct
|-
| 12||APAR Radiation||KJ/m2||APAR_diffuse
|-
| 13||Sublimation||mm||sublim
|-
| 14||Transpiration||mm||trans
|-
| 15||Aerodynamic Conductance||mm/s||ga
|-
| 16||Surface (non-vascular) Conductance||m/s||gsurf
|-
| 17||Canopy Conductance||mm/s||gs
|-
| 18||??||??||?psi?||rhessys5.10.10
|-
| 19||Respiration||kgC/m2||leaf_day_mr
|-
| 20||Net Photosynthesis||gC/m2||psn_to_cpool
|-
| 21||Rain Interception Storage||mm||rain_stored
|-
| 22||Snow Interception Storage||mm||snow_stored
|-
| 23||Rooting Zone Saturation||??||rootzone.S
|}

== Stratum Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Stratum ID|| ||
|-
| 9||Leaf Area Index||m2/m2||proj_lai
|-
| 10||Leaf C||gN/m2||leafc
|-
| 11||Dead Leaf C||gN/m2||dead_leafc
|-
| 12||Fine Root C||gN/m2||frootc
|-
| 13||Live Stem C||gN/m2||live_stemc
|-
| 14||Leaf C Store||gN/m2||leafc_store
|-
| 15||Dead Stem C||gN/m2||dead_stemc
|-
| 16||Live Coarse Root C||gN/m2||live_crootc
|-
| 17||Dead Coarse Root C||gN/m2||dead_crootc
|-
| 18||Coarse Woody Debris C||gN/m2||cwdc
|-
| 19||Maint Respiration||gC/m2||mresp
|-
| 20||Growth Respiration||gC/m2||gresp
|-
| 21||Net Photosynthesis||gC/m2||psn_to_cpool
|-
| 22||Stand Age||days||age||rhessys5.10.9
|}

== Stratum Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Hillslope ID|| ||
|-
| 5||Zone ID|| ||
|-
| 6||Patch ID|| ||
|-
| 7||Stratum ID|| ||
|-
| 8||Leaf Area Index||m2/m2||lai
|-
| 9||Net Photosynthesis||gC/m2||psn
|-
| 10||Mean Leaf Water Potential||mPa||lwp
|}

== Stratum Yearly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Zone ID|| ||
|-
| 5||Patch ID|| ||
|-
| 6||Stratum ID|| ||
|-
| 7||Net Photosynthesis||kgC/m2||psn
|-
| 8||Mean Leaf Water Potential||mPa||lwp
|}

Output Files

2010-07-16T18:52:58Z

Dgroulx: /* Patch Yearly Growth */

== Basin Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| || ||
|-
| 2||Month|| || ||
|-
| 3||Year|| || ||
|-
| 4||Basin ID|| || ||
|-
| 5||Rain Throughfall||mm||pot_surface_infil||
|-
| 6||Snow Throughfall||mm||snow_thr||
|-
| 7||Saturation Deficit-depth||mm of depth||sat_def_z||
|-
| 8||Saturation Deficit-volume||mm of water||sat_def||
|-
| 8||Rooting Zone Storage||mm of water||rz_storage||
|-
| 9||Unsaturated Storage||mm||unsat_stor||
|-
| 10||Unsaturated Drainage||mm||unsat_drain||
|-
| 11||Capillary Rise||mm||cap||
|-
| 12||Evaporation||mm||evap||
|-
| 13||Snowpack Depth||mm||snow||
|-
| 14||Transpiration||mm||trans||
|-
| 15||Baseflow||mm||baseflow||
|-
| 20||Return Flow||mm||return||
|-
| 17||Total Stream Outflow||mm||streamflow||
|-
| 18||Net Photosynthesis||kgC/m2||psn||
|-
| 19||Leaf Area Index||m2/m2||lai||
|-
| 20||Groundwater Output||mm||gw.Qout||
|-
| 21||Groundwater Nitrate Output||mm||gw.Nout||
|-
| 22||Groundwater Store||mm||gw.storage||rhessys5.10.5
|-
| 23||Groundwater Nitrate Store||mm||gw.NO3||rhessys5.10.5
|-
| 24||Detention Store||mm||detention_store||rhessys5.10.10
|-
| 25||Percent Saturated Area||m2/m2||%sat_area||rhessys5.10.10
|-
| 26||Litter Store||m2/m2||litter_store||rhessys5.10.12
|-
| 27||Percent Snow Cover||m2/m2||%snow_cover||rhessys5.10.12
|}

== Basin Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Gross Photosynthesis||gC/m2||gpsn
|-
| 6||Plant Maintenance Respiration||mC/m2||plant_resp
|-
| 7||Soil Respiration||gC/m2/day||soil_resp||rhessys5.10.11
|-
| 8||Nitrate N||gN/m2||nitrate
|-
| 9||Mineralized N||gN/m2||sminn
|-
| 10||Plant C||kgC/m2||plantc
|-
| 11||Plant N||kgN/m2||plantn
|-
| 12||Litter C||kgC/m2||litrc
|-
| 13||Litter N||kgN/m2||litrn
|-
| 14||Soil C||kgC/m2||soilc
|-
| 15||Soil N||kgN/m2||soiln
|-
| 16||Streamflow Nitrate||gN/m2/day||streamflow_NO3
|-
| 17||Denitrification||gN/m2/day||denitrif
|-
| 18||Nitrification||gN/m2/day||nitrif
|-
| 19||Dissolved Organic Carbon loss||gC/m2/day||DOC
|-
| 20||Dissolved Organic Nitrogen loss||gN/m2/day||DON
|}

== Basin Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Total Stream Outflow||mm||streamflow
|-
| 5||Nitrate to Stream||gN/m2||streamflow_NO3
|-
| 6||Denitrification||gN/m2||denitrif
|-
| 7||Dissolved Organic Carbon loss||gC/m2||DOC
|-
| 8||Dissolved Organic Nitrogen loss||gN/m2||DON
|-
| 9||Evapotranspiration||mm/m2||et
|-
| 10||Net Photosynthesis||gC/m2||psn
|-
| 11||Leaf Area Index||m2/m2||lai
|-
| 12||Nitrification||gN/m2||nitrif
|-
| 13||Mineralized Nitrate||gN/m2||mineralized
|-
| 14||Vegetation Nitrogen Uptake||gN/m2||uptake
|}

== Basin Yearly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Total Stream Outflow||mm||streamflow
|-
| 4||Nitrate to Stream||gN/m2||streamflow_NO3
|-
| 5||Denitrification||gN/m2||denitrif
|-
| 6||Dissolved Organic Carbon loss||gC/m2||DOC
|-
| 7||Dissolved Organic Nitrogen loss||gN/m2||DON
|-
| 8||Evapotranspiration||mm/m2||et
|-
| 9||Net Photosynthesis||gC/m2||psn
|-
| 10||Average Leaf Area Index||m2/m2||lai
|-
| 11||Nitrification||gN/m2||nitrif
|-
| 12||Mineralized N||gN/m2||mineralized
|-
| 13||Vegetation Uptake||gN/m2||uptake
|-
| 14||Number Threshold||?||num_thresh
|}

== Basin Yearly Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Year|| || ||rhessys5.10.5
|-
| 2||Basin ID|| || ||rhessys5.10.5
|-
| 3||Gross Photosynthesis||gC/m2||gpsn||rhessys5.10.5
|-
| 4||Plant Respiration||mC/m2||plantresp||rhessys5.10.5
|-
| 5||New Carbon||mC/m2||newC||rhessys5.10.5
|-
| 6||?Soilhr?||??||soilhr||rhessys5.10.5
|-
| 7||?Streamflow Nitrate?||??||strN||rhessys5.10.5
|-
| 8||Denitrification||gN/m2||denitrif||rhessys5.10.5
|-
|
|}

== Hillslope Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Rain Throughfall||mm||rain_thr
|-
| 7||Snow Throughfall||mm||snow_thr
|-
| 8||Saturation Deficit||mm of depth||sat_def_z
|-
| 9||Saturation Deficit||mm of water||sat_def
|-
| 10||Unsaturated Storage||mm||unsat_stor
|-
| 11||Unsaturated Drainage||mm||unsat_drain
|-
| 12||Capillary Rise||mm||cap
|-
| 13||Evaporation||mm||evap
|-
| 14||Snowpack Depth||mm||snow
|-
| 15||Transpiration||mm||trans
|-
| 16||Baseflow||mm||baseflow
|-
| 17||Return Flow||mm||return
|-
| 18||Total Stream Outflow||mm||streamflow
|-
| 19||Net Photosynthesis||kgC/m2||psn
|-
| 20||Leaf Area Index||m2/m2||lai
|-
| 21||Groundwater Output||mm||gw.Qout||rhessys5.10.5
|-
| 22||Groundwater Nitrate Output||mm||gw.Nout||rhessys5.10.5
|-
| 23||Groundwater Store||mm||gw.storage||rhessys5.10.5
|-
| 24||Groundwater Nitrate Store||mm||gw.N03||rhessys5.10.5
|}

== Hillslope Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Gross Photosynthesis||gC/m2||gpsn
|-
| 7||Maint Respiration||mC/m2||resp
|-
| 8||Nitrate N||gN/m2||nitrate
|-
| 9||Mineralized N||gN/m2||sminn
|-
| 10||Plant C||kgC/m2||plantc
|-
| 11||Plant N||kgN/m2||plantn
|-
| 12||Litter C||kgC/m2||litrc
|-
| 13||Litter N||kgN/m2||litrn
|-
| 14||Soil C||kgC/m2||soilc
|-
| 15||Soil N||kgN/m2||soiln
|-
| 16||Streamflow Nitrate||gN/m2/day||streamflow_NO3
|-
| 17||Streamflow||mm/day||streamflow
|-
| 18||Denitrification||gN/m2/day||denitrif
|-
| 19||Nitrification||gN/m2/day||nitrif
|-
| 20||Dissolved Organic Carbon loss||gC/m2/day||DOC
|-
| 21||Dissolved Organic Nitrogen loss||gN/m2/day||DON
|-
|
|}

== Hillslope Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| || ||rhessys5.10.7
|-
| 2||Year|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Streamflow||mm||streamflow
|-
| 5||Streamflow Nitrate||gN/m2/day||streamflow_N03
|-
| 6||Denitrification||gN/m2/day||denitrif
|-
| 7||Dissolved Organic Carbon Loss||gC/m2/day||DOC
|-
| 8||Dissolved Organic Nitrogen Loss||gN/m2/day||DON
|-
| 9||Evapotranspiration||mm/m2||et
|-
| 10||Net Photosynthesis||gC/m2||psn
|-
| 11||Leaf Area Index||m2/m2||lai
|-
| 12||Nitrification||gN/m2||nitrif
|-
| 13||Mineralized N||gN/m2||mineralized
|-
| 14||Vegetation Uptake||gN/m2||uptake
|}

== Hillslope Yearly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| || ||rhessys5.10.7
|-
| 2||Hillslope ID|| ||
|-
| 3||Streamflow||mm||streamflow
|-
| 4||Nitrate to Stream||gN/m2||streamflow_N03
|-
| 5||Denitrification||gN/m2||denitrif
|-
| 6||Dissolved Organic Carbon loss||gC/m2||DOC
|-
| 7||Dissolved Organic Nitrogen loss||gN/m2||DON
|-
| 8||Evapotranspiration||mm/m2||et
|-
| 9||Net Photosynthesis||gC/m2||psn
|-
| 10||Mineralized N||gN/m2||mineralized
|-
| 11||Vegetation Uptake||gN/m2||uptake
|}

== Zone Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Rainfall||mm||rain
|-
| 8||Snowfall||mm||snow
|-
| 9||Daytime Mean Air Temperature||C||tday
|-
| 10||Average Daily Temperature||C||tavg
|-
| 11||Vapour Pressure Deficit||Pa||vpd
|-
| 12||Direct Radiation||KJ/m2||Kdown_direct
|-
| 13||Diffuse Radiation||KJ/m2||Kdown_diffuse
|-
| 14||Direct PAR Radiation||KJ/m2||PAR_direct
|-
| 15||Diffuse PAR Radiation||KJ/m2||PAR_diffuse
|}

== Zone Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Hillslope ID|| ||
|-
| 5||Zone ID|| ||
|-
| 6||Precipitation||mm||precip
|-
| 7||Direct Radiation||KJ/m2||K_direct
|-
| 8||Diffuse Radiation||KJ/m2||K_diffuse
|-
| 9||Average Max Daily Temperature||C||tmax
|-
| 10||Average Min Daily Temperature||C||tmin
|}

== Patch Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Rain Throughfall||mm||rain_thr
|-
| 9||Detention Store||mm||detention_store||rhessys5.10.10
|-
| 10||Saturation Deficit (depth)||mm of depth||sat_def_z
|-
| 11||Saturation Deficit (water)||mm of water||sat_def
|-
| 12||Unsaturated Storage||mm||unsat_stor
|-
| 13||Unsaturated Drainage||mm||unsat_drain
|-
| 14||Capillary Rise||mm||cap
|-
| 15||Return Flow||mm||return
|-
| 16||Evaporation||mm||evap
|-
| 17||Snowpack Depth||mm||snow
|-
| 18||Transpiration||mm||trans
|-
| 19||Subsurface Flow to Stream||mm||Qin||rhessys5.10.9
|-
| 20||Subsurface Flow to Stream||mm||Qout||rhessys5.10.9
|-
| 21||Net Photosynthesis||kgC/m2||psn
|-
| 22||Rooting Zone Saturation||?||root_zone.S
|-
| 23||Litter Rain Stored||mm||litter.rain_stor||rhessys5.10.10
|-
| 24||Litter Percent Saturation||m2/m2 ?||litter.S||rhessys5.10.9
|}

== Patch Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Leaf Area Index||m2/m2||lai
|-
| 9||Plant C||kgC/m2||plantc
|-
| 10||Net Photosynthesis||gC/m2||net_psn
|-
| 11||Plant Respiration||gC/m2/day||plant_resp||rhessys5.10.11
|-
| 12||Soil Respiration||gC/m2/day||soil_resp||rhessys5.10.11
|-
| 13||Labile Litter C||kgC/m2||litr1c
|-
| 14||Cellulose Litter C||kgC/m2||litr2c
|-
| 15||Shielded Cellulose Litter C||kgC/m2||litr3c
|-
| 16||Lignan Litter C||kgC/m2||litr4c
|-
| 17||Litter Rain Capacity||mm||lit.rain_cap||rhessys5.10.10
|-
| 18||Fast Soil C||kgC/m2||soil1c
|-
| 19||Medium Soil C||kgC/m2||soil2c
|-
| 20||Slow Soil C||kgC/m2||soil3c
|-
| 21||Recalcitrant Soil C||kgC/m2||soil4c
|-
| 22||Denitrification||gN/m2||denitrif
|-
| 23||Net Nitrate Flux (+in)||gN/m2||netleach
|-
| 24||Soil Nitrate||gN/m2||soilNO3
|-
| 25||Streamflow N||gN/m2||streamN03
|-
| 26||Surface N||gN/m2||surfaceN03
|-
| 27||Canopy Height||m||height
|-
| 28||Nitrogen Uptake||??||N-uptake
|-
| 29||Area||cells||area
|}

== Patch Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Hillslope ID|| ||
|-
| 5||Zone ID|| ||
|-
| 6||Patch ID|| ||
|-
| 7||Net Nitrate Flux (+in)||gN/m2||leach
|-
| 8||Denitrification||gN/m2/month||denitrif
|-
| 9||Average Soil Moisture Deficit||mm||soil_moist_deficit
|-
| 10||Evapotranspiration||mm/m2/month||et
|-
| 11||Net Photosynthesis||gC/m2/month||psn
|-
| 12||Dissolved Organic Carbon loss||gC/m2/month||DOC
|-
| 13||Dissolved Organic Nitrogen loss||gN/m2/month||DON
|-
| 14||Average LAI||m2/m2||lai
|-
| 15||Nitrification||gN/m2/month||nitrif
|-
| 16||Mineralized N||gN/m2/month||mineralized
|-
| 17||Vegetation Uptake||gN/m2/month||uptake
|-
| 18||Theta||0-100 percent||theta
|}

== Patch Yearly ==

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Zone ID|| ||
|-
| 5||Patch ID|| ||
|-
| 6||Number of Days Below Sat. Threshold|| ||num_threshold_sat_def
|-
| 7||Net Nitrate Flux (+in)||gN/m2/year||leach
|-
| 8||Denitrification||gN/m2/year||denitrif
|-
| 9||Dissolved Organic Carbon loss||gC/m2/year||DOC_loss
|-
| 10||Dissolved Organic Nitrogen loss||gN/m2/year||DON_loss
|-
| 11||Net Photosynthesis||gC/m2||psn
|-
| 12||Evapotranspiration||mm/m2/year||et
|-
| 13||Maximum Leaf Area Index||m2/m2/year||lai
|-
| 14||Nitrification||gN/m2/year||nitrif
|-
| 15||Mineralized N||gN/m2year||mineralized
|-
| 16||Vegetation Uptake||gN/m2/year||uptake
|-
| 17||Theta||0-100 percent||theta
|}

== Patch Yearly Growth ==

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Zone ID|| ||
|-
| 5||Patch ID|| ||
|-
| 6||Litter C||kgC/m2||litter_c
|-
| 7||Soil C||kgC/m2/year||soil_c
|-
| 8||Litter N||kgN/m2/year||litter_n
|-
| 9||Soil N||kgN/m2/year||soil_n
|-
| 10||Soil Nitrate||gN/m2/year||nitrate
|-
| 11||Mineralized N||gN/m2||Sminn
|}

== Stratum Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Stratum ID|| ||
|-
| 9||Leaf Area Index||m2/m2||lai
|-
| 10||Evaporation||mm||evap
|-
| 11||APAR Radiation||KJ/m2||APAR_direct
|-
| 12||APAR Radiation||KJ/m2||APAR_diffuse
|-
| 13||Sublimation||mm||sublim
|-
| 14||Transpiration||mm||trans
|-
| 15||Aerodynamic Conductance||mm/s||ga
|-
| 16||Surface (non-vascular) Conductance||m/s||gsurf
|-
| 17||Canopy Conductance||mm/s||gs
|-
| 18||??||??||?psi?||rhessys5.10.10
|-
| 19||Respiration||kgC/m2||leaf_day_mr
|-
| 20||Net Photosynthesis||gC/m2||psn_to_cpool
|-
| 21||Rain Interception Storage||mm||rain_stored
|-
| 22||Snow Interception Storage||mm||snow_stored
|-
| 23||Rooting Zone Saturation||??||rootzone.S
|}

== Stratum Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Stratum ID|| ||
|-
| 9||Leaf Area Index||m2/m2||proj_lai
|-
| 10||Leaf C||gN/m2||leafc
|-
| 11||Dead Leaf C||gN/m2||dead_leafc
|-
| 12||Fine Root C||gN/m2||frootc
|-
| 13||Live Stem C||gN/m2||live_stemc
|-
| 14||Leaf C Store||gN/m2||leafc_store
|-
| 15||Dead Stem C||gN/m2||dead_stemc
|-
| 16||Live Coarse Root C||gN/m2||live_crootc
|-
| 17||Dead Coarse Root C||gN/m2||dead_crootc
|-
| 18||Coarse Woody Debris C||gN/m2||cwdc
|-
| 19||Maint Respiration||gC/m2||mresp
|-
| 20||Growth Respiration||gC/m2||gresp
|-
| 21||Net Photosynthesis||gC/m2||psn_to_cpool
|-
| 22||Stand Age||days||age||rhessys5.10.9
|}

== Stratum Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Hillslope ID|| ||
|-
| 5||Zone ID|| ||
|-
| 6||Patch ID|| ||
|-
| 7||Stratum ID|| ||
|-
| 8||Leaf Area Index||m2/m2||lai
|-
| 9||Net Photosynthesis||gC/m2||psn
|-
| 10||Mean Leaf Water Potential||mPa||lwp
|}

== Stratum Yearly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Zone ID|| ||
|-
| 5||Patch ID|| ||
|-
| 6||Stratum ID|| ||
|-
| 7||Net Photosynthesis||kgC/m2||psn
|-
| 8||Mean Leaf Water Potential||mPa||lwp
|}

Output Files

2010-07-16T18:52:48Z

Dgroulx: /* Patch Yearly */

== Basin Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| || ||
|-
| 2||Month|| || ||
|-
| 3||Year|| || ||
|-
| 4||Basin ID|| || ||
|-
| 5||Rain Throughfall||mm||pot_surface_infil||
|-
| 6||Snow Throughfall||mm||snow_thr||
|-
| 7||Saturation Deficit-depth||mm of depth||sat_def_z||
|-
| 8||Saturation Deficit-volume||mm of water||sat_def||
|-
| 8||Rooting Zone Storage||mm of water||rz_storage||
|-
| 9||Unsaturated Storage||mm||unsat_stor||
|-
| 10||Unsaturated Drainage||mm||unsat_drain||
|-
| 11||Capillary Rise||mm||cap||
|-
| 12||Evaporation||mm||evap||
|-
| 13||Snowpack Depth||mm||snow||
|-
| 14||Transpiration||mm||trans||
|-
| 15||Baseflow||mm||baseflow||
|-
| 20||Return Flow||mm||return||
|-
| 17||Total Stream Outflow||mm||streamflow||
|-
| 18||Net Photosynthesis||kgC/m2||psn||
|-
| 19||Leaf Area Index||m2/m2||lai||
|-
| 20||Groundwater Output||mm||gw.Qout||
|-
| 21||Groundwater Nitrate Output||mm||gw.Nout||
|-
| 22||Groundwater Store||mm||gw.storage||rhessys5.10.5
|-
| 23||Groundwater Nitrate Store||mm||gw.NO3||rhessys5.10.5
|-
| 24||Detention Store||mm||detention_store||rhessys5.10.10
|-
| 25||Percent Saturated Area||m2/m2||%sat_area||rhessys5.10.10
|-
| 26||Litter Store||m2/m2||litter_store||rhessys5.10.12
|-
| 27||Percent Snow Cover||m2/m2||%snow_cover||rhessys5.10.12
|}

== Basin Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Gross Photosynthesis||gC/m2||gpsn
|-
| 6||Plant Maintenance Respiration||mC/m2||plant_resp
|-
| 7||Soil Respiration||gC/m2/day||soil_resp||rhessys5.10.11
|-
| 8||Nitrate N||gN/m2||nitrate
|-
| 9||Mineralized N||gN/m2||sminn
|-
| 10||Plant C||kgC/m2||plantc
|-
| 11||Plant N||kgN/m2||plantn
|-
| 12||Litter C||kgC/m2||litrc
|-
| 13||Litter N||kgN/m2||litrn
|-
| 14||Soil C||kgC/m2||soilc
|-
| 15||Soil N||kgN/m2||soiln
|-
| 16||Streamflow Nitrate||gN/m2/day||streamflow_NO3
|-
| 17||Denitrification||gN/m2/day||denitrif
|-
| 18||Nitrification||gN/m2/day||nitrif
|-
| 19||Dissolved Organic Carbon loss||gC/m2/day||DOC
|-
| 20||Dissolved Organic Nitrogen loss||gN/m2/day||DON
|}

== Basin Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Total Stream Outflow||mm||streamflow
|-
| 5||Nitrate to Stream||gN/m2||streamflow_NO3
|-
| 6||Denitrification||gN/m2||denitrif
|-
| 7||Dissolved Organic Carbon loss||gC/m2||DOC
|-
| 8||Dissolved Organic Nitrogen loss||gN/m2||DON
|-
| 9||Evapotranspiration||mm/m2||et
|-
| 10||Net Photosynthesis||gC/m2||psn
|-
| 11||Leaf Area Index||m2/m2||lai
|-
| 12||Nitrification||gN/m2||nitrif
|-
| 13||Mineralized Nitrate||gN/m2||mineralized
|-
| 14||Vegetation Nitrogen Uptake||gN/m2||uptake
|}

== Basin Yearly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Total Stream Outflow||mm||streamflow
|-
| 4||Nitrate to Stream||gN/m2||streamflow_NO3
|-
| 5||Denitrification||gN/m2||denitrif
|-
| 6||Dissolved Organic Carbon loss||gC/m2||DOC
|-
| 7||Dissolved Organic Nitrogen loss||gN/m2||DON
|-
| 8||Evapotranspiration||mm/m2||et
|-
| 9||Net Photosynthesis||gC/m2||psn
|-
| 10||Average Leaf Area Index||m2/m2||lai
|-
| 11||Nitrification||gN/m2||nitrif
|-
| 12||Mineralized N||gN/m2||mineralized
|-
| 13||Vegetation Uptake||gN/m2||uptake
|-
| 14||Number Threshold||?||num_thresh
|}

== Basin Yearly Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Year|| || ||rhessys5.10.5
|-
| 2||Basin ID|| || ||rhessys5.10.5
|-
| 3||Gross Photosynthesis||gC/m2||gpsn||rhessys5.10.5
|-
| 4||Plant Respiration||mC/m2||plantresp||rhessys5.10.5
|-
| 5||New Carbon||mC/m2||newC||rhessys5.10.5
|-
| 6||?Soilhr?||??||soilhr||rhessys5.10.5
|-
| 7||?Streamflow Nitrate?||??||strN||rhessys5.10.5
|-
| 8||Denitrification||gN/m2||denitrif||rhessys5.10.5
|-
|
|}

== Hillslope Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Rain Throughfall||mm||rain_thr
|-
| 7||Snow Throughfall||mm||snow_thr
|-
| 8||Saturation Deficit||mm of depth||sat_def_z
|-
| 9||Saturation Deficit||mm of water||sat_def
|-
| 10||Unsaturated Storage||mm||unsat_stor
|-
| 11||Unsaturated Drainage||mm||unsat_drain
|-
| 12||Capillary Rise||mm||cap
|-
| 13||Evaporation||mm||evap
|-
| 14||Snowpack Depth||mm||snow
|-
| 15||Transpiration||mm||trans
|-
| 16||Baseflow||mm||baseflow
|-
| 17||Return Flow||mm||return
|-
| 18||Total Stream Outflow||mm||streamflow
|-
| 19||Net Photosynthesis||kgC/m2||psn
|-
| 20||Leaf Area Index||m2/m2||lai
|-
| 21||Groundwater Output||mm||gw.Qout||rhessys5.10.5
|-
| 22||Groundwater Nitrate Output||mm||gw.Nout||rhessys5.10.5
|-
| 23||Groundwater Store||mm||gw.storage||rhessys5.10.5
|-
| 24||Groundwater Nitrate Store||mm||gw.N03||rhessys5.10.5
|}

== Hillslope Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Gross Photosynthesis||gC/m2||gpsn
|-
| 7||Maint Respiration||mC/m2||resp
|-
| 8||Nitrate N||gN/m2||nitrate
|-
| 9||Mineralized N||gN/m2||sminn
|-
| 10||Plant C||kgC/m2||plantc
|-
| 11||Plant N||kgN/m2||plantn
|-
| 12||Litter C||kgC/m2||litrc
|-
| 13||Litter N||kgN/m2||litrn
|-
| 14||Soil C||kgC/m2||soilc
|-
| 15||Soil N||kgN/m2||soiln
|-
| 16||Streamflow Nitrate||gN/m2/day||streamflow_NO3
|-
| 17||Streamflow||mm/day||streamflow
|-
| 18||Denitrification||gN/m2/day||denitrif
|-
| 19||Nitrification||gN/m2/day||nitrif
|-
| 20||Dissolved Organic Carbon loss||gC/m2/day||DOC
|-
| 21||Dissolved Organic Nitrogen loss||gN/m2/day||DON
|-
|
|}

== Hillslope Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| || ||rhessys5.10.7
|-
| 2||Year|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Streamflow||mm||streamflow
|-
| 5||Streamflow Nitrate||gN/m2/day||streamflow_N03
|-
| 6||Denitrification||gN/m2/day||denitrif
|-
| 7||Dissolved Organic Carbon Loss||gC/m2/day||DOC
|-
| 8||Dissolved Organic Nitrogen Loss||gN/m2/day||DON
|-
| 9||Evapotranspiration||mm/m2||et
|-
| 10||Net Photosynthesis||gC/m2||psn
|-
| 11||Leaf Area Index||m2/m2||lai
|-
| 12||Nitrification||gN/m2||nitrif
|-
| 13||Mineralized N||gN/m2||mineralized
|-
| 14||Vegetation Uptake||gN/m2||uptake
|}

== Hillslope Yearly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| || ||rhessys5.10.7
|-
| 2||Hillslope ID|| ||
|-
| 3||Streamflow||mm||streamflow
|-
| 4||Nitrate to Stream||gN/m2||streamflow_N03
|-
| 5||Denitrification||gN/m2||denitrif
|-
| 6||Dissolved Organic Carbon loss||gC/m2||DOC
|-
| 7||Dissolved Organic Nitrogen loss||gN/m2||DON
|-
| 8||Evapotranspiration||mm/m2||et
|-
| 9||Net Photosynthesis||gC/m2||psn
|-
| 10||Mineralized N||gN/m2||mineralized
|-
| 11||Vegetation Uptake||gN/m2||uptake
|}

== Zone Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Rainfall||mm||rain
|-
| 8||Snowfall||mm||snow
|-
| 9||Daytime Mean Air Temperature||C||tday
|-
| 10||Average Daily Temperature||C||tavg
|-
| 11||Vapour Pressure Deficit||Pa||vpd
|-
| 12||Direct Radiation||KJ/m2||Kdown_direct
|-
| 13||Diffuse Radiation||KJ/m2||Kdown_diffuse
|-
| 14||Direct PAR Radiation||KJ/m2||PAR_direct
|-
| 15||Diffuse PAR Radiation||KJ/m2||PAR_diffuse
|}

== Zone Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Hillslope ID|| ||
|-
| 5||Zone ID|| ||
|-
| 6||Precipitation||mm||precip
|-
| 7||Direct Radiation||KJ/m2||K_direct
|-
| 8||Diffuse Radiation||KJ/m2||K_diffuse
|-
| 9||Average Max Daily Temperature||C||tmax
|-
| 10||Average Min Daily Temperature||C||tmin
|}

== Patch Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Rain Throughfall||mm||rain_thr
|-
| 9||Detention Store||mm||detention_store||rhessys5.10.10
|-
| 10||Saturation Deficit (depth)||mm of depth||sat_def_z
|-
| 11||Saturation Deficit (water)||mm of water||sat_def
|-
| 12||Unsaturated Storage||mm||unsat_stor
|-
| 13||Unsaturated Drainage||mm||unsat_drain
|-
| 14||Capillary Rise||mm||cap
|-
| 15||Return Flow||mm||return
|-
| 16||Evaporation||mm||evap
|-
| 17||Snowpack Depth||mm||snow
|-
| 18||Transpiration||mm||trans
|-
| 19||Subsurface Flow to Stream||mm||Qin||rhessys5.10.9
|-
| 20||Subsurface Flow to Stream||mm||Qout||rhessys5.10.9
|-
| 21||Net Photosynthesis||kgC/m2||psn
|-
| 22||Rooting Zone Saturation||?||root_zone.S
|-
| 23||Litter Rain Stored||mm||litter.rain_stor||rhessys5.10.10
|-
| 24||Litter Percent Saturation||m2/m2 ?||litter.S||rhessys5.10.9
|}

== Patch Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Leaf Area Index||m2/m2||lai
|-
| 9||Plant C||kgC/m2||plantc
|-
| 10||Net Photosynthesis||gC/m2||net_psn
|-
| 11||Plant Respiration||gC/m2/day||plant_resp||rhessys5.10.11
|-
| 12||Soil Respiration||gC/m2/day||soil_resp||rhessys5.10.11
|-
| 13||Labile Litter C||kgC/m2||litr1c
|-
| 14||Cellulose Litter C||kgC/m2||litr2c
|-
| 15||Shielded Cellulose Litter C||kgC/m2||litr3c
|-
| 16||Lignan Litter C||kgC/m2||litr4c
|-
| 17||Litter Rain Capacity||mm||lit.rain_cap||rhessys5.10.10
|-
| 18||Fast Soil C||kgC/m2||soil1c
|-
| 19||Medium Soil C||kgC/m2||soil2c
|-
| 20||Slow Soil C||kgC/m2||soil3c
|-
| 21||Recalcitrant Soil C||kgC/m2||soil4c
|-
| 22||Denitrification||gN/m2||denitrif
|-
| 23||Net Nitrate Flux (+in)||gN/m2||netleach
|-
| 24||Soil Nitrate||gN/m2||soilNO3
|-
| 25||Streamflow N||gN/m2||streamN03
|-
| 26||Surface N||gN/m2||surfaceN03
|-
| 27||Canopy Height||m||height
|-
| 28||Nitrogen Uptake||??||N-uptake
|-
| 29||Area||cells||area
|}

== Patch Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Hillslope ID|| ||
|-
| 5||Zone ID|| ||
|-
| 6||Patch ID|| ||
|-
| 7||Net Nitrate Flux (+in)||gN/m2||leach
|-
| 8||Denitrification||gN/m2/month||denitrif
|-
| 9||Average Soil Moisture Deficit||mm||soil_moist_deficit
|-
| 10||Evapotranspiration||mm/m2/month||et
|-
| 11||Net Photosynthesis||gC/m2/month||psn
|-
| 12||Dissolved Organic Carbon loss||gC/m2/month||DOC
|-
| 13||Dissolved Organic Nitrogen loss||gN/m2/month||DON
|-
| 14||Average LAI||m2/m2||lai
|-
| 15||Nitrification||gN/m2/month||nitrif
|-
| 16||Mineralized N||gN/m2/month||mineralized
|-
| 17||Vegetation Uptake||gN/m2/month||uptake
|-
| 18||Theta||0-100 percent||theta
|}

== Patch Yearly ==

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Zone ID|| ||
|-
| 5||Patch ID|| ||
|-
| 6||Number of Days Below Sat. Threshold|| ||num_threshold_sat_def
|-
| 7||Net Nitrate Flux (+in)||gN/m2/year||leach
|-
| 8||Denitrification||gN/m2/year||denitrif
|-
| 9||Dissolved Organic Carbon loss||gC/m2/year||DOC_loss
|-
| 10||Dissolved Organic Nitrogen loss||gN/m2/year||DON_loss
|-
| 11||Net Photosynthesis||gC/m2||psn
|-
| 12||Evapotranspiration||mm/m2/year||et
|-
| 13||Maximum Leaf Area Index||m2/m2/year||lai
|-
| 14||Nitrification||gN/m2/year||nitrif
|-
| 15||Mineralized N||gN/m2year||mineralized
|-
| 16||Vegetation Uptake||gN/m2/year||uptake
|-
| 17||Theta||0-100 percent||theta
|}

== Patch Yearly Growth ==

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Zone ID|| ||
|-
| 5||Patch ID|| ||
|-
| 6||Litter C||kgC/m2||litter_c
|-
| 7||Soil C||kgC/m2/year||soil_c
|-
| 8||Litter N||kgN/m2/year||litter_n
|-
| 9||Soil N||kgN/m2/year||soil_n
|-
| 10||Soil Nitrate||gN/m2/year||nitrate
|-
| 11||Mineralized N||gN/m2||Sminn
|}

== Stratum Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Stratum ID|| ||
|-
| 9||Leaf Area Index||m2/m2||lai
|-
| 10||Evaporation||mm||evap
|-
| 11||APAR Radiation||KJ/m2||APAR_direct
|-
| 12||APAR Radiation||KJ/m2||APAR_diffuse
|-
| 13||Sublimation||mm||sublim
|-
| 14||Transpiration||mm||trans
|-
| 15||Aerodynamic Conductance||mm/s||ga
|-
| 16||Surface (non-vascular) Conductance||m/s||gsurf
|-
| 17||Canopy Conductance||mm/s||gs
|-
| 18||??||??||?psi?||rhessys5.10.10
|-
| 19||Respiration||kgC/m2||leaf_day_mr
|-
| 20||Net Photosynthesis||gC/m2||psn_to_cpool
|-
| 21||Rain Interception Storage||mm||rain_stored
|-
| 22||Snow Interception Storage||mm||snow_stored
|-
| 23||Rooting Zone Saturation||??||rootzone.S
|}

== Stratum Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Stratum ID|| ||
|-
| 9||Leaf Area Index||m2/m2||proj_lai
|-
| 10||Leaf C||gN/m2||leafc
|-
| 11||Dead Leaf C||gN/m2||dead_leafc
|-
| 12||Fine Root C||gN/m2||frootc
|-
| 13||Live Stem C||gN/m2||live_stemc
|-
| 14||Leaf C Store||gN/m2||leafc_store
|-
| 15||Dead Stem C||gN/m2||dead_stemc
|-
| 16||Live Coarse Root C||gN/m2||live_crootc
|-
| 17||Dead Coarse Root C||gN/m2||dead_crootc
|-
| 18||Coarse Woody Debris C||gN/m2||cwdc
|-
| 19||Maint Respiration||gC/m2||mresp
|-
| 20||Growth Respiration||gC/m2||gresp
|-
| 21||Net Photosynthesis||gC/m2||psn_to_cpool
|-
| 22||Stand Age||days||age||rhessys5.10.9
|}

== Stratum Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Hillslope ID|| ||
|-
| 5||Zone ID|| ||
|-
| 6||Patch ID|| ||
|-
| 7||Stratum ID|| ||
|-
| 8||Leaf Area Index||m2/m2||lai
|-
| 9||Net Photosynthesis||gC/m2||psn
|-
| 10||Mean Leaf Water Potential||mPa||lwp
|}

== Stratum Yearly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Zone ID|| ||
|-
| 5||Patch ID|| ||
|-
| 6||Stratum ID|| ||
|-
| 7||Net Photosynthesis||kgC/m2||psn
|-
| 8||Mean Leaf Water Potential||mPa||lwp
|}

Output Files

2010-07-16T18:52:40Z

Dgroulx: /* Patch Monthly */

== Basin Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| || ||
|-
| 2||Month|| || ||
|-
| 3||Year|| || ||
|-
| 4||Basin ID|| || ||
|-
| 5||Rain Throughfall||mm||pot_surface_infil||
|-
| 6||Snow Throughfall||mm||snow_thr||
|-
| 7||Saturation Deficit-depth||mm of depth||sat_def_z||
|-
| 8||Saturation Deficit-volume||mm of water||sat_def||
|-
| 8||Rooting Zone Storage||mm of water||rz_storage||
|-
| 9||Unsaturated Storage||mm||unsat_stor||
|-
| 10||Unsaturated Drainage||mm||unsat_drain||
|-
| 11||Capillary Rise||mm||cap||
|-
| 12||Evaporation||mm||evap||
|-
| 13||Snowpack Depth||mm||snow||
|-
| 14||Transpiration||mm||trans||
|-
| 15||Baseflow||mm||baseflow||
|-
| 20||Return Flow||mm||return||
|-
| 17||Total Stream Outflow||mm||streamflow||
|-
| 18||Net Photosynthesis||kgC/m2||psn||
|-
| 19||Leaf Area Index||m2/m2||lai||
|-
| 20||Groundwater Output||mm||gw.Qout||
|-
| 21||Groundwater Nitrate Output||mm||gw.Nout||
|-
| 22||Groundwater Store||mm||gw.storage||rhessys5.10.5
|-
| 23||Groundwater Nitrate Store||mm||gw.NO3||rhessys5.10.5
|-
| 24||Detention Store||mm||detention_store||rhessys5.10.10
|-
| 25||Percent Saturated Area||m2/m2||%sat_area||rhessys5.10.10
|-
| 26||Litter Store||m2/m2||litter_store||rhessys5.10.12
|-
| 27||Percent Snow Cover||m2/m2||%snow_cover||rhessys5.10.12
|}

== Basin Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Gross Photosynthesis||gC/m2||gpsn
|-
| 6||Plant Maintenance Respiration||mC/m2||plant_resp
|-
| 7||Soil Respiration||gC/m2/day||soil_resp||rhessys5.10.11
|-
| 8||Nitrate N||gN/m2||nitrate
|-
| 9||Mineralized N||gN/m2||sminn
|-
| 10||Plant C||kgC/m2||plantc
|-
| 11||Plant N||kgN/m2||plantn
|-
| 12||Litter C||kgC/m2||litrc
|-
| 13||Litter N||kgN/m2||litrn
|-
| 14||Soil C||kgC/m2||soilc
|-
| 15||Soil N||kgN/m2||soiln
|-
| 16||Streamflow Nitrate||gN/m2/day||streamflow_NO3
|-
| 17||Denitrification||gN/m2/day||denitrif
|-
| 18||Nitrification||gN/m2/day||nitrif
|-
| 19||Dissolved Organic Carbon loss||gC/m2/day||DOC
|-
| 20||Dissolved Organic Nitrogen loss||gN/m2/day||DON
|}

== Basin Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Total Stream Outflow||mm||streamflow
|-
| 5||Nitrate to Stream||gN/m2||streamflow_NO3
|-
| 6||Denitrification||gN/m2||denitrif
|-
| 7||Dissolved Organic Carbon loss||gC/m2||DOC
|-
| 8||Dissolved Organic Nitrogen loss||gN/m2||DON
|-
| 9||Evapotranspiration||mm/m2||et
|-
| 10||Net Photosynthesis||gC/m2||psn
|-
| 11||Leaf Area Index||m2/m2||lai
|-
| 12||Nitrification||gN/m2||nitrif
|-
| 13||Mineralized Nitrate||gN/m2||mineralized
|-
| 14||Vegetation Nitrogen Uptake||gN/m2||uptake
|}

== Basin Yearly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Total Stream Outflow||mm||streamflow
|-
| 4||Nitrate to Stream||gN/m2||streamflow_NO3
|-
| 5||Denitrification||gN/m2||denitrif
|-
| 6||Dissolved Organic Carbon loss||gC/m2||DOC
|-
| 7||Dissolved Organic Nitrogen loss||gN/m2||DON
|-
| 8||Evapotranspiration||mm/m2||et
|-
| 9||Net Photosynthesis||gC/m2||psn
|-
| 10||Average Leaf Area Index||m2/m2||lai
|-
| 11||Nitrification||gN/m2||nitrif
|-
| 12||Mineralized N||gN/m2||mineralized
|-
| 13||Vegetation Uptake||gN/m2||uptake
|-
| 14||Number Threshold||?||num_thresh
|}

== Basin Yearly Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Year|| || ||rhessys5.10.5
|-
| 2||Basin ID|| || ||rhessys5.10.5
|-
| 3||Gross Photosynthesis||gC/m2||gpsn||rhessys5.10.5
|-
| 4||Plant Respiration||mC/m2||plantresp||rhessys5.10.5
|-
| 5||New Carbon||mC/m2||newC||rhessys5.10.5
|-
| 6||?Soilhr?||??||soilhr||rhessys5.10.5
|-
| 7||?Streamflow Nitrate?||??||strN||rhessys5.10.5
|-
| 8||Denitrification||gN/m2||denitrif||rhessys5.10.5
|-
|
|}

== Hillslope Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Rain Throughfall||mm||rain_thr
|-
| 7||Snow Throughfall||mm||snow_thr
|-
| 8||Saturation Deficit||mm of depth||sat_def_z
|-
| 9||Saturation Deficit||mm of water||sat_def
|-
| 10||Unsaturated Storage||mm||unsat_stor
|-
| 11||Unsaturated Drainage||mm||unsat_drain
|-
| 12||Capillary Rise||mm||cap
|-
| 13||Evaporation||mm||evap
|-
| 14||Snowpack Depth||mm||snow
|-
| 15||Transpiration||mm||trans
|-
| 16||Baseflow||mm||baseflow
|-
| 17||Return Flow||mm||return
|-
| 18||Total Stream Outflow||mm||streamflow
|-
| 19||Net Photosynthesis||kgC/m2||psn
|-
| 20||Leaf Area Index||m2/m2||lai
|-
| 21||Groundwater Output||mm||gw.Qout||rhessys5.10.5
|-
| 22||Groundwater Nitrate Output||mm||gw.Nout||rhessys5.10.5
|-
| 23||Groundwater Store||mm||gw.storage||rhessys5.10.5
|-
| 24||Groundwater Nitrate Store||mm||gw.N03||rhessys5.10.5
|}

== Hillslope Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Gross Photosynthesis||gC/m2||gpsn
|-
| 7||Maint Respiration||mC/m2||resp
|-
| 8||Nitrate N||gN/m2||nitrate
|-
| 9||Mineralized N||gN/m2||sminn
|-
| 10||Plant C||kgC/m2||plantc
|-
| 11||Plant N||kgN/m2||plantn
|-
| 12||Litter C||kgC/m2||litrc
|-
| 13||Litter N||kgN/m2||litrn
|-
| 14||Soil C||kgC/m2||soilc
|-
| 15||Soil N||kgN/m2||soiln
|-
| 16||Streamflow Nitrate||gN/m2/day||streamflow_NO3
|-
| 17||Streamflow||mm/day||streamflow
|-
| 18||Denitrification||gN/m2/day||denitrif
|-
| 19||Nitrification||gN/m2/day||nitrif
|-
| 20||Dissolved Organic Carbon loss||gC/m2/day||DOC
|-
| 21||Dissolved Organic Nitrogen loss||gN/m2/day||DON
|-
|
|}

== Hillslope Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| || ||rhessys5.10.7
|-
| 2||Year|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Streamflow||mm||streamflow
|-
| 5||Streamflow Nitrate||gN/m2/day||streamflow_N03
|-
| 6||Denitrification||gN/m2/day||denitrif
|-
| 7||Dissolved Organic Carbon Loss||gC/m2/day||DOC
|-
| 8||Dissolved Organic Nitrogen Loss||gN/m2/day||DON
|-
| 9||Evapotranspiration||mm/m2||et
|-
| 10||Net Photosynthesis||gC/m2||psn
|-
| 11||Leaf Area Index||m2/m2||lai
|-
| 12||Nitrification||gN/m2||nitrif
|-
| 13||Mineralized N||gN/m2||mineralized
|-
| 14||Vegetation Uptake||gN/m2||uptake
|}

== Hillslope Yearly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| || ||rhessys5.10.7
|-
| 2||Hillslope ID|| ||
|-
| 3||Streamflow||mm||streamflow
|-
| 4||Nitrate to Stream||gN/m2||streamflow_N03
|-
| 5||Denitrification||gN/m2||denitrif
|-
| 6||Dissolved Organic Carbon loss||gC/m2||DOC
|-
| 7||Dissolved Organic Nitrogen loss||gN/m2||DON
|-
| 8||Evapotranspiration||mm/m2||et
|-
| 9||Net Photosynthesis||gC/m2||psn
|-
| 10||Mineralized N||gN/m2||mineralized
|-
| 11||Vegetation Uptake||gN/m2||uptake
|}

== Zone Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Rainfall||mm||rain
|-
| 8||Snowfall||mm||snow
|-
| 9||Daytime Mean Air Temperature||C||tday
|-
| 10||Average Daily Temperature||C||tavg
|-
| 11||Vapour Pressure Deficit||Pa||vpd
|-
| 12||Direct Radiation||KJ/m2||Kdown_direct
|-
| 13||Diffuse Radiation||KJ/m2||Kdown_diffuse
|-
| 14||Direct PAR Radiation||KJ/m2||PAR_direct
|-
| 15||Diffuse PAR Radiation||KJ/m2||PAR_diffuse
|}

== Zone Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Hillslope ID|| ||
|-
| 5||Zone ID|| ||
|-
| 6||Precipitation||mm||precip
|-
| 7||Direct Radiation||KJ/m2||K_direct
|-
| 8||Diffuse Radiation||KJ/m2||K_diffuse
|-
| 9||Average Max Daily Temperature||C||tmax
|-
| 10||Average Min Daily Temperature||C||tmin
|}

== Patch Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Rain Throughfall||mm||rain_thr
|-
| 9||Detention Store||mm||detention_store||rhessys5.10.10
|-
| 10||Saturation Deficit (depth)||mm of depth||sat_def_z
|-
| 11||Saturation Deficit (water)||mm of water||sat_def
|-
| 12||Unsaturated Storage||mm||unsat_stor
|-
| 13||Unsaturated Drainage||mm||unsat_drain
|-
| 14||Capillary Rise||mm||cap
|-
| 15||Return Flow||mm||return
|-
| 16||Evaporation||mm||evap
|-
| 17||Snowpack Depth||mm||snow
|-
| 18||Transpiration||mm||trans
|-
| 19||Subsurface Flow to Stream||mm||Qin||rhessys5.10.9
|-
| 20||Subsurface Flow to Stream||mm||Qout||rhessys5.10.9
|-
| 21||Net Photosynthesis||kgC/m2||psn
|-
| 22||Rooting Zone Saturation||?||root_zone.S
|-
| 23||Litter Rain Stored||mm||litter.rain_stor||rhessys5.10.10
|-
| 24||Litter Percent Saturation||m2/m2 ?||litter.S||rhessys5.10.9
|}

== Patch Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Leaf Area Index||m2/m2||lai
|-
| 9||Plant C||kgC/m2||plantc
|-
| 10||Net Photosynthesis||gC/m2||net_psn
|-
| 11||Plant Respiration||gC/m2/day||plant_resp||rhessys5.10.11
|-
| 12||Soil Respiration||gC/m2/day||soil_resp||rhessys5.10.11
|-
| 13||Labile Litter C||kgC/m2||litr1c
|-
| 14||Cellulose Litter C||kgC/m2||litr2c
|-
| 15||Shielded Cellulose Litter C||kgC/m2||litr3c
|-
| 16||Lignan Litter C||kgC/m2||litr4c
|-
| 17||Litter Rain Capacity||mm||lit.rain_cap||rhessys5.10.10
|-
| 18||Fast Soil C||kgC/m2||soil1c
|-
| 19||Medium Soil C||kgC/m2||soil2c
|-
| 20||Slow Soil C||kgC/m2||soil3c
|-
| 21||Recalcitrant Soil C||kgC/m2||soil4c
|-
| 22||Denitrification||gN/m2||denitrif
|-
| 23||Net Nitrate Flux (+in)||gN/m2||netleach
|-
| 24||Soil Nitrate||gN/m2||soilNO3
|-
| 25||Streamflow N||gN/m2||streamN03
|-
| 26||Surface N||gN/m2||surfaceN03
|-
| 27||Canopy Height||m||height
|-
| 28||Nitrogen Uptake||??||N-uptake
|-
| 29||Area||cells||area
|}

== Patch Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Hillslope ID|| ||
|-
| 5||Zone ID|| ||
|-
| 6||Patch ID|| ||
|-
| 7||Net Nitrate Flux (+in)||gN/m2||leach
|-
| 8||Denitrification||gN/m2/month||denitrif
|-
| 9||Average Soil Moisture Deficit||mm||soil_moist_deficit
|-
| 10||Evapotranspiration||mm/m2/month||et
|-
| 11||Net Photosynthesis||gC/m2/month||psn
|-
| 12||Dissolved Organic Carbon loss||gC/m2/month||DOC
|-
| 13||Dissolved Organic Nitrogen loss||gN/m2/month||DON
|-
| 14||Average LAI||m2/m2||lai
|-
| 15||Nitrification||gN/m2/month||nitrif
|-
| 16||Mineralized N||gN/m2/month||mineralized
|-
| 17||Vegetation Uptake||gN/m2/month||uptake
|-
| 18||Theta||0-100 percent||theta
|}

== Patch Yearly ==

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Zone ID|| ||
|-
| 5||Patch ID|| ||
|-
| 6||Number of Days Below Sat. Threshold|| ||num_threshold_sat_def
|-
| 7||Net Nitrate Flux (+in)||gN/m2/year||leach
|-
| 8||Denitrification||gN/m2/year||denitrif
|-
| 9||Dissolved Organic Carbon loss||gC/m2/year||DOC_loss
|-
| 10||Dissolved Organic Nitrogen loss||gN/m2/year||DON_loss
|-
| 11||Net Photosynthesis||gC/m2||psn
|-
| 12||Evapotranspiration||mm/m2/year||et
|-
| 13||Maximum Leaf Area Index||m2/m2/year||lai
|-
| 14||Nitrification||gN/m2/year||nitrif
|-
| 15||Mineralized N||gN/m2year||mineralized
|-
| 16||Vegetation Uptake||gN/m2/year||uptake
|-
| 17||Theta||0-100 percent||theta
|}

== Patch Yearly Growth ==

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Zone ID|| ||
|-
| 5||Patch ID|| ||
|-
| 6||Litter C||kgC/m2||litter_c
|-
| 7||Soil C||kgC/m2/year||soil_c
|-
| 8||Litter N||kgN/m2/year||litter_n
|-
| 9||Soil N||kgN/m2/year||soil_n
|-
| 10||Soil Nitrate||gN/m2/year||nitrate
|-
| 11||Mineralized N||gN/m2||Sminn
|}

== Stratum Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Stratum ID|| ||
|-
| 9||Leaf Area Index||m2/m2||lai
|-
| 10||Evaporation||mm||evap
|-
| 11||APAR Radiation||KJ/m2||APAR_direct
|-
| 12||APAR Radiation||KJ/m2||APAR_diffuse
|-
| 13||Sublimation||mm||sublim
|-
| 14||Transpiration||mm||trans
|-
| 15||Aerodynamic Conductance||mm/s||ga
|-
| 16||Surface (non-vascular) Conductance||m/s||gsurf
|-
| 17||Canopy Conductance||mm/s||gs
|-
| 18||??||??||?psi?||rhessys5.10.10
|-
| 19||Respiration||kgC/m2||leaf_day_mr
|-
| 20||Net Photosynthesis||gC/m2||psn_to_cpool
|-
| 21||Rain Interception Storage||mm||rain_stored
|-
| 22||Snow Interception Storage||mm||snow_stored
|-
| 23||Rooting Zone Saturation||??||rootzone.S
|}

== Stratum Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Stratum ID|| ||
|-
| 9||Leaf Area Index||m2/m2||proj_lai
|-
| 10||Leaf C||gN/m2||leafc
|-
| 11||Dead Leaf C||gN/m2||dead_leafc
|-
| 12||Fine Root C||gN/m2||frootc
|-
| 13||Live Stem C||gN/m2||live_stemc
|-
| 14||Leaf C Store||gN/m2||leafc_store
|-
| 15||Dead Stem C||gN/m2||dead_stemc
|-
| 16||Live Coarse Root C||gN/m2||live_crootc
|-
| 17||Dead Coarse Root C||gN/m2||dead_crootc
|-
| 18||Coarse Woody Debris C||gN/m2||cwdc
|-
| 19||Maint Respiration||gC/m2||mresp
|-
| 20||Growth Respiration||gC/m2||gresp
|-
| 21||Net Photosynthesis||gC/m2||psn_to_cpool
|-
| 22||Stand Age||days||age||rhessys5.10.9
|}

== Stratum Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Hillslope ID|| ||
|-
| 5||Zone ID|| ||
|-
| 6||Patch ID|| ||
|-
| 7||Stratum ID|| ||
|-
| 8||Leaf Area Index||m2/m2||lai
|-
| 9||Net Photosynthesis||gC/m2||psn
|-
| 10||Mean Leaf Water Potential||mPa||lwp
|}

== Stratum Yearly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Zone ID|| ||
|-
| 5||Patch ID|| ||
|-
| 6||Stratum ID|| ||
|-
| 7||Net Photosynthesis||kgC/m2||psn
|-
| 8||Mean Leaf Water Potential||mPa||lwp
|}

Output Files

2010-07-16T18:52:29Z

Dgroulx: /* Patch Daily Growth */

== Basin Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| || ||
|-
| 2||Month|| || ||
|-
| 3||Year|| || ||
|-
| 4||Basin ID|| || ||
|-
| 5||Rain Throughfall||mm||pot_surface_infil||
|-
| 6||Snow Throughfall||mm||snow_thr||
|-
| 7||Saturation Deficit-depth||mm of depth||sat_def_z||
|-
| 8||Saturation Deficit-volume||mm of water||sat_def||
|-
| 8||Rooting Zone Storage||mm of water||rz_storage||
|-
| 9||Unsaturated Storage||mm||unsat_stor||
|-
| 10||Unsaturated Drainage||mm||unsat_drain||
|-
| 11||Capillary Rise||mm||cap||
|-
| 12||Evaporation||mm||evap||
|-
| 13||Snowpack Depth||mm||snow||
|-
| 14||Transpiration||mm||trans||
|-
| 15||Baseflow||mm||baseflow||
|-
| 20||Return Flow||mm||return||
|-
| 17||Total Stream Outflow||mm||streamflow||
|-
| 18||Net Photosynthesis||kgC/m2||psn||
|-
| 19||Leaf Area Index||m2/m2||lai||
|-
| 20||Groundwater Output||mm||gw.Qout||
|-
| 21||Groundwater Nitrate Output||mm||gw.Nout||
|-
| 22||Groundwater Store||mm||gw.storage||rhessys5.10.5
|-
| 23||Groundwater Nitrate Store||mm||gw.NO3||rhessys5.10.5
|-
| 24||Detention Store||mm||detention_store||rhessys5.10.10
|-
| 25||Percent Saturated Area||m2/m2||%sat_area||rhessys5.10.10
|-
| 26||Litter Store||m2/m2||litter_store||rhessys5.10.12
|-
| 27||Percent Snow Cover||m2/m2||%snow_cover||rhessys5.10.12
|}

== Basin Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Gross Photosynthesis||gC/m2||gpsn
|-
| 6||Plant Maintenance Respiration||mC/m2||plant_resp
|-
| 7||Soil Respiration||gC/m2/day||soil_resp||rhessys5.10.11
|-
| 8||Nitrate N||gN/m2||nitrate
|-
| 9||Mineralized N||gN/m2||sminn
|-
| 10||Plant C||kgC/m2||plantc
|-
| 11||Plant N||kgN/m2||plantn
|-
| 12||Litter C||kgC/m2||litrc
|-
| 13||Litter N||kgN/m2||litrn
|-
| 14||Soil C||kgC/m2||soilc
|-
| 15||Soil N||kgN/m2||soiln
|-
| 16||Streamflow Nitrate||gN/m2/day||streamflow_NO3
|-
| 17||Denitrification||gN/m2/day||denitrif
|-
| 18||Nitrification||gN/m2/day||nitrif
|-
| 19||Dissolved Organic Carbon loss||gC/m2/day||DOC
|-
| 20||Dissolved Organic Nitrogen loss||gN/m2/day||DON
|}

== Basin Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Total Stream Outflow||mm||streamflow
|-
| 5||Nitrate to Stream||gN/m2||streamflow_NO3
|-
| 6||Denitrification||gN/m2||denitrif
|-
| 7||Dissolved Organic Carbon loss||gC/m2||DOC
|-
| 8||Dissolved Organic Nitrogen loss||gN/m2||DON
|-
| 9||Evapotranspiration||mm/m2||et
|-
| 10||Net Photosynthesis||gC/m2||psn
|-
| 11||Leaf Area Index||m2/m2||lai
|-
| 12||Nitrification||gN/m2||nitrif
|-
| 13||Mineralized Nitrate||gN/m2||mineralized
|-
| 14||Vegetation Nitrogen Uptake||gN/m2||uptake
|}

== Basin Yearly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Total Stream Outflow||mm||streamflow
|-
| 4||Nitrate to Stream||gN/m2||streamflow_NO3
|-
| 5||Denitrification||gN/m2||denitrif
|-
| 6||Dissolved Organic Carbon loss||gC/m2||DOC
|-
| 7||Dissolved Organic Nitrogen loss||gN/m2||DON
|-
| 8||Evapotranspiration||mm/m2||et
|-
| 9||Net Photosynthesis||gC/m2||psn
|-
| 10||Average Leaf Area Index||m2/m2||lai
|-
| 11||Nitrification||gN/m2||nitrif
|-
| 12||Mineralized N||gN/m2||mineralized
|-
| 13||Vegetation Uptake||gN/m2||uptake
|-
| 14||Number Threshold||?||num_thresh
|}

== Basin Yearly Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Year|| || ||rhessys5.10.5
|-
| 2||Basin ID|| || ||rhessys5.10.5
|-
| 3||Gross Photosynthesis||gC/m2||gpsn||rhessys5.10.5
|-
| 4||Plant Respiration||mC/m2||plantresp||rhessys5.10.5
|-
| 5||New Carbon||mC/m2||newC||rhessys5.10.5
|-
| 6||?Soilhr?||??||soilhr||rhessys5.10.5
|-
| 7||?Streamflow Nitrate?||??||strN||rhessys5.10.5
|-
| 8||Denitrification||gN/m2||denitrif||rhessys5.10.5
|-
|
|}

== Hillslope Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Rain Throughfall||mm||rain_thr
|-
| 7||Snow Throughfall||mm||snow_thr
|-
| 8||Saturation Deficit||mm of depth||sat_def_z
|-
| 9||Saturation Deficit||mm of water||sat_def
|-
| 10||Unsaturated Storage||mm||unsat_stor
|-
| 11||Unsaturated Drainage||mm||unsat_drain
|-
| 12||Capillary Rise||mm||cap
|-
| 13||Evaporation||mm||evap
|-
| 14||Snowpack Depth||mm||snow
|-
| 15||Transpiration||mm||trans
|-
| 16||Baseflow||mm||baseflow
|-
| 17||Return Flow||mm||return
|-
| 18||Total Stream Outflow||mm||streamflow
|-
| 19||Net Photosynthesis||kgC/m2||psn
|-
| 20||Leaf Area Index||m2/m2||lai
|-
| 21||Groundwater Output||mm||gw.Qout||rhessys5.10.5
|-
| 22||Groundwater Nitrate Output||mm||gw.Nout||rhessys5.10.5
|-
| 23||Groundwater Store||mm||gw.storage||rhessys5.10.5
|-
| 24||Groundwater Nitrate Store||mm||gw.N03||rhessys5.10.5
|}

== Hillslope Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Gross Photosynthesis||gC/m2||gpsn
|-
| 7||Maint Respiration||mC/m2||resp
|-
| 8||Nitrate N||gN/m2||nitrate
|-
| 9||Mineralized N||gN/m2||sminn
|-
| 10||Plant C||kgC/m2||plantc
|-
| 11||Plant N||kgN/m2||plantn
|-
| 12||Litter C||kgC/m2||litrc
|-
| 13||Litter N||kgN/m2||litrn
|-
| 14||Soil C||kgC/m2||soilc
|-
| 15||Soil N||kgN/m2||soiln
|-
| 16||Streamflow Nitrate||gN/m2/day||streamflow_NO3
|-
| 17||Streamflow||mm/day||streamflow
|-
| 18||Denitrification||gN/m2/day||denitrif
|-
| 19||Nitrification||gN/m2/day||nitrif
|-
| 20||Dissolved Organic Carbon loss||gC/m2/day||DOC
|-
| 21||Dissolved Organic Nitrogen loss||gN/m2/day||DON
|-
|
|}

== Hillslope Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| || ||rhessys5.10.7
|-
| 2||Year|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Streamflow||mm||streamflow
|-
| 5||Streamflow Nitrate||gN/m2/day||streamflow_N03
|-
| 6||Denitrification||gN/m2/day||denitrif
|-
| 7||Dissolved Organic Carbon Loss||gC/m2/day||DOC
|-
| 8||Dissolved Organic Nitrogen Loss||gN/m2/day||DON
|-
| 9||Evapotranspiration||mm/m2||et
|-
| 10||Net Photosynthesis||gC/m2||psn
|-
| 11||Leaf Area Index||m2/m2||lai
|-
| 12||Nitrification||gN/m2||nitrif
|-
| 13||Mineralized N||gN/m2||mineralized
|-
| 14||Vegetation Uptake||gN/m2||uptake
|}

== Hillslope Yearly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| || ||rhessys5.10.7
|-
| 2||Hillslope ID|| ||
|-
| 3||Streamflow||mm||streamflow
|-
| 4||Nitrate to Stream||gN/m2||streamflow_N03
|-
| 5||Denitrification||gN/m2||denitrif
|-
| 6||Dissolved Organic Carbon loss||gC/m2||DOC
|-
| 7||Dissolved Organic Nitrogen loss||gN/m2||DON
|-
| 8||Evapotranspiration||mm/m2||et
|-
| 9||Net Photosynthesis||gC/m2||psn
|-
| 10||Mineralized N||gN/m2||mineralized
|-
| 11||Vegetation Uptake||gN/m2||uptake
|}

== Zone Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Rainfall||mm||rain
|-
| 8||Snowfall||mm||snow
|-
| 9||Daytime Mean Air Temperature||C||tday
|-
| 10||Average Daily Temperature||C||tavg
|-
| 11||Vapour Pressure Deficit||Pa||vpd
|-
| 12||Direct Radiation||KJ/m2||Kdown_direct
|-
| 13||Diffuse Radiation||KJ/m2||Kdown_diffuse
|-
| 14||Direct PAR Radiation||KJ/m2||PAR_direct
|-
| 15||Diffuse PAR Radiation||KJ/m2||PAR_diffuse
|}

== Zone Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Hillslope ID|| ||
|-
| 5||Zone ID|| ||
|-
| 6||Precipitation||mm||precip
|-
| 7||Direct Radiation||KJ/m2||K_direct
|-
| 8||Diffuse Radiation||KJ/m2||K_diffuse
|-
| 9||Average Max Daily Temperature||C||tmax
|-
| 10||Average Min Daily Temperature||C||tmin
|}

== Patch Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Rain Throughfall||mm||rain_thr
|-
| 9||Detention Store||mm||detention_store||rhessys5.10.10
|-
| 10||Saturation Deficit (depth)||mm of depth||sat_def_z
|-
| 11||Saturation Deficit (water)||mm of water||sat_def
|-
| 12||Unsaturated Storage||mm||unsat_stor
|-
| 13||Unsaturated Drainage||mm||unsat_drain
|-
| 14||Capillary Rise||mm||cap
|-
| 15||Return Flow||mm||return
|-
| 16||Evaporation||mm||evap
|-
| 17||Snowpack Depth||mm||snow
|-
| 18||Transpiration||mm||trans
|-
| 19||Subsurface Flow to Stream||mm||Qin||rhessys5.10.9
|-
| 20||Subsurface Flow to Stream||mm||Qout||rhessys5.10.9
|-
| 21||Net Photosynthesis||kgC/m2||psn
|-
| 22||Rooting Zone Saturation||?||root_zone.S
|-
| 23||Litter Rain Stored||mm||litter.rain_stor||rhessys5.10.10
|-
| 24||Litter Percent Saturation||m2/m2 ?||litter.S||rhessys5.10.9
|}

== Patch Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Leaf Area Index||m2/m2||lai
|-
| 9||Plant C||kgC/m2||plantc
|-
| 10||Net Photosynthesis||gC/m2||net_psn
|-
| 11||Plant Respiration||gC/m2/day||plant_resp||rhessys5.10.11
|-
| 12||Soil Respiration||gC/m2/day||soil_resp||rhessys5.10.11
|-
| 13||Labile Litter C||kgC/m2||litr1c
|-
| 14||Cellulose Litter C||kgC/m2||litr2c
|-
| 15||Shielded Cellulose Litter C||kgC/m2||litr3c
|-
| 16||Lignan Litter C||kgC/m2||litr4c
|-
| 17||Litter Rain Capacity||mm||lit.rain_cap||rhessys5.10.10
|-
| 18||Fast Soil C||kgC/m2||soil1c
|-
| 19||Medium Soil C||kgC/m2||soil2c
|-
| 20||Slow Soil C||kgC/m2||soil3c
|-
| 21||Recalcitrant Soil C||kgC/m2||soil4c
|-
| 22||Denitrification||gN/m2||denitrif
|-
| 23||Net Nitrate Flux (+in)||gN/m2||netleach
|-
| 24||Soil Nitrate||gN/m2||soilNO3
|-
| 25||Streamflow N||gN/m2||streamN03
|-
| 26||Surface N||gN/m2||surfaceN03
|-
| 27||Canopy Height||m||height
|-
| 28||Nitrogen Uptake||??||N-uptake
|-
| 29||Area||cells||area
|}

== Patch Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Hillslope ID|| ||
|-
| 5||Zone ID|| ||
|-
| 6||Patch ID|| ||
|-
| 7||Net Nitrate Flux (+in)||gN/m2||leach
|-
| 8||Denitrification||gN/m2/month||denitrif
|-
| 9||Average Soil Moisture Deficit||mm||soil_moist_deficit
|-
| 10||Evapotranspiration||mm/m2/month||et
|-
| 11||Net Photosynthesis||gC/m2/month||psn
|-
| 12||Dissolved Organic Carbon loss||gC/m2/month||DOC
|-
| 13||Dissolved Organic Nitrogen loss||gN/m2/month||DON
|-
| 14||Average LAI||m2/m2||lai
|-
| 15||Nitrification||gN/m2/month||nitrif
|-
| 16||Mineralized N||gN/m2/month||mineralized
|-
| 17||Vegetation Uptake||gN/m2/month||uptake
|-
| 18||Theta||0-100 percent||theta
|}

== Patch Yearly ==

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Zone ID|| ||
|-
| 5||Patch ID|| ||
|-
| 6||Number of Days Below Sat. Threshold|| ||num_threshold_sat_def
|-
| 7||Net Nitrate Flux (+in)||gN/m2/year||leach
|-
| 8||Denitrification||gN/m2/year||denitrif
|-
| 9||Dissolved Organic Carbon loss||gC/m2/year||DOC_loss
|-
| 10||Dissolved Organic Nitrogen loss||gN/m2/year||DON_loss
|-
| 11||Net Photosynthesis||gC/m2||psn
|-
| 12||Evapotranspiration||mm/m2/year||et
|-
| 13||Maximum Leaf Area Index||m2/m2/year||lai
|-
| 14||Nitrification||gN/m2/year||nitrif
|-
| 15||Mineralized N||gN/m2year||mineralized
|-
| 16||Vegetation Uptake||gN/m2/year||uptake
|-
| 17||Theta||0-100 percent||theta
|}

== Patch Yearly Growth ==

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Zone ID|| ||
|-
| 5||Patch ID|| ||
|-
| 6||Litter C||kgC/m2||litter_c
|-
| 7||Soil C||kgC/m2/year||soil_c
|-
| 8||Litter N||kgN/m2/year||litter_n
|-
| 9||Soil N||kgN/m2/year||soil_n
|-
| 10||Soil Nitrate||gN/m2/year||nitrate
|-
| 11||Mineralized N||gN/m2||Sminn
|}

== Stratum Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Stratum ID|| ||
|-
| 9||Leaf Area Index||m2/m2||lai
|-
| 10||Evaporation||mm||evap
|-
| 11||APAR Radiation||KJ/m2||APAR_direct
|-
| 12||APAR Radiation||KJ/m2||APAR_diffuse
|-
| 13||Sublimation||mm||sublim
|-
| 14||Transpiration||mm||trans
|-
| 15||Aerodynamic Conductance||mm/s||ga
|-
| 16||Surface (non-vascular) Conductance||m/s||gsurf
|-
| 17||Canopy Conductance||mm/s||gs
|-
| 18||??||??||?psi?||rhessys5.10.10
|-
| 19||Respiration||kgC/m2||leaf_day_mr
|-
| 20||Net Photosynthesis||gC/m2||psn_to_cpool
|-
| 21||Rain Interception Storage||mm||rain_stored
|-
| 22||Snow Interception Storage||mm||snow_stored
|-
| 23||Rooting Zone Saturation||??||rootzone.S
|}

== Stratum Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Stratum ID|| ||
|-
| 9||Leaf Area Index||m2/m2||proj_lai
|-
| 10||Leaf C||gN/m2||leafc
|-
| 11||Dead Leaf C||gN/m2||dead_leafc
|-
| 12||Fine Root C||gN/m2||frootc
|-
| 13||Live Stem C||gN/m2||live_stemc
|-
| 14||Leaf C Store||gN/m2||leafc_store
|-
| 15||Dead Stem C||gN/m2||dead_stemc
|-
| 16||Live Coarse Root C||gN/m2||live_crootc
|-
| 17||Dead Coarse Root C||gN/m2||dead_crootc
|-
| 18||Coarse Woody Debris C||gN/m2||cwdc
|-
| 19||Maint Respiration||gC/m2||mresp
|-
| 20||Growth Respiration||gC/m2||gresp
|-
| 21||Net Photosynthesis||gC/m2||psn_to_cpool
|-
| 22||Stand Age||days||age||rhessys5.10.9
|}

== Stratum Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Hillslope ID|| ||
|-
| 5||Zone ID|| ||
|-
| 6||Patch ID|| ||
|-
| 7||Stratum ID|| ||
|-
| 8||Leaf Area Index||m2/m2||lai
|-
| 9||Net Photosynthesis||gC/m2||psn
|-
| 10||Mean Leaf Water Potential||mPa||lwp
|}

== Stratum Yearly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Zone ID|| ||
|-
| 5||Patch ID|| ||
|-
| 6||Stratum ID|| ||
|-
| 7||Net Photosynthesis||kgC/m2||psn
|-
| 8||Mean Leaf Water Potential||mPa||lwp
|}

Output Files

2010-07-16T18:52:19Z

Dgroulx: /* Patch Daily */

== Basin Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| || ||
|-
| 2||Month|| || ||
|-
| 3||Year|| || ||
|-
| 4||Basin ID|| || ||
|-
| 5||Rain Throughfall||mm||pot_surface_infil||
|-
| 6||Snow Throughfall||mm||snow_thr||
|-
| 7||Saturation Deficit-depth||mm of depth||sat_def_z||
|-
| 8||Saturation Deficit-volume||mm of water||sat_def||
|-
| 8||Rooting Zone Storage||mm of water||rz_storage||
|-
| 9||Unsaturated Storage||mm||unsat_stor||
|-
| 10||Unsaturated Drainage||mm||unsat_drain||
|-
| 11||Capillary Rise||mm||cap||
|-
| 12||Evaporation||mm||evap||
|-
| 13||Snowpack Depth||mm||snow||
|-
| 14||Transpiration||mm||trans||
|-
| 15||Baseflow||mm||baseflow||
|-
| 20||Return Flow||mm||return||
|-
| 17||Total Stream Outflow||mm||streamflow||
|-
| 18||Net Photosynthesis||kgC/m2||psn||
|-
| 19||Leaf Area Index||m2/m2||lai||
|-
| 20||Groundwater Output||mm||gw.Qout||
|-
| 21||Groundwater Nitrate Output||mm||gw.Nout||
|-
| 22||Groundwater Store||mm||gw.storage||rhessys5.10.5
|-
| 23||Groundwater Nitrate Store||mm||gw.NO3||rhessys5.10.5
|-
| 24||Detention Store||mm||detention_store||rhessys5.10.10
|-
| 25||Percent Saturated Area||m2/m2||%sat_area||rhessys5.10.10
|-
| 26||Litter Store||m2/m2||litter_store||rhessys5.10.12
|-
| 27||Percent Snow Cover||m2/m2||%snow_cover||rhessys5.10.12
|}

== Basin Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Gross Photosynthesis||gC/m2||gpsn
|-
| 6||Plant Maintenance Respiration||mC/m2||plant_resp
|-
| 7||Soil Respiration||gC/m2/day||soil_resp||rhessys5.10.11
|-
| 8||Nitrate N||gN/m2||nitrate
|-
| 9||Mineralized N||gN/m2||sminn
|-
| 10||Plant C||kgC/m2||plantc
|-
| 11||Plant N||kgN/m2||plantn
|-
| 12||Litter C||kgC/m2||litrc
|-
| 13||Litter N||kgN/m2||litrn
|-
| 14||Soil C||kgC/m2||soilc
|-
| 15||Soil N||kgN/m2||soiln
|-
| 16||Streamflow Nitrate||gN/m2/day||streamflow_NO3
|-
| 17||Denitrification||gN/m2/day||denitrif
|-
| 18||Nitrification||gN/m2/day||nitrif
|-
| 19||Dissolved Organic Carbon loss||gC/m2/day||DOC
|-
| 20||Dissolved Organic Nitrogen loss||gN/m2/day||DON
|}

== Basin Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Total Stream Outflow||mm||streamflow
|-
| 5||Nitrate to Stream||gN/m2||streamflow_NO3
|-
| 6||Denitrification||gN/m2||denitrif
|-
| 7||Dissolved Organic Carbon loss||gC/m2||DOC
|-
| 8||Dissolved Organic Nitrogen loss||gN/m2||DON
|-
| 9||Evapotranspiration||mm/m2||et
|-
| 10||Net Photosynthesis||gC/m2||psn
|-
| 11||Leaf Area Index||m2/m2||lai
|-
| 12||Nitrification||gN/m2||nitrif
|-
| 13||Mineralized Nitrate||gN/m2||mineralized
|-
| 14||Vegetation Nitrogen Uptake||gN/m2||uptake
|}

== Basin Yearly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Total Stream Outflow||mm||streamflow
|-
| 4||Nitrate to Stream||gN/m2||streamflow_NO3
|-
| 5||Denitrification||gN/m2||denitrif
|-
| 6||Dissolved Organic Carbon loss||gC/m2||DOC
|-
| 7||Dissolved Organic Nitrogen loss||gN/m2||DON
|-
| 8||Evapotranspiration||mm/m2||et
|-
| 9||Net Photosynthesis||gC/m2||psn
|-
| 10||Average Leaf Area Index||m2/m2||lai
|-
| 11||Nitrification||gN/m2||nitrif
|-
| 12||Mineralized N||gN/m2||mineralized
|-
| 13||Vegetation Uptake||gN/m2||uptake
|-
| 14||Number Threshold||?||num_thresh
|}

== Basin Yearly Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Year|| || ||rhessys5.10.5
|-
| 2||Basin ID|| || ||rhessys5.10.5
|-
| 3||Gross Photosynthesis||gC/m2||gpsn||rhessys5.10.5
|-
| 4||Plant Respiration||mC/m2||plantresp||rhessys5.10.5
|-
| 5||New Carbon||mC/m2||newC||rhessys5.10.5
|-
| 6||?Soilhr?||??||soilhr||rhessys5.10.5
|-
| 7||?Streamflow Nitrate?||??||strN||rhessys5.10.5
|-
| 8||Denitrification||gN/m2||denitrif||rhessys5.10.5
|-
|
|}

== Hillslope Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Rain Throughfall||mm||rain_thr
|-
| 7||Snow Throughfall||mm||snow_thr
|-
| 8||Saturation Deficit||mm of depth||sat_def_z
|-
| 9||Saturation Deficit||mm of water||sat_def
|-
| 10||Unsaturated Storage||mm||unsat_stor
|-
| 11||Unsaturated Drainage||mm||unsat_drain
|-
| 12||Capillary Rise||mm||cap
|-
| 13||Evaporation||mm||evap
|-
| 14||Snowpack Depth||mm||snow
|-
| 15||Transpiration||mm||trans
|-
| 16||Baseflow||mm||baseflow
|-
| 17||Return Flow||mm||return
|-
| 18||Total Stream Outflow||mm||streamflow
|-
| 19||Net Photosynthesis||kgC/m2||psn
|-
| 20||Leaf Area Index||m2/m2||lai
|-
| 21||Groundwater Output||mm||gw.Qout||rhessys5.10.5
|-
| 22||Groundwater Nitrate Output||mm||gw.Nout||rhessys5.10.5
|-
| 23||Groundwater Store||mm||gw.storage||rhessys5.10.5
|-
| 24||Groundwater Nitrate Store||mm||gw.N03||rhessys5.10.5
|}

== Hillslope Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Gross Photosynthesis||gC/m2||gpsn
|-
| 7||Maint Respiration||mC/m2||resp
|-
| 8||Nitrate N||gN/m2||nitrate
|-
| 9||Mineralized N||gN/m2||sminn
|-
| 10||Plant C||kgC/m2||plantc
|-
| 11||Plant N||kgN/m2||plantn
|-
| 12||Litter C||kgC/m2||litrc
|-
| 13||Litter N||kgN/m2||litrn
|-
| 14||Soil C||kgC/m2||soilc
|-
| 15||Soil N||kgN/m2||soiln
|-
| 16||Streamflow Nitrate||gN/m2/day||streamflow_NO3
|-
| 17||Streamflow||mm/day||streamflow
|-
| 18||Denitrification||gN/m2/day||denitrif
|-
| 19||Nitrification||gN/m2/day||nitrif
|-
| 20||Dissolved Organic Carbon loss||gC/m2/day||DOC
|-
| 21||Dissolved Organic Nitrogen loss||gN/m2/day||DON
|-
|
|}

== Hillslope Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| || ||rhessys5.10.7
|-
| 2||Year|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Streamflow||mm||streamflow
|-
| 5||Streamflow Nitrate||gN/m2/day||streamflow_N03
|-
| 6||Denitrification||gN/m2/day||denitrif
|-
| 7||Dissolved Organic Carbon Loss||gC/m2/day||DOC
|-
| 8||Dissolved Organic Nitrogen Loss||gN/m2/day||DON
|-
| 9||Evapotranspiration||mm/m2||et
|-
| 10||Net Photosynthesis||gC/m2||psn
|-
| 11||Leaf Area Index||m2/m2||lai
|-
| 12||Nitrification||gN/m2||nitrif
|-
| 13||Mineralized N||gN/m2||mineralized
|-
| 14||Vegetation Uptake||gN/m2||uptake
|}

== Hillslope Yearly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| || ||rhessys5.10.7
|-
| 2||Hillslope ID|| ||
|-
| 3||Streamflow||mm||streamflow
|-
| 4||Nitrate to Stream||gN/m2||streamflow_N03
|-
| 5||Denitrification||gN/m2||denitrif
|-
| 6||Dissolved Organic Carbon loss||gC/m2||DOC
|-
| 7||Dissolved Organic Nitrogen loss||gN/m2||DON
|-
| 8||Evapotranspiration||mm/m2||et
|-
| 9||Net Photosynthesis||gC/m2||psn
|-
| 10||Mineralized N||gN/m2||mineralized
|-
| 11||Vegetation Uptake||gN/m2||uptake
|}

== Zone Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Rainfall||mm||rain
|-
| 8||Snowfall||mm||snow
|-
| 9||Daytime Mean Air Temperature||C||tday
|-
| 10||Average Daily Temperature||C||tavg
|-
| 11||Vapour Pressure Deficit||Pa||vpd
|-
| 12||Direct Radiation||KJ/m2||Kdown_direct
|-
| 13||Diffuse Radiation||KJ/m2||Kdown_diffuse
|-
| 14||Direct PAR Radiation||KJ/m2||PAR_direct
|-
| 15||Diffuse PAR Radiation||KJ/m2||PAR_diffuse
|}

== Zone Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Hillslope ID|| ||
|-
| 5||Zone ID|| ||
|-
| 6||Precipitation||mm||precip
|-
| 7||Direct Radiation||KJ/m2||K_direct
|-
| 8||Diffuse Radiation||KJ/m2||K_diffuse
|-
| 9||Average Max Daily Temperature||C||tmax
|-
| 10||Average Min Daily Temperature||C||tmin
|}

== Patch Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Rain Throughfall||mm||rain_thr
|-
| 9||Detention Store||mm||detention_store||rhessys5.10.10
|-
| 10||Saturation Deficit (depth)||mm of depth||sat_def_z
|-
| 11||Saturation Deficit (water)||mm of water||sat_def
|-
| 12||Unsaturated Storage||mm||unsat_stor
|-
| 13||Unsaturated Drainage||mm||unsat_drain
|-
| 14||Capillary Rise||mm||cap
|-
| 15||Return Flow||mm||return
|-
| 16||Evaporation||mm||evap
|-
| 17||Snowpack Depth||mm||snow
|-
| 18||Transpiration||mm||trans
|-
| 19||Subsurface Flow to Stream||mm||Qin||rhessys5.10.9
|-
| 20||Subsurface Flow to Stream||mm||Qout||rhessys5.10.9
|-
| 21||Net Photosynthesis||kgC/m2||psn
|-
| 22||Rooting Zone Saturation||?||root_zone.S
|-
| 23||Litter Rain Stored||mm||litter.rain_stor||rhessys5.10.10
|-
| 24||Litter Percent Saturation||m2/m2 ?||litter.S||rhessys5.10.9
|}

== Patch Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Leaf Area Index||m2/m2||lai
|-
| 9||Plant C||kgC/m2||plantc
|-
| 10||Net Photosynthesis||gC/m2||net_psn
|-
| 11||Plant Respiration||gC/m2/day||plant_resp||rhessys5.10.11
|-
| 12||Soil Respiration||gC/m2/day||soil_resp||rhessys5.10.11
|-
| 13||Labile Litter C||kgC/m2||litr1c
|-
| 14||Cellulose Litter C||kgC/m2||litr2c
|-
| 15||Shielded Cellulose Litter C||kgC/m2||litr3c
|-
| 16||Lignan Litter C||kgC/m2||litr4c
|-
| 17||Litter Rain Capacity||mm||lit.rain_cap||rhessys5.10.10
|-
| 18||Fast Soil C||kgC/m2||soil1c
|-
| 19||Medium Soil C||kgC/m2||soil2c
|-
| 20||Slow Soil C||kgC/m2||soil3c
|-
| 21||Recalcitrant Soil C||kgC/m2||soil4c
|-
| 22||Denitrification||gN/m2||denitrif
|-
| 23||Net Nitrate Flux (+in)||gN/m2||netleach
|-
| 24||Soil Nitrate||gN/m2||soilNO3
|-
| 25||Streamflow N||gN/m2||streamN03
|-
| 26||Surface N||gN/m2||surfaceN03
|-
| 27||Canopy Height||m||height
|-
| 28||Nitrogen Uptake||??||N-uptake
|-
| 29||Area||cells||area
|}

== Patch Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Hillslope ID|| ||
|-
| 5||Zone ID|| ||
|-
| 6||Patch ID|| ||
|-
| 7||Net Nitrate Flux (+in)||gN/m2||leach
|-
| 8||Denitrification||gN/m2/month||denitrif
|-
| 9||Average Soil Moisture Deficit||mm||soil_moist_deficit
|-
| 10||Evapotranspiration||mm/m2/month||et
|-
| 11||Net Photosynthesis||gC/m2/month||psn
|-
| 12||Dissolved Organic Carbon loss||gC/m2/month||DOC
|-
| 13||Dissolved Organic Nitrogen loss||gN/m2/month||DON
|-
| 14||Average LAI||m2/m2||lai
|-
| 15||Nitrification||gN/m2/month||nitrif
|-
| 16||Mineralized N||gN/m2/month||mineralized
|-
| 17||Vegetation Uptake||gN/m2/month||uptake
|-
| 18||Theta||0-100 percent||theta
|}

== Patch Yearly ==

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Zone ID|| ||
|-
| 5||Patch ID|| ||
|-
| 6||Number of Days Below Sat. Threshold|| ||num_threshold_sat_def
|-
| 7||Net Nitrate Flux (+in)||gN/m2/year||leach
|-
| 8||Denitrification||gN/m2/year||denitrif
|-
| 9||Dissolved Organic Carbon loss||gC/m2/year||DOC_loss
|-
| 10||Dissolved Organic Nitrogen loss||gN/m2/year||DON_loss
|-
| 11||Net Photosynthesis||gC/m2||psn
|-
| 12||Evapotranspiration||mm/m2/year||et
|-
| 13||Maximum Leaf Area Index||m2/m2/year||lai
|-
| 14||Nitrification||gN/m2/year||nitrif
|-
| 15||Mineralized N||gN/m2year||mineralized
|-
| 16||Vegetation Uptake||gN/m2/year||uptake
|-
| 17||Theta||0-100 percent||theta
|}

== Patch Yearly Growth ==

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Zone ID|| ||
|-
| 5||Patch ID|| ||
|-
| 6||Litter C||kgC/m2||litter_c
|-
| 7||Soil C||kgC/m2/year||soil_c
|-
| 8||Litter N||kgN/m2/year||litter_n
|-
| 9||Soil N||kgN/m2/year||soil_n
|-
| 10||Soil Nitrate||gN/m2/year||nitrate
|-
| 11||Mineralized N||gN/m2||Sminn
|}

== Stratum Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Stratum ID|| ||
|-
| 9||Leaf Area Index||m2/m2||lai
|-
| 10||Evaporation||mm||evap
|-
| 11||APAR Radiation||KJ/m2||APAR_direct
|-
| 12||APAR Radiation||KJ/m2||APAR_diffuse
|-
| 13||Sublimation||mm||sublim
|-
| 14||Transpiration||mm||trans
|-
| 15||Aerodynamic Conductance||mm/s||ga
|-
| 16||Surface (non-vascular) Conductance||m/s||gsurf
|-
| 17||Canopy Conductance||mm/s||gs
|-
| 18||??||??||?psi?||rhessys5.10.10
|-
| 19||Respiration||kgC/m2||leaf_day_mr
|-
| 20||Net Photosynthesis||gC/m2||psn_to_cpool
|-
| 21||Rain Interception Storage||mm||rain_stored
|-
| 22||Snow Interception Storage||mm||snow_stored
|-
| 23||Rooting Zone Saturation||??||rootzone.S
|}

== Stratum Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Stratum ID|| ||
|-
| 9||Leaf Area Index||m2/m2||proj_lai
|-
| 10||Leaf C||gN/m2||leafc
|-
| 11||Dead Leaf C||gN/m2||dead_leafc
|-
| 12||Fine Root C||gN/m2||frootc
|-
| 13||Live Stem C||gN/m2||live_stemc
|-
| 14||Leaf C Store||gN/m2||leafc_store
|-
| 15||Dead Stem C||gN/m2||dead_stemc
|-
| 16||Live Coarse Root C||gN/m2||live_crootc
|-
| 17||Dead Coarse Root C||gN/m2||dead_crootc
|-
| 18||Coarse Woody Debris C||gN/m2||cwdc
|-
| 19||Maint Respiration||gC/m2||mresp
|-
| 20||Growth Respiration||gC/m2||gresp
|-
| 21||Net Photosynthesis||gC/m2||psn_to_cpool
|-
| 22||Stand Age||days||age||rhessys5.10.9
|}

== Stratum Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Hillslope ID|| ||
|-
| 5||Zone ID|| ||
|-
| 6||Patch ID|| ||
|-
| 7||Stratum ID|| ||
|-
| 8||Leaf Area Index||m2/m2||lai
|-
| 9||Net Photosynthesis||gC/m2||psn
|-
| 10||Mean Leaf Water Potential||mPa||lwp
|}

== Stratum Yearly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Zone ID|| ||
|-
| 5||Patch ID|| ||
|-
| 6||Stratum ID|| ||
|-
| 7||Net Photosynthesis||kgC/m2||psn
|-
| 8||Mean Leaf Water Potential||mPa||lwp
|}

Output Files

2010-07-16T18:52:09Z

Dgroulx: /* Zone Monthly */

== Basin Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| || ||
|-
| 2||Month|| || ||
|-
| 3||Year|| || ||
|-
| 4||Basin ID|| || ||
|-
| 5||Rain Throughfall||mm||pot_surface_infil||
|-
| 6||Snow Throughfall||mm||snow_thr||
|-
| 7||Saturation Deficit-depth||mm of depth||sat_def_z||
|-
| 8||Saturation Deficit-volume||mm of water||sat_def||
|-
| 8||Rooting Zone Storage||mm of water||rz_storage||
|-
| 9||Unsaturated Storage||mm||unsat_stor||
|-
| 10||Unsaturated Drainage||mm||unsat_drain||
|-
| 11||Capillary Rise||mm||cap||
|-
| 12||Evaporation||mm||evap||
|-
| 13||Snowpack Depth||mm||snow||
|-
| 14||Transpiration||mm||trans||
|-
| 15||Baseflow||mm||baseflow||
|-
| 20||Return Flow||mm||return||
|-
| 17||Total Stream Outflow||mm||streamflow||
|-
| 18||Net Photosynthesis||kgC/m2||psn||
|-
| 19||Leaf Area Index||m2/m2||lai||
|-
| 20||Groundwater Output||mm||gw.Qout||
|-
| 21||Groundwater Nitrate Output||mm||gw.Nout||
|-
| 22||Groundwater Store||mm||gw.storage||rhessys5.10.5
|-
| 23||Groundwater Nitrate Store||mm||gw.NO3||rhessys5.10.5
|-
| 24||Detention Store||mm||detention_store||rhessys5.10.10
|-
| 25||Percent Saturated Area||m2/m2||%sat_area||rhessys5.10.10
|-
| 26||Litter Store||m2/m2||litter_store||rhessys5.10.12
|-
| 27||Percent Snow Cover||m2/m2||%snow_cover||rhessys5.10.12
|}

== Basin Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Gross Photosynthesis||gC/m2||gpsn
|-
| 6||Plant Maintenance Respiration||mC/m2||plant_resp
|-
| 7||Soil Respiration||gC/m2/day||soil_resp||rhessys5.10.11
|-
| 8||Nitrate N||gN/m2||nitrate
|-
| 9||Mineralized N||gN/m2||sminn
|-
| 10||Plant C||kgC/m2||plantc
|-
| 11||Plant N||kgN/m2||plantn
|-
| 12||Litter C||kgC/m2||litrc
|-
| 13||Litter N||kgN/m2||litrn
|-
| 14||Soil C||kgC/m2||soilc
|-
| 15||Soil N||kgN/m2||soiln
|-
| 16||Streamflow Nitrate||gN/m2/day||streamflow_NO3
|-
| 17||Denitrification||gN/m2/day||denitrif
|-
| 18||Nitrification||gN/m2/day||nitrif
|-
| 19||Dissolved Organic Carbon loss||gC/m2/day||DOC
|-
| 20||Dissolved Organic Nitrogen loss||gN/m2/day||DON
|}

== Basin Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Total Stream Outflow||mm||streamflow
|-
| 5||Nitrate to Stream||gN/m2||streamflow_NO3
|-
| 6||Denitrification||gN/m2||denitrif
|-
| 7||Dissolved Organic Carbon loss||gC/m2||DOC
|-
| 8||Dissolved Organic Nitrogen loss||gN/m2||DON
|-
| 9||Evapotranspiration||mm/m2||et
|-
| 10||Net Photosynthesis||gC/m2||psn
|-
| 11||Leaf Area Index||m2/m2||lai
|-
| 12||Nitrification||gN/m2||nitrif
|-
| 13||Mineralized Nitrate||gN/m2||mineralized
|-
| 14||Vegetation Nitrogen Uptake||gN/m2||uptake
|}

== Basin Yearly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Total Stream Outflow||mm||streamflow
|-
| 4||Nitrate to Stream||gN/m2||streamflow_NO3
|-
| 5||Denitrification||gN/m2||denitrif
|-
| 6||Dissolved Organic Carbon loss||gC/m2||DOC
|-
| 7||Dissolved Organic Nitrogen loss||gN/m2||DON
|-
| 8||Evapotranspiration||mm/m2||et
|-
| 9||Net Photosynthesis||gC/m2||psn
|-
| 10||Average Leaf Area Index||m2/m2||lai
|-
| 11||Nitrification||gN/m2||nitrif
|-
| 12||Mineralized N||gN/m2||mineralized
|-
| 13||Vegetation Uptake||gN/m2||uptake
|-
| 14||Number Threshold||?||num_thresh
|}

== Basin Yearly Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Year|| || ||rhessys5.10.5
|-
| 2||Basin ID|| || ||rhessys5.10.5
|-
| 3||Gross Photosynthesis||gC/m2||gpsn||rhessys5.10.5
|-
| 4||Plant Respiration||mC/m2||plantresp||rhessys5.10.5
|-
| 5||New Carbon||mC/m2||newC||rhessys5.10.5
|-
| 6||?Soilhr?||??||soilhr||rhessys5.10.5
|-
| 7||?Streamflow Nitrate?||??||strN||rhessys5.10.5
|-
| 8||Denitrification||gN/m2||denitrif||rhessys5.10.5
|-
|
|}

== Hillslope Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Rain Throughfall||mm||rain_thr
|-
| 7||Snow Throughfall||mm||snow_thr
|-
| 8||Saturation Deficit||mm of depth||sat_def_z
|-
| 9||Saturation Deficit||mm of water||sat_def
|-
| 10||Unsaturated Storage||mm||unsat_stor
|-
| 11||Unsaturated Drainage||mm||unsat_drain
|-
| 12||Capillary Rise||mm||cap
|-
| 13||Evaporation||mm||evap
|-
| 14||Snowpack Depth||mm||snow
|-
| 15||Transpiration||mm||trans
|-
| 16||Baseflow||mm||baseflow
|-
| 17||Return Flow||mm||return
|-
| 18||Total Stream Outflow||mm||streamflow
|-
| 19||Net Photosynthesis||kgC/m2||psn
|-
| 20||Leaf Area Index||m2/m2||lai
|-
| 21||Groundwater Output||mm||gw.Qout||rhessys5.10.5
|-
| 22||Groundwater Nitrate Output||mm||gw.Nout||rhessys5.10.5
|-
| 23||Groundwater Store||mm||gw.storage||rhessys5.10.5
|-
| 24||Groundwater Nitrate Store||mm||gw.N03||rhessys5.10.5
|}

== Hillslope Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Gross Photosynthesis||gC/m2||gpsn
|-
| 7||Maint Respiration||mC/m2||resp
|-
| 8||Nitrate N||gN/m2||nitrate
|-
| 9||Mineralized N||gN/m2||sminn
|-
| 10||Plant C||kgC/m2||plantc
|-
| 11||Plant N||kgN/m2||plantn
|-
| 12||Litter C||kgC/m2||litrc
|-
| 13||Litter N||kgN/m2||litrn
|-
| 14||Soil C||kgC/m2||soilc
|-
| 15||Soil N||kgN/m2||soiln
|-
| 16||Streamflow Nitrate||gN/m2/day||streamflow_NO3
|-
| 17||Streamflow||mm/day||streamflow
|-
| 18||Denitrification||gN/m2/day||denitrif
|-
| 19||Nitrification||gN/m2/day||nitrif
|-
| 20||Dissolved Organic Carbon loss||gC/m2/day||DOC
|-
| 21||Dissolved Organic Nitrogen loss||gN/m2/day||DON
|-
|
|}

== Hillslope Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| || ||rhessys5.10.7
|-
| 2||Year|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Streamflow||mm||streamflow
|-
| 5||Streamflow Nitrate||gN/m2/day||streamflow_N03
|-
| 6||Denitrification||gN/m2/day||denitrif
|-
| 7||Dissolved Organic Carbon Loss||gC/m2/day||DOC
|-
| 8||Dissolved Organic Nitrogen Loss||gN/m2/day||DON
|-
| 9||Evapotranspiration||mm/m2||et
|-
| 10||Net Photosynthesis||gC/m2||psn
|-
| 11||Leaf Area Index||m2/m2||lai
|-
| 12||Nitrification||gN/m2||nitrif
|-
| 13||Mineralized N||gN/m2||mineralized
|-
| 14||Vegetation Uptake||gN/m2||uptake
|}

== Hillslope Yearly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| || ||rhessys5.10.7
|-
| 2||Hillslope ID|| ||
|-
| 3||Streamflow||mm||streamflow
|-
| 4||Nitrate to Stream||gN/m2||streamflow_N03
|-
| 5||Denitrification||gN/m2||denitrif
|-
| 6||Dissolved Organic Carbon loss||gC/m2||DOC
|-
| 7||Dissolved Organic Nitrogen loss||gN/m2||DON
|-
| 8||Evapotranspiration||mm/m2||et
|-
| 9||Net Photosynthesis||gC/m2||psn
|-
| 10||Mineralized N||gN/m2||mineralized
|-
| 11||Vegetation Uptake||gN/m2||uptake
|}

== Zone Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Rainfall||mm||rain
|-
| 8||Snowfall||mm||snow
|-
| 9||Daytime Mean Air Temperature||C||tday
|-
| 10||Average Daily Temperature||C||tavg
|-
| 11||Vapour Pressure Deficit||Pa||vpd
|-
| 12||Direct Radiation||KJ/m2||Kdown_direct
|-
| 13||Diffuse Radiation||KJ/m2||Kdown_diffuse
|-
| 14||Direct PAR Radiation||KJ/m2||PAR_direct
|-
| 15||Diffuse PAR Radiation||KJ/m2||PAR_diffuse
|}

== Zone Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Hillslope ID|| ||
|-
| 5||Zone ID|| ||
|-
| 6||Precipitation||mm||precip
|-
| 7||Direct Radiation||KJ/m2||K_direct
|-
| 8||Diffuse Radiation||KJ/m2||K_diffuse
|-
| 9||Average Max Daily Temperature||C||tmax
|-
| 10||Average Min Daily Temperature||C||tmin
|}

== Patch Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Rain Throughfall||mm||rain_thr
|-
| 9||Detention Store||mm||detention_store||rhessys5.10.10
|-
| 10||Saturation Deficit (depth)||mm of depth||sat_def_z
|-
| 11||Saturation Deficit (water)||mm of water||sat_def
|-
| 12||Unsaturated Storage||mm||unsat_stor
|-
| 13||Unsaturated Drainage||mm||unsat_drain
|-
| 14||Capillary Rise||mm||cap
|-
| 15||Return Flow||mm||return
|-
| 16||Evaporation||mm||evap
|-
| 17||Snowpack Depth||mm||snow
|-
| 18||Transpiration||mm||trans
|-
| 19||Subsurface Flow to Stream||mm||Qin||rhessys5.10.9
|-
| 20||Subsurface Flow to Stream||mm||Qout||rhessys5.10.9
|-
| 21||Net Photosynthesis||kgC/m2||psn
|-
| 22||Rooting Zone Saturation||?||root_zone.S
|-
| 23||Litter Rain Stored||mm||litter.rain_stor||rhessys5.10.10
|-
| 24||Litter Percent Saturation||m2/m2 ?||litter.S||rhessys5.10.9
|}

== Patch Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Leaf Area Index||m2/m2||lai
|-
| 9||Plant C||kgC/m2||plantc
|-
| 10||Net Photosynthesis||gC/m2||net_psn
|-
| 11||Plant Respiration||gC/m2/day||plant_resp||rhessys5.10.11
|-
| 12||Soil Respiration||gC/m2/day||soil_resp||rhessys5.10.11
|-
| 13||Labile Litter C||kgC/m2||litr1c
|-
| 14||Cellulose Litter C||kgC/m2||litr2c
|-
| 15||Shielded Cellulose Litter C||kgC/m2||litr3c
|-
| 16||Lignan Litter C||kgC/m2||litr4c
|-
| 17||Litter Rain Capacity||mm||lit.rain_cap||rhessys5.10.10
|-
| 18||Fast Soil C||kgC/m2||soil1c
|-
| 19||Medium Soil C||kgC/m2||soil2c
|-
| 20||Slow Soil C||kgC/m2||soil3c
|-
| 21||Recalcitrant Soil C||kgC/m2||soil4c
|-
| 22||Denitrification||gN/m2||denitrif
|-
| 23||Net Nitrate Flux (+in)||gN/m2||netleach
|-
| 24||Soil Nitrate||gN/m2||soilNO3
|-
| 25||Streamflow N||gN/m2||streamN03
|-
| 26||Surface N||gN/m2||surfaceN03
|-
| 27||Canopy Height||m||height
|-
| 28||Nitrogen Uptake||??||N-uptake
|-
| 29||Area||cells||area
|}

== Patch Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Hillslope ID|| ||
|-
| 5||Zone ID|| ||
|-
| 6||Patch ID|| ||
|-
| 7||Net Nitrate Flux (+in)||gN/m2||leach
|-
| 8||Denitrification||gN/m2/month||denitrif
|-
| 9||Average Soil Moisture Deficit||mm||soil_moist_deficit
|-
| 10||Evapotranspiration||mm/m2/month||et
|-
| 11||Net Photosynthesis||gC/m2/month||psn
|-
| 12||Dissolved Organic Carbon loss||gC/m2/month||DOC
|-
| 13||Dissolved Organic Nitrogen loss||gN/m2/month||DON
|-
| 14||Average LAI||m2/m2||lai
|-
| 15||Nitrification||gN/m2/month||nitrif
|-
| 16||Mineralized N||gN/m2/month||mineralized
|-
| 17||Vegetation Uptake||gN/m2/month||uptake
|-
| 18||Theta||0-100 percent||theta
|}

== Patch Yearly ==

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Zone ID|| ||
|-
| 5||Patch ID|| ||
|-
| 6||Number of Days Below Sat. Threshold|| ||num_threshold_sat_def
|-
| 7||Net Nitrate Flux (+in)||gN/m2/year||leach
|-
| 8||Denitrification||gN/m2/year||denitrif
|-
| 9||Dissolved Organic Carbon loss||gC/m2/year||DOC_loss
|-
| 10||Dissolved Organic Nitrogen loss||gN/m2/year||DON_loss
|-
| 11||Net Photosynthesis||gC/m2||psn
|-
| 12||Evapotranspiration||mm/m2/year||et
|-
| 13||Maximum Leaf Area Index||m2/m2/year||lai
|-
| 14||Nitrification||gN/m2/year||nitrif
|-
| 15||Mineralized N||gN/m2year||mineralized
|-
| 16||Vegetation Uptake||gN/m2/year||uptake
|-
| 17||Theta||0-100 percent||theta
|}

== Patch Yearly Growth ==

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Zone ID|| ||
|-
| 5||Patch ID|| ||
|-
| 6||Litter C||kgC/m2||litter_c
|-
| 7||Soil C||kgC/m2/year||soil_c
|-
| 8||Litter N||kgN/m2/year||litter_n
|-
| 9||Soil N||kgN/m2/year||soil_n
|-
| 10||Soil Nitrate||gN/m2/year||nitrate
|-
| 11||Mineralized N||gN/m2||Sminn
|}

== Stratum Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Stratum ID|| ||
|-
| 9||Leaf Area Index||m2/m2||lai
|-
| 10||Evaporation||mm||evap
|-
| 11||APAR Radiation||KJ/m2||APAR_direct
|-
| 12||APAR Radiation||KJ/m2||APAR_diffuse
|-
| 13||Sublimation||mm||sublim
|-
| 14||Transpiration||mm||trans
|-
| 15||Aerodynamic Conductance||mm/s||ga
|-
| 16||Surface (non-vascular) Conductance||m/s||gsurf
|-
| 17||Canopy Conductance||mm/s||gs
|-
| 18||??||??||?psi?||rhessys5.10.10
|-
| 19||Respiration||kgC/m2||leaf_day_mr
|-
| 20||Net Photosynthesis||gC/m2||psn_to_cpool
|-
| 21||Rain Interception Storage||mm||rain_stored
|-
| 22||Snow Interception Storage||mm||snow_stored
|-
| 23||Rooting Zone Saturation||??||rootzone.S
|}

== Stratum Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Stratum ID|| ||
|-
| 9||Leaf Area Index||m2/m2||proj_lai
|-
| 10||Leaf C||gN/m2||leafc
|-
| 11||Dead Leaf C||gN/m2||dead_leafc
|-
| 12||Fine Root C||gN/m2||frootc
|-
| 13||Live Stem C||gN/m2||live_stemc
|-
| 14||Leaf C Store||gN/m2||leafc_store
|-
| 15||Dead Stem C||gN/m2||dead_stemc
|-
| 16||Live Coarse Root C||gN/m2||live_crootc
|-
| 17||Dead Coarse Root C||gN/m2||dead_crootc
|-
| 18||Coarse Woody Debris C||gN/m2||cwdc
|-
| 19||Maint Respiration||gC/m2||mresp
|-
| 20||Growth Respiration||gC/m2||gresp
|-
| 21||Net Photosynthesis||gC/m2||psn_to_cpool
|-
| 22||Stand Age||days||age||rhessys5.10.9
|}

== Stratum Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Hillslope ID|| ||
|-
| 5||Zone ID|| ||
|-
| 6||Patch ID|| ||
|-
| 7||Stratum ID|| ||
|-
| 8||Leaf Area Index||m2/m2||lai
|-
| 9||Net Photosynthesis||gC/m2||psn
|-
| 10||Mean Leaf Water Potential||mPa||lwp
|}

== Stratum Yearly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Zone ID|| ||
|-
| 5||Patch ID|| ||
|-
| 6||Stratum ID|| ||
|-
| 7||Net Photosynthesis||kgC/m2||psn
|-
| 8||Mean Leaf Water Potential||mPa||lwp
|}

Output Files

2010-07-16T18:51:56Z

Dgroulx: /* Zone Daily */

== Basin Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| || ||
|-
| 2||Month|| || ||
|-
| 3||Year|| || ||
|-
| 4||Basin ID|| || ||
|-
| 5||Rain Throughfall||mm||pot_surface_infil||
|-
| 6||Snow Throughfall||mm||snow_thr||
|-
| 7||Saturation Deficit-depth||mm of depth||sat_def_z||
|-
| 8||Saturation Deficit-volume||mm of water||sat_def||
|-
| 8||Rooting Zone Storage||mm of water||rz_storage||
|-
| 9||Unsaturated Storage||mm||unsat_stor||
|-
| 10||Unsaturated Drainage||mm||unsat_drain||
|-
| 11||Capillary Rise||mm||cap||
|-
| 12||Evaporation||mm||evap||
|-
| 13||Snowpack Depth||mm||snow||
|-
| 14||Transpiration||mm||trans||
|-
| 15||Baseflow||mm||baseflow||
|-
| 20||Return Flow||mm||return||
|-
| 17||Total Stream Outflow||mm||streamflow||
|-
| 18||Net Photosynthesis||kgC/m2||psn||
|-
| 19||Leaf Area Index||m2/m2||lai||
|-
| 20||Groundwater Output||mm||gw.Qout||
|-
| 21||Groundwater Nitrate Output||mm||gw.Nout||
|-
| 22||Groundwater Store||mm||gw.storage||rhessys5.10.5
|-
| 23||Groundwater Nitrate Store||mm||gw.NO3||rhessys5.10.5
|-
| 24||Detention Store||mm||detention_store||rhessys5.10.10
|-
| 25||Percent Saturated Area||m2/m2||%sat_area||rhessys5.10.10
|-
| 26||Litter Store||m2/m2||litter_store||rhessys5.10.12
|-
| 27||Percent Snow Cover||m2/m2||%snow_cover||rhessys5.10.12
|}

== Basin Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Gross Photosynthesis||gC/m2||gpsn
|-
| 6||Plant Maintenance Respiration||mC/m2||plant_resp
|-
| 7||Soil Respiration||gC/m2/day||soil_resp||rhessys5.10.11
|-
| 8||Nitrate N||gN/m2||nitrate
|-
| 9||Mineralized N||gN/m2||sminn
|-
| 10||Plant C||kgC/m2||plantc
|-
| 11||Plant N||kgN/m2||plantn
|-
| 12||Litter C||kgC/m2||litrc
|-
| 13||Litter N||kgN/m2||litrn
|-
| 14||Soil C||kgC/m2||soilc
|-
| 15||Soil N||kgN/m2||soiln
|-
| 16||Streamflow Nitrate||gN/m2/day||streamflow_NO3
|-
| 17||Denitrification||gN/m2/day||denitrif
|-
| 18||Nitrification||gN/m2/day||nitrif
|-
| 19||Dissolved Organic Carbon loss||gC/m2/day||DOC
|-
| 20||Dissolved Organic Nitrogen loss||gN/m2/day||DON
|}

== Basin Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Total Stream Outflow||mm||streamflow
|-
| 5||Nitrate to Stream||gN/m2||streamflow_NO3
|-
| 6||Denitrification||gN/m2||denitrif
|-
| 7||Dissolved Organic Carbon loss||gC/m2||DOC
|-
| 8||Dissolved Organic Nitrogen loss||gN/m2||DON
|-
| 9||Evapotranspiration||mm/m2||et
|-
| 10||Net Photosynthesis||gC/m2||psn
|-
| 11||Leaf Area Index||m2/m2||lai
|-
| 12||Nitrification||gN/m2||nitrif
|-
| 13||Mineralized Nitrate||gN/m2||mineralized
|-
| 14||Vegetation Nitrogen Uptake||gN/m2||uptake
|}

== Basin Yearly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Total Stream Outflow||mm||streamflow
|-
| 4||Nitrate to Stream||gN/m2||streamflow_NO3
|-
| 5||Denitrification||gN/m2||denitrif
|-
| 6||Dissolved Organic Carbon loss||gC/m2||DOC
|-
| 7||Dissolved Organic Nitrogen loss||gN/m2||DON
|-
| 8||Evapotranspiration||mm/m2||et
|-
| 9||Net Photosynthesis||gC/m2||psn
|-
| 10||Average Leaf Area Index||m2/m2||lai
|-
| 11||Nitrification||gN/m2||nitrif
|-
| 12||Mineralized N||gN/m2||mineralized
|-
| 13||Vegetation Uptake||gN/m2||uptake
|-
| 14||Number Threshold||?||num_thresh
|}

== Basin Yearly Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Year|| || ||rhessys5.10.5
|-
| 2||Basin ID|| || ||rhessys5.10.5
|-
| 3||Gross Photosynthesis||gC/m2||gpsn||rhessys5.10.5
|-
| 4||Plant Respiration||mC/m2||plantresp||rhessys5.10.5
|-
| 5||New Carbon||mC/m2||newC||rhessys5.10.5
|-
| 6||?Soilhr?||??||soilhr||rhessys5.10.5
|-
| 7||?Streamflow Nitrate?||??||strN||rhessys5.10.5
|-
| 8||Denitrification||gN/m2||denitrif||rhessys5.10.5
|-
|
|}

== Hillslope Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Rain Throughfall||mm||rain_thr
|-
| 7||Snow Throughfall||mm||snow_thr
|-
| 8||Saturation Deficit||mm of depth||sat_def_z
|-
| 9||Saturation Deficit||mm of water||sat_def
|-
| 10||Unsaturated Storage||mm||unsat_stor
|-
| 11||Unsaturated Drainage||mm||unsat_drain
|-
| 12||Capillary Rise||mm||cap
|-
| 13||Evaporation||mm||evap
|-
| 14||Snowpack Depth||mm||snow
|-
| 15||Transpiration||mm||trans
|-
| 16||Baseflow||mm||baseflow
|-
| 17||Return Flow||mm||return
|-
| 18||Total Stream Outflow||mm||streamflow
|-
| 19||Net Photosynthesis||kgC/m2||psn
|-
| 20||Leaf Area Index||m2/m2||lai
|-
| 21||Groundwater Output||mm||gw.Qout||rhessys5.10.5
|-
| 22||Groundwater Nitrate Output||mm||gw.Nout||rhessys5.10.5
|-
| 23||Groundwater Store||mm||gw.storage||rhessys5.10.5
|-
| 24||Groundwater Nitrate Store||mm||gw.N03||rhessys5.10.5
|}

== Hillslope Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Gross Photosynthesis||gC/m2||gpsn
|-
| 7||Maint Respiration||mC/m2||resp
|-
| 8||Nitrate N||gN/m2||nitrate
|-
| 9||Mineralized N||gN/m2||sminn
|-
| 10||Plant C||kgC/m2||plantc
|-
| 11||Plant N||kgN/m2||plantn
|-
| 12||Litter C||kgC/m2||litrc
|-
| 13||Litter N||kgN/m2||litrn
|-
| 14||Soil C||kgC/m2||soilc
|-
| 15||Soil N||kgN/m2||soiln
|-
| 16||Streamflow Nitrate||gN/m2/day||streamflow_NO3
|-
| 17||Streamflow||mm/day||streamflow
|-
| 18||Denitrification||gN/m2/day||denitrif
|-
| 19||Nitrification||gN/m2/day||nitrif
|-
| 20||Dissolved Organic Carbon loss||gC/m2/day||DOC
|-
| 21||Dissolved Organic Nitrogen loss||gN/m2/day||DON
|-
|
|}

== Hillslope Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Month|| || ||rhessys5.10.7
|-
| 2||Year|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Streamflow||mm||streamflow
|-
| 5||Streamflow Nitrate||gN/m2/day||streamflow_N03
|-
| 6||Denitrification||gN/m2/day||denitrif
|-
| 7||Dissolved Organic Carbon Loss||gC/m2/day||DOC
|-
| 8||Dissolved Organic Nitrogen Loss||gN/m2/day||DON
|-
| 9||Evapotranspiration||mm/m2||et
|-
| 10||Net Photosynthesis||gC/m2||psn
|-
| 11||Leaf Area Index||m2/m2||lai
|-
| 12||Nitrification||gN/m2||nitrif
|-
| 13||Mineralized N||gN/m2||mineralized
|-
| 14||Vegetation Uptake||gN/m2||uptake
|}

== Hillslope Yearly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| || ||rhessys5.10.7
|-
| 2||Hillslope ID|| ||
|-
| 3||Streamflow||mm||streamflow
|-
| 4||Nitrate to Stream||gN/m2||streamflow_N03
|-
| 5||Denitrification||gN/m2||denitrif
|-
| 6||Dissolved Organic Carbon loss||gC/m2||DOC
|-
| 7||Dissolved Organic Nitrogen loss||gN/m2||DON
|-
| 8||Evapotranspiration||mm/m2||et
|-
| 9||Net Photosynthesis||gC/m2||psn
|-
| 10||Mineralized N||gN/m2||mineralized
|-
| 11||Vegetation Uptake||gN/m2||uptake
|}

== Zone Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''Included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Rainfall||mm||rain
|-
| 8||Snowfall||mm||snow
|-
| 9||Daytime Mean Air Temperature||C||tday
|-
| 10||Average Daily Temperature||C||tavg
|-
| 11||Vapour Pressure Deficit||Pa||vpd
|-
| 12||Direct Radiation||KJ/m2||Kdown_direct
|-
| 13||Diffuse Radiation||KJ/m2||Kdown_diffuse
|-
| 14||Direct PAR Radiation||KJ/m2||PAR_direct
|-
| 15||Diffuse PAR Radiation||KJ/m2||PAR_diffuse
|}

== Zone Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Hillslope ID|| ||
|-
| 5||Zone ID|| ||
|-
| 6||Precipitation||mm||precip
|-
| 7||Direct Radiation||KJ/m2||K_direct
|-
| 8||Diffuse Radiation||KJ/m2||K_diffuse
|-
| 9||Average Max Daily Temperature||C||tmax
|-
| 10||Average Min Daily Temperature||C||tmin
|}

== Patch Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Rain Throughfall||mm||rain_thr
|-
| 9||Detention Store||mm||detention_store||rhessys5.10.10
|-
| 10||Saturation Deficit (depth)||mm of depth||sat_def_z
|-
| 11||Saturation Deficit (water)||mm of water||sat_def
|-
| 12||Unsaturated Storage||mm||unsat_stor
|-
| 13||Unsaturated Drainage||mm||unsat_drain
|-
| 14||Capillary Rise||mm||cap
|-
| 15||Return Flow||mm||return
|-
| 16||Evaporation||mm||evap
|-
| 17||Snowpack Depth||mm||snow
|-
| 18||Transpiration||mm||trans
|-
| 19||Subsurface Flow to Stream||mm||Qin||rhessys5.10.9
|-
| 20||Subsurface Flow to Stream||mm||Qout||rhessys5.10.9
|-
| 21||Net Photosynthesis||kgC/m2||psn
|-
| 22||Rooting Zone Saturation||?||root_zone.S
|-
| 23||Litter Rain Stored||mm||litter.rain_stor||rhessys5.10.10
|-
| 24||Litter Percent Saturation||m2/m2 ?||litter.S||rhessys5.10.9
|}

== Patch Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Leaf Area Index||m2/m2||lai
|-
| 9||Plant C||kgC/m2||plantc
|-
| 10||Net Photosynthesis||gC/m2||net_psn
|-
| 11||Plant Respiration||gC/m2/day||plant_resp||rhessys5.10.11
|-
| 12||Soil Respiration||gC/m2/day||soil_resp||rhessys5.10.11
|-
| 13||Labile Litter C||kgC/m2||litr1c
|-
| 14||Cellulose Litter C||kgC/m2||litr2c
|-
| 15||Shielded Cellulose Litter C||kgC/m2||litr3c
|-
| 16||Lignan Litter C||kgC/m2||litr4c
|-
| 17||Litter Rain Capacity||mm||lit.rain_cap||rhessys5.10.10
|-
| 18||Fast Soil C||kgC/m2||soil1c
|-
| 19||Medium Soil C||kgC/m2||soil2c
|-
| 20||Slow Soil C||kgC/m2||soil3c
|-
| 21||Recalcitrant Soil C||kgC/m2||soil4c
|-
| 22||Denitrification||gN/m2||denitrif
|-
| 23||Net Nitrate Flux (+in)||gN/m2||netleach
|-
| 24||Soil Nitrate||gN/m2||soilNO3
|-
| 25||Streamflow N||gN/m2||streamN03
|-
| 26||Surface N||gN/m2||surfaceN03
|-
| 27||Canopy Height||m||height
|-
| 28||Nitrogen Uptake||??||N-uptake
|-
| 29||Area||cells||area
|}

== Patch Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Hillslope ID|| ||
|-
| 5||Zone ID|| ||
|-
| 6||Patch ID|| ||
|-
| 7||Net Nitrate Flux (+in)||gN/m2||leach
|-
| 8||Denitrification||gN/m2/month||denitrif
|-
| 9||Average Soil Moisture Deficit||mm||soil_moist_deficit
|-
| 10||Evapotranspiration||mm/m2/month||et
|-
| 11||Net Photosynthesis||gC/m2/month||psn
|-
| 12||Dissolved Organic Carbon loss||gC/m2/month||DOC
|-
| 13||Dissolved Organic Nitrogen loss||gN/m2/month||DON
|-
| 14||Average LAI||m2/m2||lai
|-
| 15||Nitrification||gN/m2/month||nitrif
|-
| 16||Mineralized N||gN/m2/month||mineralized
|-
| 17||Vegetation Uptake||gN/m2/month||uptake
|-
| 18||Theta||0-100 percent||theta
|}

== Patch Yearly ==

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Zone ID|| ||
|-
| 5||Patch ID|| ||
|-
| 6||Number of Days Below Sat. Threshold|| ||num_threshold_sat_def
|-
| 7||Net Nitrate Flux (+in)||gN/m2/year||leach
|-
| 8||Denitrification||gN/m2/year||denitrif
|-
| 9||Dissolved Organic Carbon loss||gC/m2/year||DOC_loss
|-
| 10||Dissolved Organic Nitrogen loss||gN/m2/year||DON_loss
|-
| 11||Net Photosynthesis||gC/m2||psn
|-
| 12||Evapotranspiration||mm/m2/year||et
|-
| 13||Maximum Leaf Area Index||m2/m2/year||lai
|-
| 14||Nitrification||gN/m2/year||nitrif
|-
| 15||Mineralized N||gN/m2year||mineralized
|-
| 16||Vegetation Uptake||gN/m2/year||uptake
|-
| 17||Theta||0-100 percent||theta
|}

== Patch Yearly Growth ==

{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Zone ID|| ||
|-
| 5||Patch ID|| ||
|-
| 6||Litter C||kgC/m2||litter_c
|-
| 7||Soil C||kgC/m2/year||soil_c
|-
| 8||Litter N||kgN/m2/year||litter_n
|-
| 9||Soil N||kgN/m2/year||soil_n
|-
| 10||Soil Nitrate||gN/m2/year||nitrate
|-
| 11||Mineralized N||gN/m2||Sminn
|}

== Stratum Daily ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Stratum ID|| ||
|-
| 9||Leaf Area Index||m2/m2||lai
|-
| 10||Evaporation||mm||evap
|-
| 11||APAR Radiation||KJ/m2||APAR_direct
|-
| 12||APAR Radiation||KJ/m2||APAR_diffuse
|-
| 13||Sublimation||mm||sublim
|-
| 14||Transpiration||mm||trans
|-
| 15||Aerodynamic Conductance||mm/s||ga
|-
| 16||Surface (non-vascular) Conductance||m/s||gsurf
|-
| 17||Canopy Conductance||mm/s||gs
|-
| 18||??||??||?psi?||rhessys5.10.10
|-
| 19||Respiration||kgC/m2||leaf_day_mr
|-
| 20||Net Photosynthesis||gC/m2||psn_to_cpool
|-
| 21||Rain Interception Storage||mm||rain_stored
|-
| 22||Snow Interception Storage||mm||snow_stored
|-
| 23||Rooting Zone Saturation||??||rootzone.S
|}

== Stratum Daily Growth ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Day|| ||
|-
| 2||Month|| ||
|-
| 3||Year|| ||
|-
| 4||Basin ID|| ||
|-
| 5||Hillslope ID|| ||
|-
| 6||Zone ID|| ||
|-
| 7||Patch ID|| ||
|-
| 8||Stratum ID|| ||
|-
| 9||Leaf Area Index||m2/m2||proj_lai
|-
| 10||Leaf C||gN/m2||leafc
|-
| 11||Dead Leaf C||gN/m2||dead_leafc
|-
| 12||Fine Root C||gN/m2||frootc
|-
| 13||Live Stem C||gN/m2||live_stemc
|-
| 14||Leaf C Store||gN/m2||leafc_store
|-
| 15||Dead Stem C||gN/m2||dead_stemc
|-
| 16||Live Coarse Root C||gN/m2||live_crootc
|-
| 17||Dead Coarse Root C||gN/m2||dead_crootc
|-
| 18||Coarse Woody Debris C||gN/m2||cwdc
|-
| 19||Maint Respiration||gC/m2||mresp
|-
| 20||Growth Respiration||gC/m2||gresp
|-
| 21||Net Photosynthesis||gC/m2||psn_to_cpool
|-
| 22||Stand Age||days||age||rhessys5.10.9
|}

== Stratum Monthly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Month|| ||
|-
| 2||Year|| ||
|-
| 3||Basin ID|| ||
|-
| 4||Hillslope ID|| ||
|-
| 5||Zone ID|| ||
|-
| 6||Patch ID|| ||
|-
| 7||Stratum ID|| ||
|-
| 8||Leaf Area Index||m2/m2||lai
|-
| 9||Net Photosynthesis||gC/m2||psn
|-
| 10||Mean Leaf Water Potential||mPa||lwp
|}

== Stratum Yearly ==

{| {{table}}
| align="center" colspan='2' style="background:#f0f0f0;"|'''Column Contents'''
| align="center" style="background:#f0f0f0;"|'''Units'''
| align="center" style="background:#f0f0f0;"|'''RHESSys Output Abbreviation'''
| align="center" style="background:#f0f0f0;"|'''included as of version'''
|-
| 1||Year|| ||
|-
| 2||Basin ID|| ||
|-
| 3||Hillslope ID|| ||
|-
| 4||Zone ID|| ||
|-
| 5||Patch ID|| ||
|-
| 6||Stratum ID|| ||
|-
| 7||Net Photosynthesis||kgC/m2||psn
|-
| 8||Mean Leaf Water Potential||mPa||lwp
|}