Difference between revisions of "User's guide to RegWise"

From Heureka Wiki
Jump to navigation Jump to search
Line 16: Line 16:
  
 
== Running simulations/scenarios ==
 
== Running simulations/scenarios ==
RegWise is based on forest scenario analyses, in contrary to the optimizations in PlanWise. A scenario is hence a consequence of the pre-defined forestry and all other influencing factors (e.g. any future climate changes). The users will here, instead of analyzing an optimized plan, analyse and compare several different scenarios following from different assumptions about future forestry. The control categories used in PlanWise is here not enough - more controlling parameters needs to be defined.
+
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.  
  
Explain the main parts of "Regional framework"...
+
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.  
  
[[Control Categories, Control Tables, and Forest Domains]]
+
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.
  
 
== Analyzing Results ==
 
== Analyzing Results ==

Revision as of 10:01, 29 March 2011

Introduction

RegWise (sv: RegVis) is a tool for large-scale forestry scenario analysis. Because users have different assumptions about forest management and use, the application can evaluate a variety of forestry-related issues. What to analyse is decided by the user and may include many utilities: supply of timber, forest fuel ("bio-energy"), development of biodiversity, and amount of carbon sequestration in forest.

The basic analyse done with RegWise is non-spatial. In such an analysis you would normally choose to use National Forest Inventory (NFI) survey plots as input data. A spatial analysis requires whole-coverage data, which is obtained by combining NFI plots with remote sensing data. One method to combine data is called kNN, and Heureka will offer the possibility to import kNN-Sweden data ([1]). A GIS-tool for working with landscape samples in the form of 1x1 km contiguous squares have been developed.

Results can be presented in tables and maps that describe the state and development of the forest ecosystem as well as outcomes of cuttings and other utilities.

The application addresses the needs of information desired by different kind of users, for example the Swedish Forest Agency, the Swedish Environmental Agency, large forest companies, and branch organizations and actors interested in forest policy issues. Because many uses are included in the analyses, other organizations - such as municipalities, county administrations, and NGO:s - will benefit from the analyses.

Working with Projects

Introduction to Projects

Create a new Project

Open an existing Project

Making a copy of a Project

Delete a Project

Running simulations/scenarios

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.

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 About Control Categories, Control Tables, and Forest Domains. The Control Table ControlTable Scenario Settings is specific for RegWise, and holds the settings for priority functions and global constraints mentioned above.

Analyzing Results

Results can be presented in maps, tables, and graphs, both on stand-level and forest-level aggregates: Results

How Do I?

Create a New Result Database

Improve Performance

Organize Windows

Reference

Control Tables

Common Dialogs

Error Messages