Version 1.2 - Revision history

Peder at 14:21, 14 November 2017

2017-11-14T14:21:15Z

Peder: /* Details */

2011-02-17T15:36:56Z

Details

Peder: /* Details */

2011-02-17T15:32:56Z

Details

Peder at 14:55, 17 February 2011

2011-02-17T14:55:23Z

Peder at 14:54, 17 February 2011

2011-02-17T14:54:37Z

Peder: /* Details */

2011-02-17T14:51:32Z

Details

Peder: /* Details */

2011-02-17T14:48:21Z

Details

Peder: /* Summary */

2011-02-17T14:45:43Z

Summary

Peder: /* Summary */

2011-02-17T14:45:01Z

Summary

Peder: /* Summary */

2011-02-17T14:44:48Z

Summary

@@ Line 1: / Line 1: @@
 {{Languages}}
-[[Category:Release]]
+[[Category:ReleaseNotes archive]]
-[[Release date::2011-02-16]]
+[[newsdate::2011-02-16]]
 ==Summary==

@@ Line 17: / Line 17: @@
 ==Details==
 {| style="text-align:top-left;" valign = "top"
-| align="left" width = "5%" style="background:#f0f0f0;"|'''Version'''
+| align="left" style="background:#f0f0f0;width:5%;"|'''Version'''
-| align="left" width = "5%"  style="background:#f0f0f0;"|'''Type'''
+| align="left" style="background:#f0f0f0;width:10%;;"|'''Type'''
-| align="left" width = "60%"  style="background:#f0f0f0;"|'''Description'''
+| align="left" style="background:#f0f0f0;width:50%;;"|'''Description'''
-| align="left" width = "20%"  style="background:#f0f0f0;"|'''Application'''
+| align="left" style="background:#f0f0f0;width:35%;;"|'''Application'''
 |- valign="top"
 | 1.2.0||Bugfix||Problem:  For some users en error occured when building an optimization model in PlanWise, "ZIMPL... cannot be found...". Solution: Fixed by including absolute file path to ZIMPL binary file.||All

@@ Line 24: / Line 24: @@
 | 1.2.0||Bugfix||Problem:  For some users en error occured when building an optimization model in PlanWise, "ZIMPL... cannot be found...". Solution: Fixed by including absolute file path to ZIMPL binary file.||All
 |- valign="top"
-| 1.2.0||Bugfix||Problem: Stands imported from stand register data or from FMPP (Indelningspaketet) with mean height < 0.5 m obtained no initial state. Solution: Problem was that regeneration year had not been set in stand register file. Added support to handle such missing data, so that if regeneration year is missing, but there are plants/stems and age > 0, then regenration year is set to inventory year - stand age + 2 (+2 for assumed plant age when planting) ||PlanStart
+| 1.2.0||Bugfix||Problem: Stands imported from stand register data or from FMPP (Indelningspaketet) with mean height < 0.5 m obtained no initial state. Solution: Problem was that regeneration year had not been set in stand register file. Added support to handle such missing data, so that if regeneration year is missing, but there are plants or stems and age is larger than 0, then regenration year is set to inventory year - stand age + 2 (+2 for assumed plant age when planting) ||PlanStart
 |- valign="top"
-| 1.2.0||Bugfix||Problem: DominantSpecies in young stands varied from period to period. Solution: In young stands (\"sapling plots\") is determined by stem density instead of basal area. Of determined by basal area, a spruce plantation will often be classified as a deciduous stand because of fast growth of birch. This will lead to erronuous final felling age for the spruce stand.||All
+| 1.2.0||Bugfix||Problem: DominantSpecies in young stands varied from period to period. Solution: In young stands ("sapling plots") is determined by stem density instead of basal area. Of determined by basal area, a spruce plantation will often be classified as a deciduous stand because of fast growth of birch. This will lead to erronuous final felling age for the spruce stand.||All
 |- valign="top"
 | 1.2.0||Bugfix||Problem: Planted beech was not growing, or growing extremely slowly. Solution: Problem was that wrong type av height function was applied for beech, which is now corrected.||All

@@ Line 17: / Line 17: @@
 ==Details==
 {| style="text-align:top-left;" valign = "top"
-| align="left" width = "10%" style="background:#f0f0f0;"|'''Version'''
+| align="left" width = "5%" style="background:#f0f0f0;"|'''Version'''
-| align="left" width = "10%"  style="background:#f0f0f0;"|'''Type'''
+| align="left" width = "5%"  style="background:#f0f0f0;"|'''Type'''
 | align="left" width = "60%"  style="background:#f0f0f0;"|'''Description'''
 | align="left" width = "20%"  style="background:#f0f0f0;"|'''Application'''

@@ Line 17: / Line 17: @@
 ==Details==
 {| style="text-align:top-left;" valign = "top"
-| align="left" width = "10" style="background:#f0f0f0;"|'''Version'''
+| align="left" width = "10%" style="background:#f0f0f0;"|'''Version'''
-| align="left" width = "10"  style="background:#f0f0f0;"|'''Type'''
+| align="left" width = "10%"  style="background:#f0f0f0;"|'''Type'''
-| align="left" width = "60"  style="background:#f0f0f0;"|'''Description'''
+| align="left" width = "60%"  style="background:#f0f0f0;"|'''Description'''
-| align="left" width = "20"  style="background:#f0f0f0;"|'''Application'''
+| align="left" width = "20%"  style="background:#f0f0f0;"|'''Application'''
 |- valign="top"
 | 1.2.0||Bugfix||Problem:  For some users en error occured when building an optimization model in PlanWise, "ZIMPL... cannot be found...". Solution: Fixed by including absolute file path to ZIMPL binary file.||All

@@ Line 22: / Line 22: @@
 | align="left" width = "20"  style="background:#f0f0f0;"|'''Application'''
 |- valign="top"
-| 1.2.0||Bugfix||Problem:  For some users en error occurs when build optimization model in PlanWise, "ZIMPL... cannot be found...". Solution: Fixed by including absolute file path to ZIMPL binary file.||All
+| 1.2.0||Bugfix||Problem:  For some users en error occured when building an optimization model in PlanWise, "ZIMPL... cannot be found...". Solution: Fixed by including absolute file path to ZIMPL binary file.||All
 |- valign="top"
-| 1.2.0||Bugfix||Problem: Stands imported from stand register data or from FMPP (Indelningspaketet) with mean height < 0.5 m obtains no initial state. Solution: Problem was that regeneration year had not been set in stand register file. Added support to handle such missing data, so that if regeneration year is missing, but there are plants/stems and age > 0, then regenration year is set to inventory year - stand age + 2 (+2 for assumed plant age when planting) ||PlanStart
+| 1.2.0||Bugfix||Problem: Stands imported from stand register data or from FMPP (Indelningspaketet) with mean height < 0.5 m obtained no initial state. Solution: Problem was that regeneration year had not been set in stand register file. Added support to handle such missing data, so that if regeneration year is missing, but there are plants/stems and age > 0, then regenration year is set to inventory year - stand age + 2 (+2 for assumed plant age when planting) ||PlanStart
 |- valign="top"
-| 1.2.0||Bugfix||Problem: DominantSpecies in young stands varies from period to period. Solution: In young stands (\"sapling plots\") is determined by stem density instead of basal area. Of determined by basal area, a spruce plantation will often be classified as a deciduous stand because of fast growth of birch. This will lead to erronuous final felling age for the spruce stand.||All
+| 1.2.0||Bugfix||Problem: DominantSpecies in young stands varied from period to period. Solution: In young stands (\"sapling plots\") is determined by stem density instead of basal area. Of determined by basal area, a spruce plantation will often be classified as a deciduous stand because of fast growth of birch. This will lead to erronuous final felling age for the spruce stand.||All
 |- valign="top"
-| 1.2.0||Bugfix||Problem: Planted beech is not growing. Solution: Problem was that wrong type av height function was applied for beech, which is now corrected.||All
+| 1.2.0||Bugfix||Problem: Planted beech was not growing, or growing extremely slowly. Solution: Problem was that wrong type av height function was applied for beech, which is now corrected.||All
 |- valign="top"
-| 1.2.0||Bugfix||Problem: Values for overstorey trees are not updated after treatment. Fixed.||Common
+| 1.2.0||Bugfix||Problem: Values for overstorey trees were not updated after treatment. Fixed.||Common
 |- valign="top"
 | 1.2.0||Bugfix||Conditions with typed variables (such as Species Code, Soil Moisture Code etc.) in Forest Domain Builder did not work when selecting multiple values. This has been fixed.||All
@@ Line 40: / Line 40: @@
 | 1.2.0||Bugfix||Problem: Sometimes an error "Object reference not set to an instance of an object." occurred when changing project, which has been fixed.||PlanWise
 |- valign="top"
-| 1.2.0||Bugfix||Problem: "OutOfMemoryException" when running Treatment Program Generator (TPG) in PlanWise for large datasets. Solution: There is still a limitation for how large datasets can be run, but some code optimization has been done to prevent this problem to occur as far as possible. We have succesfully run more than 20000 treatment units.\'||PlanWise, RegWise
+| 1.2.0||Bugfix||Problem: "OutOfMemoryException" when running Treatment Program Generator (TPG) in PlanWise for large datasets. Solution: There is still a limitation for how large datasets can be run, but several code optimizations has been done to minimize the problem and to increase speed when updating forest domains etc. In tests we have succesfully run more than 20000 treatment units.||PlanWise, RegWise
 |- valign="top"
 | 1.2.0||Bugfix||Initial soil carbon storage was erroneous due to a unit error and should be 10 times larger. Also, funtion for spruce was mistakenly used for pine when calculating carbon in  debris from tree logs. These errors have been fixed||All
@@ Line 48: / Line 48: @@
 | 1.2.0||Bugfix||The mortality model for trees in young stands has been faulty, so that mortality was too high. This has been fixed. ||
 |- valign="top"
-| 1.2.0||Bugfix||Problem: Calculation of net present values in StandWise fails due to null referencing ("Object reference not set to an instance of an object"). Solution: Fixed.||StandWise
+| 1.2.0||Bugfix||Problem: Calculation of net present values in StandWise failed due to null referencing ("Object reference not set to an instance of an object"). Solution: Fixed.||StandWise
 |- valign="top"
 | 1.2.0||Bugfix||Problem: Error when using function "Last periods with treatments" in StandWise. Solution: This problem occured after version 1.1 but has now been fixed.||StandWise
 |- valign="top"
-| 1.2.0||Bugfix||Problem: When editing conditions with coded variables (such as Species or Vegetation Type), and multiple values have been selected, an error occurs. The problem occured when running projects created in versions before 1.1, but has now been fixed. ||PlanWise
+| 1.2.0||Bugfix||Problem: When editing conditions with coded variables (such as Species or Vegetation Type), and multiple values have been selected, an error occured. The problem occured when running projects created in versions before 1.1, but has now been fixed. ||PlanWise
 |- valign="top"
 | 1.2.0||Improvement||Year (relative from start year 0), is displayed in tables and graphs (x-axis).||PlanWise, RegWise

@@ Line 12: / Line 12: @@
 Improvements:
-*You can name variables in reports (aliases).
+*You can give report variables names (aliases).
 *For those who use CPLEX for solving optimization problem in PlanWise, possible causes to infeasibility are reported in case a problem is infeasible.

@@ Line 9: / Line 9: @@
 *The calculation of natural mortality in young stands was faulty and gave larger mortality than the underlying model depicts.
 *The amount of initial soil carbon was ten times too small, and wrong function was used for pine.
-*Young stands with an initial height less than 5 dm was not regenerated in case no regeneration year had been supplied in the imported data.
+*Plantations with an average height < 5 dm was treated as bare land if no data on regeneration year had been supplied by the user.
 Improvements: