Temporal Event Control files - Revision history

Dgroulx: /* TEC Event Options */

2009-11-29T21:42:46Z

TEC Event Options

Dgroulx at 21:09, 24 November 2009

2009-11-24T21:09:41Z

Dgroulx: /* Tec File Instructions and Format */

2009-11-24T19:09:31Z

Tec File Instructions and Format

Dgroulx: /* Tec File Instructions and Format */

2009-11-24T19:09:18Z

Tec File Instructions and Format

Dgroulx: /* Tec File Instructions and Format */

2009-11-24T19:08:59Z

Tec File Instructions and Format

Dgroulx: /* Important Notes */

2009-11-24T19:04:55Z

Important Notes

Dgroulx at 18:18, 24 November 2009

2009-11-24T18:18:48Z

Dgroulx: /* Tec File Instructions and Format */

2009-11-24T18:18:25Z

Tec File Instructions and Format

Dgroulx: /* TEC Event Options */

2009-11-24T18:18:07Z

TEC Event Options

Dgroulx at 18:17, 24 November 2009

2009-11-24T18:17:00Z

@@ Line 31: / Line 31: @@
 | align="center" style="background:#f0f0f0;"|'''Description'''
 |-
-| print_daily_on||Begin daily printing for regular or custom output*
+| print_daily_on||Begin daily printing for regular or custom output
 |-
 | print_daily_off||End daily printing for regular or custom output
@@ Line 69: / Line 69: @@
 | output_current_state||Outputs current state in worldfile format
 |}
 ==Important Notes==

@@ Line 8: / Line 8: @@
 Example:
-<code>
+<pre>
-1 1 1 print_daily_on<br>
+1 1 1 print_daily_on
-4 2 1 output_current_state<br>
+4 2 1 output_current_state
-4 3 1 redefine_strata<br>
+4 3 1 redefine_strata
-12 30 1 print_daily_off<br>
+12 30 1 print_daily_off
-</code>
+</pre>
 Save the TEC file.

@@ Line 7: / Line 7: @@
 Example:
 <code>
 1 1 1 print_daily_on<br>

@@ Line 8: / Line 8: @@
 Example:
 <code>
-1 1 1 print_daily_on
+1 1 1 print_daily_on<br>
-4 2 1 output_current_state
+4 2 1 output_current_state<br>
-4 3 1 redefine_strata
+4 3 1 redefine_strata<br>
-12 30 1 print_daily_off
+12 30 1 print_daily_off<br>
 </code>

@@ Line 7: / Line 7: @@
 Example:
-1 1 1 print_daily_on1982 4 2 1 output_current_state1982 4 3 1 redefine_strata1984 12 30 1 print_daily_off
+<code>
 Save the TEC file.
 ==TEC File Description==

@@ Line 67: / Line 67: @@
 ==Important Notes==
-The tec_file should not contain any blank lines. This will interfere with the parsing of the file and a run-time error may occur. Please make sure there are no blank lines, especially those at the end of the file.
+* The ''tec_file'' should not contain any blank lines. This will interfere with the parsing of the file and a run-time error may occur. Please make sure there are no blank lines, especially those at the end of the file.
-print_?_on and print_?_off control the flow of output in RHESSys. They will cause RHESSys to print data to the output files for specific levels in the hierarchy as chosen on the command line. These print options also control the temporal level of output data aggregation. That is, print_yearly_on will start the printing of yearly accumulated data.
+* ''print_?_on'' and ''print_?_off'' control the flow of output in RHESSys. They will cause RHESSys to print data to the output files for specific levels in the hierarchy as chosen on the command line. These print options also control the temporal level of output data aggregation. That is, print_yearly_on will start the printing of yearly accumulated data.
-roads_on switches on routing of subsurface throughflow and overland flow via the road network. Prior to roads_on, roads are ignored in flow routing. Flow routing uses a flow_table to determine the pattern of flow across the landscape. Roads can potentially alter this pattern. When a road_on command is given; RHESSys reads in a new flow_table with a specific name. The name of the new "roads_on" flow_table must be the flow_table name that was specified on the command line appended by the date of the road event using the following format:
+* ''roads_on'' switches on routing of subsurface throughflow and overland flow via the road network. Prior to ''roads_on'', roads are ignored in flow routing. Flow routing uses a flow_table to determine the pattern of flow across the landscape. Roads can potentially alter this pattern. When a road_on command is given; RHESSys reads in a new flow_table with a specific name. The name of the new "roads_on" flow_table must be the flow_table name that was specified on the command line appended by the date of the road event using the following format:
 flow_table_name.YyearMmthDdayHhour
@@ Line 76: / Line 76: @@
 flow_table.dat.Y1998M1D16H1
 The algorithms used for routing associated with a road network is described in Part II. roads_off switches the routing back to the initial flow_table.
-redefine_world and redefine_strata implements a user-controlled change to the landscape. This does not change the spatial containment hierarchy, it merely redefines strata types and the state of the world. That is, a land-use change such as logging is implemented in this way. redefine_strata and redefine_world assumes input of a stratum or worldstate definition file. For redefining the stratum, this file must be named by the worldfile name appended with str. Both files can also be generated using GRASS2WORLD.
+* ''redefine_world'' and ''redefine_strata'' implements a user-controlled change to the landscape. This does not change the spatial containment hierarchy, it merely redefines strata types and the state of the world. That is, a land-use change such as logging is implemented in this way. redefine_strata and redefine_world assumes input of a stratum or worldstate definition file. For redefining the stratum, this file must be named by the worldfile name appended with str. Both files can also be generated using GRASS2WORLD.
-output_current_state outputs the current state of the simulation in a worldfile format and reflects the state of the world at the particular point in time. The resulting worldfile may then be used as input to another RHESSys simulation. When outputting the current state, RHESSys will call the new worldfile the same name as the worldfile specified in the simulation with a date extension of the date specified in the TEC file to output the current state, i.e. "hjaworld.Y1980M10D1H
+* ''output_current_state'' outputs the current state of the simulation in a worldfile format and reflects the state of the world at the particular point in time. The resulting worldfile may then be used as input to another RHESSys simulation. When outputting the current state, RHESSys will call the new worldfile the same name as the worldfile specified in the simulation with a date extension of the date specified in the TEC file to output the current state, i.e. "hjaworld.Y1980M10D1H

@@ Line 21: / Line 21: @@
 ==TEC Event Options==
+{| {{table}}
-Table 6. Temporal Event Control File
+| align="center" style="background:#f0f0f0;"|'''TEC Event'''
-TEC Event	Description
+| align="center" style="background:#f0f0f0;"|'''Description'''
-print_daily_on	Begin daily printing for regular or custom output*
+|-
-print_daily_off	End daily printing for regular or custom output
+| print_daily_on||Begin daily printing for regular or custom output*
-print_daily_growth_on	Begin daily growth printing for regular output only
+|-
-print_daily_growth_off	End daily growth printing for regular output only
+| print_daily_off||End daily printing for regular or custom output
-print_yearly_on	Begin yearly printing for custom output only
+|-
-print_yearly_off	End yearly printing for custom output only
+| print_daily_growth_on||Begin daily growth printing for regular output only
-print_monthly_on	Begin monthly printing for custom output only
+|-
-print_monthly_off	End monthly printing for custom output only
+| print_daily_growth_off||End daily growth printing for regular output only
-print_hourly_on	Begin hourly printing for regular or custom output
+|-
-print_hourly_off	End hourly printing for regular or custom output
+| print_yearly_on||Begin yearly printing for custom output only
-print_daily_csv_on	Begin daily printing in comma delimited format for regular output only
+|-
-print_daily_csv_off	End daily printing in comma delimited format for regular only
+| print_yearly_off||End yearly printing for custom output only
-print_daily_csv_growth_on	Begin daily growth printing in comma delimited format for regular output only
+|-
-print_daily_csv_growth_off	End daily growth printing in comma delimited for regular output only
+| print_monthly_on||Begin monthly printing for custom output only
-roads_on	Begin road construction
+|-
-roads_off	End road construction
+| print_monthly_off||End monthly printing for custom output only
-redefine_world	Redefinition of the world
+|-
-redefine_strata	Redefinition of strata (e.g. needed logging event)
+| print_hourly_on||Begin hourly printing for regular or custom output
-output_current_state	Outputs current state in worldfile format
+|-
+| print_hourly_off||End hourly printing for regular or custom output
 ==Important Notes==

@@ Line 1: / Line 1: @@
-[[Tec File Instructions and Format]]
+==Tec File Instructions and Format==
 The TEC file is created in a text editor such as Notepad (NT) or VI (UNIX).
 Events in the TEC file must be listed in order of execution.
@@ Line 11: / Line 11: @@
 Back to Top
-[[TEC File Description ]]
+==TEC File Description==
 RHESSys is structured as an event driven simulation, where most of the process modeling occurs between events. RHESSys execution is based on a temporal event control or TEC file which must be specified in the command line. These events are used specify printing hourly, daily, monthly, yearly and state output options, redefinition of strata and road construction. The TEC file, as its name may imply, is not used to specify the modelling of certain processes as events.
@@ Line 20: / Line 20: @@
-[[TEC Event Options]]
+==TEC Event Options==
 Table 6. Temporal Event Control File
@@ Line 45: / Line 45: @@
-[[Important Notes]]
+==Important Notes==
 The tec_file should not contain any blank lines. This will interfere with the parsing of the file and a run-time error may occur. Please make sure there are no blank lines, especially those at the end of the file.