User's guide to RegWise - Revision history

Jonare at 10:17, 14 November 2024

2024-11-14T10:17:21Z

Hah: /* Running simulations/scenarios */

2012-11-09T07:59:04Z

Running simulations/scenarios

Peder: /* Analyzing Results */

2011-03-29T17:09:22Z

Analyzing Results

Peder: /* Analyzing Results */

2011-03-29T17:09:12Z

Analyzing Results

Peder: /* Running simulations/scenarios */

2011-03-29T09:32:13Z

Running simulations/scenarios

Peder: /* Running simulations/scenarios */

2011-03-29T09:31:44Z

Running simulations/scenarios

Peder: /* Running simulations/scenarios */

2011-03-29T09:21:06Z

Running simulations/scenarios

Peder: /* Running simulations/scenarios */

2011-03-29T09:20:39Z

Running simulations/scenarios

Peder: /* Running simulations/scenarios */

2011-03-29T08:02:35Z

Running simulations/scenarios

Peder: /* Running simulations/scenarios */

2011-03-29T08:01:47Z

Running simulations/scenarios

@@ Line 1: / Line 1: @@
 [[Category:User's Guides|RegVis|RegVis]]
 == Introduction ==
 {{:About_RegWise}}

@@ Line 18: / Line 18: @@
 RegWise is based on forest scenario analyses, in contrast to the optimization-based analysis used in PlanWise. A scenario is a result of the assumptions made and the models selected for projecting the development of the forest and the outputs over an extended time horizon.
-In RegWise, a set of rules is used to allocate activities (silvicultural treatments and harvesting) to treatment units. A treatment unit is RegWise could be an NFI sample plot. Rules for allocating treatments are currently (2011) the same as in the Hugin system, the predecessor to RegWise. These rules are represented as priority functions, with which treatment priorities are calculated for each treatment unit. Treatments are then allocated according to the priorities calculated, subject to global constraints such as maximum harvest volume or maximum area fertilized during a period. OF course, not all treatments are applicable to all treatment Additional rules define what treatments are allowed. For example, final felling can only be carried out if the stand age for a certain treatment unit has reached the minimum final felling age, and pre-commercial thinning is only carried out in young stands with a stem density succeeding a certain threshold value.
+In RegWise, a set of rules is used to allocate activities (silvicultural treatments and harvesting) to treatment units. A treatment unit in RegWise could be an NFI sample plot. Rules for allocating treatments are currently (2011) the same as in the Hugin system, the predecessor to RegWise. These rules are represented as priority functions, with which treatment priorities are calculated for each treatment unit. Treatments are then allocated according to the priorities calculated, subject to global constraints such as maximum harvest volume or maximum area fertilized during a period. Of course, not all treatments are applicable to all treatment units. Additional rules define what treatments are allowed. For example, final felling can only be carried out if the stand age for a certain treatment unit has reached the minimum final felling age, and pre-commercial thinning is only carried out in young stands with a stem density succeeding a certain threshold value.
 The total harvest volume can be set either manually or determined automatically. In the latter case, harvesting in a period is essentially calculated as a function of current growth, growth trend (whether growth is increasing or decreasing over two periods). A more detailed explanation of how it works is given here: [[RegWise Priority Functions]].
@@ Line 25: / Line 25: @@
 Basic steps for running a simulation:
 # Select an area. If you use NFI-data, you should use a five-year series since each survey takes five years.
-# Defined forest domains and control categories.
+# Define forest domains and control categories.
-# Link one or more control categories to each forest domain. Assign the area proportion for each control category so that a forest domain is 100% allocated.
+# Link control categories to each forest domain. Assign the area proportion for each control category so that a forest domain is completely allocated (100%).
-# Select Run from the Action-menu.
+# Select "Simulate..." from the Action-menu.
-## '''Reference year''' reflects the inventory year, or in case you are using NFI-data for several inventory years, the "average" year that corresponds to the period middle of the input data. For example, if you have selected inventory data from 2005 to 2009 (five years), then the reference year will be set to 2007.
+## '''Reference year''' reflects the inventory year, or in case you are using NFI-data for several inventory years, the "average" year that corresponds to the middle of the period of the input data. For example, if you have selected inventory data from 2005 to 2009 (five years), then the reference year will be set to 2007.
-## '''Start year''' is year of the first time period (middle) of the scenario. If, for example, this is set 2011, and the reference year is 2007, then all data will be projected for four years (2011 minus 2007) before the actual scenario begins. During these four years, harvesting is simulated according to manual settings in control table [[ControlTable_Regional_Framework#Harvest_levels | Regional Framework]]. Since the growth period length is five years, the forest state and outputs (harvest volumes etc.) is distributed over a five-year period in a logical way. In this example, the period middle of the forest is year 2011, and it will be represented by the state of the forest in 2009, 2010, 2011, 2012, and 2013 (projected from 2005, 2006, 2007, 2008, and 2009 respectively).
+## '''Start year''' is year of the first time period (middle) of the scenario. If, for example, this is set to 2011, and the reference year is 2007, then all data will be projected for four years (2011 minus 2007) before the actual scenario begins. During these four years, harvesting is simulated according to manual settings in control table [[ControlTable_Regional_Framework#Harvest_levels | Regional Framework]]. Since the growth period length is five years, the forest state and outputs (harvest volumes etc.) is distributed over a five-year period in a logical way. In this example, the period middle of the forest is year 2011, and it will be represented by the state of the forest in 2009, 2010, 2011, 2012, and 2013 (projected from 2005, 2006, 2007, 2008, and 2009 respectively).
 == Analyzing Results ==

@@ Line 33: / Line 33: @@
 == Analyzing Results ==
 Results can be presented in maps, tables, and graphs, both on stand-level and forest-level aggregates, see
-[[:Category:Results | Results]]
+[[:Category:Results | Results]].
 == How Do I? ==

@@ Line 32: / Line 32: @@
 == Analyzing Results ==
-Results can be presented in maps, tables, and graphs, both on stand-level and forest-level aggregates:
+Results can be presented in maps, tables, and graphs, both on stand-level and forest-level aggregates, see
 [[:Category:Results | Results]]

@@ Line 29: / Line 29: @@
 # Select Run from the Action-menu.
 ## '''Reference year''' reflects the inventory year, or in case you are using NFI-data for several inventory years, the "average" year that corresponds to the period middle of the input data. For example, if you have selected inventory data from 2005 to 2009 (five years), then the reference year will be set to 2007.
-## '''Start year''' is year of the first time period (middle) of the scenario. If, for example, this is set 2011, and the reference year is 2007, then all data will be projected for four years (2011 minus 2007) before the actual scenario begins. During these four years, harvesting is simulated according to manual settings in control table [[ControlTable_Regional_Framework#Harvest_levels | Regional Framework]]. Since the growth period length is five years, the forest state and outputs (harvest volume etc.) is distributed over a five-year period in a logical way. In this example, the period middle of the forest is year 2011, and it will be represented by the state of the forest in 2009, 2010, 2011, 2012, and 2013 (projected from 2005, 2006, 2007, 2008, and 2009 respectively).
+## '''Start year''' is year of the first time period (middle) of the scenario. If, for example, this is set 2011, and the reference year is 2007, then all data will be projected for four years (2011 minus 2007) before the actual scenario begins. During these four years, harvesting is simulated according to manual settings in control table [[ControlTable_Regional_Framework#Harvest_levels | Regional Framework]]. Since the growth period length is five years, the forest state and outputs (harvest volumes etc.) is distributed over a five-year period in a logical way. In this example, the period middle of the forest is year 2011, and it will be represented by the state of the forest in 2009, 2010, 2011, 2012, and 2013 (projected from 2005, 2006, 2007, 2008, and 2009 respectively).
 == Analyzing Results ==

@@ Line 21: / Line 21: @@
 The total harvest volume can be set either manually or determined automatically. In the latter case, harvesting in a period is essentially calculated as a function of current growth, growth trend (whether growth is increasing or decreasing over two periods). A more detailed explanation of how it works is given here: [[RegWise Priority Functions]].
-In RegWise and in PlanWise, treatment units are grouped into so called Forest Domains, based on used-defined criteria (conditions), see [[Control Categories, Control Tables, and Forest Domains]]. The Control Table [[ControlTable_Regional_Framework]] is specific for RegWise, and holds the settings for priority functions and global constraints mentioned above.
+In RegWise and in PlanWise, treatment units are grouped into so called Forest Domains, based on used-defined criteria (conditions), see [[Control Categories, Control Tables, and Forest Domains]]. The Control Table [[ControlTable Regional Framework]] is specific for RegWise, and holds the settings for priority functions and global constraints mentioned above.
 == Analyzing Results ==