Generating RHESSys input files - Revision history

Jchoate: /* Flowtables */

2012-02-13T04:08:01Z

Flowtables

Jchoate: /* Flowtables */

2012-02-13T04:07:18Z

Flowtables

Dgroulx: /* Tecfiles */

2010-08-03T17:30:31Z

Tecfiles

Dgroulx: /* Tecfiles */

2010-08-03T17:29:43Z

Tecfiles

Dgroulx: /* Tecfiles */

2010-08-03T17:08:10Z

Tecfiles

Dgroulx: /* Tecfiles */

2010-08-03T17:07:41Z

Tecfiles

Dgroulx: /* Flowtables */

2010-06-17T18:21:11Z

Flowtables

Dgroulx: /* Flowtables */

2010-06-17T18:20:36Z

Flowtables

Dgroulx: /* Flowtables */

2009-11-24T18:01:42Z

Flowtables

Dgroulx: /* Flowtables */

2009-10-30T00:06:33Z

Flowtables

@@ Line 130: / Line 130: @@
 To create the flowtable, at the GRASS prompt type the command:
-'''grass> cf9 output=<output filename> template=<worldfile template name>  stream=<> road=<> dem=<> slope=<> cellsize=<>
+'''grass> cf9 output=<output_filename> template=<worldfile_template_name>  stream=<> road=<> dem=<> slope=<> cellsize=<>
 '''

@@ Line 130: / Line 130: @@
 To create the flowtable, at the GRASS prompt type the command:
-'''grass> cf9 output=<output filename> template=<worldfile template name>  stream=<> road=<> dem=<> slope=<>
+'''grass> cf9 output=<output filename> template=<worldfile template name>  stream=<> road=<> dem=<> slope=<> cellsize=<>
 '''

@@ Line 153: / Line 153: @@
 # 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:
+# 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

@@ Line 150: / Line 150: @@
 Tecfile formatting:
-. The TEC file is created in a text editor (such as VI)
+# The TEC file is created in a text editor (such as VI)
-. Events must be listed in order of execution
+# Events must be listed in order of execution
-. Only one event per line is allowed, no blank lines are allowed
+# Only one event per line is allowed, no blank lines are allowed
-. The format for events in the TEC file is as follows:
+# 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

@@ Line 145: / Line 145: @@
 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]]
+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.

@@ Line 134: / Line 134: @@
 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
+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.

@@ Line 121: / Line 121: @@
 ==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 (cf7) 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.  cf7 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.
+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.
-cf7 uses GRASS raster images to create the flowtable.
+cf9 uses GRASS raster images to create the flowtable.
@@ Line 130: / Line 130: @@
 To create the flowtable, at the GRASS prompt type the command:
-'''grass> cf7 output=<output filename> template=<worldfile template name> m=<> K=<> stream=<> road=<> dem=<> slope=<>
+'''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. cf7 has several additional options,
+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 cf7 will pull the name of the basin, hillslope, patch, and zone rasters from
+but these are the required ones. Note that cf9 will pull the name of the basin, hillslope, patch, and zone rasters from
-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 cf7.  By convention, flowtables should start with the prefix flow followed by a name representing the study area, ie. flow.w8.
+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.

@@ Line 140: / Line 140: @@
 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 pathc, 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.
+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==