Regional Framework Design - Revision history

Fkl: /* Implementation */

2010-05-20T16:21:42Z

Implementation

Fkl: /* Implementation */

2010-05-20T16:20:10Z

Implementation

Fkl: /* Forest Domains */

2010-05-20T16:07:14Z

Forest Domains

Fkl: /* Overview */

2010-05-20T14:31:47Z

Overview

Fkl: /* Forest Domains */

2010-05-20T14:31:08Z

Forest Domains

2010-05-20T14:18:20Z

Created page with '== Overview == The Regional Framework performs the following steps: # Years to start period are calculated # All treatment units are loaded and [[#In�?�'

New page

== Overview ==

The Regional Framework performs the following steps:

# [[#Years to start period|Years to start period]] are calculated
# All treatment units are loaded and [[#Initialization of treatment units|initialized]]
# Treatment units are set aside for [[#Handling of nature conservation|nature conservation]]
# Total area of all treatment units is calculated
# Treatment units are allocated to forest domains
# [[#Initialization of treatment units|Treatment units are initialized]] again
# For each period:
## For each domain:
### Growth to next period is performed
### Restrictions are updated
### Treatments are executed
## Treatment units are allocated to new forest domains
# Results are saved

== Years to start period ==

Number of years to start period is determined by the reference year and the start year given by the user. Start year cannot occur before reference year. If start year and reference year are the same, simulation will be started directly, and the results and settings for the first period will be for the reference year period. If reference year occurs after start year, two extra periods will be added to the simulation, and settings for period 1 and 2 will be used for those periods, while setting for period 3 will be for the reference year period. Similarly two extra periods will be added to the results.

{| border="1"
|-
|Reference Year||Start Year||Period 0||Period 1||Period 2||Period 3
|-
|2006||2010||2006||2008||2010||2015
|-
|2010||2010||2010||2015||2020||2030
|}
== Initialization of treatment units ==

Initialization of treatment units is done twice. The first time the treatment unit is initialized with age, volume, growth, and height for all trees using the settings of the default control category, as these values might be required when assigning treatment units to forest domains.

The second time each treatment unit is assigned to a forest domain. Age, volume, growth, and height is assigned again (since another control category might be used this time), and growth to the start period is performed. Empty treatment units are also regenerated in this step.

== Handling of nature conservation ==

Treatment units are set aside for nature conservation at start of the simulation. Treatment units that has been set aside are included in the normal forest domain handling and treatment handling, but they are never prioritized for treatments.

== Execution of treatments ==

Execution of treatments follow a simple pattern:

* Execution of treatments is done for a domain at a time
* There is a treatment planner for each type of treatment that can be performed
* Each treatment planner evaluates all treatment units in the domain, checks if each treatment unit can be treated by the treatment and sets a priority for it
* Each treatment planner executes treatments for the priorized treatment units until the desired goal for the treatment as set in the domain has been reached

Treatments are executed in the following order:

# Cleaning
# Final felling
# Fertilization
# Regeneration
# Thinning
# Intensive fertilization

Several treatments in the same period is not allowed. This means if several treatments are possible for a treatment unit, the treatment with the highest priority is most likely to be performed.

== Forest Domains ==

@@ Line 103: / Line 103: @@
 ### All treatment units are added to a list of not assigned treatment units
 ## If not first period:
-### Treatment units that are in a forest domain where change of forest domain is allowed, and has the maturity class of the forest domain,
+### Treatment units that are in a forest domain where change of forest domain is allowed, and has the maturity class of the forest domain, are added to a list of not assigned treatment units
-## Remove all treatment units set aside from nature conservation from the list of not assigned treatment units
+## Remove all treatment units set aside from nature conservation from the list of not assigned treatment units, assign these to the default control category of their forest domain
 ## For each forest domain:
 ### For each control category in the domain:

@@ Line 98: / Line 98: @@
 === Implementation ===
-Vid tilldelning av kategori till en åtgärdsenhet sker följande:
+# Total area of the analysis area is calculated
-.	Total area för analysområdet beräknas.
+# For each period:
-.	Alla åtgärdsenheter tilldelas skogstyp
+## If first period:
-.	För varje styrkategori samlar man ihop de åtgärdsenheter som kan ingå i styrkategorin. Detta kan göras i ett Dictionary<ControlCategory, TreatmentUnitCollection>.
+### All treatment units are added to a list of not assigned treatment units
-.	Därefter går man igenom de styrkategorier med procentsats < 100 och lottar ut åtgärdsenheter tills dess målareal är uppfylld eller det inte finns fler åtgärdsenheter. Detta gör man i den ordning kategorierna är definierade, därför får ordningen betydelse.
+## If not first period:
-a.	Varje åtgärdsenhet som lottas in ska tas bort från dictionaries för andra styrkategorier.
+### Treatment units that are in a forest domain where change of forest domain is allowed, and has the maturity class of the forest domain,
-b.	Det torde behövas en till uppsättning dictionaries för inlottade åtgärdsenheter.
+## Remove all treatment units set aside from nature conservation from the list of not assigned treatment units
-.	Sedan går man igenom de styrkategorier med procentsats 100, kvarvarande åtgärdsenheter för dessa ska få den styrkategorin.
+## For each forest domain:
-.	Slutligen utför man simulering med simulation manager som hör till kategorin.
+### For each control category in the domain:
+#### While the assigned area of the control category is less than the target area of the control category, and there are available treatment units:
-För varje skogstyp definerar man när det är tillåtet med byte av skogstyp. Behovet verkar vara vid en viss höjd på skogen, inte efter en viss åtgärd. Förslaget är därför att implementera en funktion som beräknar huggningsklass (efter åtgärd) och låta användaren ange huggningsklass när byte ska ske. Default ska vara None, dvs aldrig byte.
+##### Pick a treatment unit with matching forest domain from the list of not assigned treatment units
+##### Add the treatment unit to the control category
-I RegVis kan byte av skogstyp hanteras så här:
+##### Increase the assigned area of the control category
+## For each treatment units that not yet has been assigned:
-.	I steg 2 tilldelas skogstyp till de åtgärdsenheter som har en skogstyp där byte kan ske och där rätt huggningsklass är tilldelad.
+### Add it to the default control category of its forest domain

← Older revision		Revision as of 16:07, 20 May 2010
Line 61:		Line 61:
	== Forest Domains ==		== Forest Domains ==

		+	=== How it should work ===
		+	A <tt>ForestDomain</tt> is a classification of treatment units. Each forest domain has two properties that are of interest for the regional framework:
		+
		+	;ChangeForestDomainAllowed:Can treatment units assigned to the domain be moved to other domains
		+	;ChangeMaturityClass:At which maturity class can the change be done
		+
		+	A <tt>ControlCategory</tt> specifies how treatments are applied, e.g. a kind of management system. Each control category has the following property of interest here:
		+
		+	;TargetArea: Percentage of the total area being analyzed that should be allocated to the control category
		+
		+	Each <tt>ForestDomain</tt> is connected to one or more <tt>ControlCategories</tt>. The same <tt>ControlCategory</tt> may be connected to more than one domain.
		+
		+	In the regional framework, it is evaluated for each period which treatment units belongs to which control category.
		+
		+	For example:
		+
		+	Say that there are three control categories:
		+
		+	* Intensive management (10%)
		+	* Continous management (20%)
		+	* Even Aged Management (100%)
		+
		+	And three forest domains, assigned to categories:
		+
		+	;Oak Forest: Continous Management , Even Aged Management
		+	;Spruce Forest: Intensive Management, Even Aged Management
		+	;Other Forest: Intensive Management, Continous Management, Even Aged Management
		+
		+	The regional framework will do as follows:
		+
		+	# If possible, allocated oak forest to continous management
		+	# If the area of the oak forest is more than 10%, use even aged management for oak forest
		+	# Similarly try to assign spruce forest to intensive management
		+	# For other forest, use intensive management if possible (there was not enough spruce forest), if not try with continous management, if that not works even aged management will have to do
		+
		+	=== Implementation ===

	Vid tilldelning av kategori till en åtgärdsenhet sker följande:		Vid tilldelning av kategori till en åtgärdsenhet sker följande:

← Older revision		Revision as of 14:31, 20 May 2010
Line 60:		Line 60:

	== Forest Domains ==		== Forest Domains ==
		+
		+
		+	Vid tilldelning av kategori till en åtgärdsenhet sker följande:
		+	1. Total area för analysområdet beräknas.
		+	2. Alla åtgärdsenheter tilldelas skogstyp
		+	3. För varje styrkategori samlar man ihop de åtgärdsenheter som kan ingå i styrkategorin. Detta kan göras i ett Dictionary<ControlCategory, TreatmentUnitCollection>.
		+	4. Därefter går man igenom de styrkategorier med procentsats < 100 och lottar ut åtgärdsenheter tills dess målareal är uppfylld eller det inte finns fler åtgärdsenheter. Detta gör man i den ordning kategorierna är definierade, därför får ordningen betydelse.
		+	a. Varje åtgärdsenhet som lottas in ska tas bort från dictionaries för andra styrkategorier.
		+	b. Det torde behövas en till uppsättning dictionaries för inlottade åtgärdsenheter.
		+	5. Sedan går man igenom de styrkategorier med procentsats 100, kvarvarande åtgärdsenheter för dessa ska få den styrkategorin.
		+	6. Slutligen utför man simulering med simulation manager som hör till kategorin.
		+
		+	För varje skogstyp definerar man när det är tillåtet med byte av skogstyp. Behovet verkar vara vid en viss höjd på skogen, inte efter en viss åtgärd. Förslaget är därför att implementera en funktion som beräknar huggningsklass (efter åtgärd) och låta användaren ange huggningsklass när byte ska ske. Default ska vara None, dvs aldrig byte.
		+
		+	I RegVis kan byte av skogstyp hanteras så här:
		+
		+	2. I steg 2 tilldelas skogstyp till de åtgärdsenheter som har en skogstyp där byte kan ske och där rätt huggningsklass är tilldelad.
		+	3. Steg 3 -5 gäller bara de åtgärdsenheter som bytt skogstyp.
		+	4. I steg 4 kan man också hantera målareal i olika tidsperioder. Om målarealen minskar ska åtgärdsenheter tas bort från kategorin, då de åtgärdsenheter som tagits bort kunna få ny kategori i steg 4 och 5.

@@ Line 7: / Line 7: @@
 # Treatment units are set aside for [[#Handling of nature conservation|nature conservation]]
 # Total area of all treatment units is calculated
-# Treatment units are allocated to forest domains
+# Treatment units are allocated to forest domains and then to control categories
 # [[#Initialization of treatment units|Treatment units are initialized]] again
 # For each period:
-## For each domain:
+## For each control category:
 ### Growth to next period is performed
 ### Restrictions are updated