Version 1.0.6 - Revision history

Peder at 14:17, 14 November 2017

2017-11-14T14:17:34Z

Peder: /* New features */

2010-06-21T15:55:21Z

New features

Peder: /* Known issues */

2010-06-21T15:47:16Z

Known issues

Peder: /* Known issues */

2010-06-21T15:46:30Z

Known issues

Peder: /* Known issues */

2010-06-21T15:46:10Z

Known issues

Peder: /* Bug fixes and improvements */

2010-06-21T15:45:19Z

Bug fixes and improvements

Peder: /* New features */

2010-06-21T15:43:56Z

New features

Peder: /* New features */

2010-06-21T15:42:50Z

New features

Peder: /* New features */

2010-06-21T15:42:08Z

New features

Peder: /* New features */

2010-06-21T15:40:45Z

New features

@@ Line 1: / Line 1: @@
 {{Languages}}
-[[Category:Release]]
+[[Category:ReleaseNotes archive]]
 [[Release date::2010-06-21]]
@@ Line 7: / Line 7: @@
 ====New features====
 *The [[Report Builder]] (PlanWise and RegWise) has been modified so that you can put more than one condition when computing sums and average values.
-*When creating a report template in previous versions of the [[Report Builder]], you had to choose between the functions ???and ???, and between ???and ???. This has been simplified so that you can always add conditions to ???and ???, making ???and ???obsolete. Old templates should still work.
+*When creating a report template in previous versions of the [[Report Builder]], you had to choose between the functions �??Sum�?� and �??ConditionalSum�?�, and between �??Average�?� and �??ConditionalAverage�?�. This has been simplified so that you can always add conditions to �??Sum�?� and �??Average�?�, making �??ConditionalSum�?� and �??ConditionalAverage�?� obsolete. Old templates should still work.
 *Reports of sums or average values over stands can now be weighted. For example, making a report of mean harvest diameter is preferably weighted with stand volume harvested, see example ([[Report_Builder#Mean_diameter_of_harvested_trees|here]].
-*The optimization language syntax now supports brackets in conditions, allowing for more complex expressions. For example, ??with (A and (B or C))?.
+*The optimization language syntax now supports brackets in conditions, allowing for more complex expressions. For example, �??with (A and (B or C))�?�.
 *Support for a third optimization problem solver called SCIP/Soplex has been added. This solver is more efficient than LP_Solve, especially for solving MIP problems (but less efficient than CPLEX). The solver itself is not distributed but must be obtained by the user. It is free for academic use. For non-academic use a commercial license is required. See [[Optimization#Solvers | Optimization solvers]] for further details.
-*StandWise has a tool for automatically generating a treatmemt schedule, but this function has until now only been working for even-aged mangement (tool button ??Last Period with ?) and no management (button "Last Period"). Now you can also choose "Continuos Cover Forestry" (selection harvesting) as management system. The two buttons "Last Period..." has been merged into one button, ??Last Period with ?("Väx till sista perioden med åtgärder"). When you select this tool, a dialog is displayed in which you select what management system to simulate.
+*StandWise has a tool for automatically generating a treatmemt schedule, but this function has until now only been working for even-aged mangement (tool button �??Last Period with Treatments�?�) and no management (button "Last Period"). Now you can also choose "Continuos Cover Forestry" (selection harvesting) as management system. The two buttons "Last Period..." has been merged into one button, �??Last Period with Treatments�?� ("Väx till sista perioden med åtgärder"). When you select this tool, a dialog is displayed in which you select what management system to simulate.
 *Additional rules for unconditional final felling and thinning have been implemented in RegWise.
 *In PlanWise, when the management system is set to "Continuous cover forestry", several alternatives can be generated for a stand by varying the timing of harvest periods.
@@ Line 20: / Line 20: @@
 ====Bug fixes and improvements====
 *The calculation of dominant height has been modified. This may lead to that you obtain different thinning regimes in this version.
-*An error had been corrected in the computation of "Lowest final felling age" (Lägsta slutavverkningsålder, ?). This error lead to that ? was too high in some cases.
+*An error had been corrected in the computation of "Lowest final felling age" (Lägsta slutavverkningsålder, LS�?). This error lead to that LS�? was too high in some cases.
 *The [[Importera beståndsregister|import utility for stand registers]] has been modified and is less error-prone (but not fool-proof!) thanks to some new functions:
 **Species proportion are always normalized so it does not matter whether the user has entered percentage or fractions.

@@ Line 16: / Line 16: @@
 *In the window "TPG Results" in PlanWise, you can scrutinize results from the treatment program generator before proceeding with the optimization model. The window design has been modified. First, you can no longer open several windows simultanously. This was a flexible but messy function. The one remaing window is split in two halves: the upper half contains an overview of treatment programs, the lower half shows details of the row (i.e. the managment program alternative) currently selected.
 *'''NOTE:''' Two new result variables are available: SiteIndexH (SIH), and DominantHeight (övre höjd). However, '''these are only intended for the research group working with the modelling of an improved stand establishment model. '''
 ====Bug fixes and improvements====

@@ Line 29: / Line 29: @@
 ==Known issues==
-*Mean age will be underestimated for young stand plantations with a mean height less than 1 m. The system will consider these stands as bare land and regenerate them, despite they may already be established. The problem occurs when you have entered data with the [[Import of stand register/sv|Import Stand Register]] utility, and but not entered regeneration method and year for young stands. The problem is solved if you enter a plantation year and method for all stands that are have a mean height less than 1 m.
+*Mean age will be underestimated for young stand plantations with a mean height less than 1 m. The system will consider these stands as bare land and regenerate them, despite they may already be established. The problem occurs when you have entered data with the [[Import of stand register/sv|Import Stand Register]] utility, and not entered regeneration method and year for the young stands. The problem is solved if you enter a plantation year and method for all stands that are have a mean height less than 1 m.
 *In RegWise, there is no harvesting in the first period.

@@ Line 29: / Line 29: @@
 ==Known issues==
-*Stand age will be underestimated for young stand plantations with a mean height less than 1 m. The system will consider these stands as bare land and regenerate them, despite they may already be established. The problem occurs when you have entered data with the [[Import of stand register/sv|Import Stand Register]] utility, and but not entered regeneration method and year for young stands. The problem is solved if you enter a plantation year and method for all stands that are have a mean height less than 1 m.
+*Mean age will be underestimated for young stand plantations with a mean height less than 1 m. The system will consider these stands as bare land and regenerate them, despite they may already be established. The problem occurs when you have entered data with the [[Import of stand register/sv|Import Stand Register]] utility, and but not entered regeneration method and year for young stands. The problem is solved if you enter a plantation year and method for all stands that are have a mean height less than 1 m.
 *In RegWise, there is no harvesting in the first period.

@@ Line 29: / Line 29: @@
 ==Known issues==
-*Stand age will be underestimated for young stand plantations with a mean height less than 1 m. In this case, the system will consider these stands as bare land and regenerate them, despite they may already be established. The problem occurs when you have entered data with the [[Import of stand register/sv|Import Stand Register]] utility, and but not entered regeneration method and year for young stands. The problem is solved if you enter a plantation year and method for all stands that are have a mean height less than 1 m.
+*Stand age will be underestimated for young stand plantations with a mean height less than 1 m. The system will consider these stands as bare land and regenerate them, despite they may already be established. The problem occurs when you have entered data with the [[Import of stand register/sv|Import Stand Register]] utility, and but not entered regeneration method and year for young stands. The problem is solved if you enter a plantation year and method for all stands that are have a mean height less than 1 m.
 *In RegWise, there is no harvesting in the first period.

@@ Line 22: / Line 22: @@
 *The [[Importera beståndsregister|import utility for stand registers]] has been modified and is less error-prone (but not fool-proof!) thanks to some new functions:
 **Species proportion are always normalized so it does not matter whether the user has entered percentage or fractions.
-**Species-wise stem densities are calibered to match total stem densities.
+**Species-wise stem densities are calibrated to match total stem densities.
 **Latitude is not required if coordinates are supplied.
 **StandID is now a text string allowing longer StandID. MapID and SubStandID are no longer in use.

@@ Line 8: / Line 8: @@
 *The [[Report Builder]] (PlanWise and RegWise) has been modified so that you can put more than one condition when computing sums and average values.
-*Report variables can now be weighted. For example, making a report of mean harvest diameter is preferably weighted to volume harvested. (lank)
+*Reports of sums or average values over stands can now be weighted. For example, making a report of mean harvest diameter is preferably weighted with stand volume harvested, see example ([[Report_Builder#Mean_diameter_of_harvested_trees|here]].
 *Support for a third optimization problem solver called SCIP/Soplex is added. This solver is more efficient than LP_Solve, especially for solving MIP problems (but less efficient than CPLEX).  The solver itself is not distributed but must be obtained by the user. It is free for academic use. For non-academic use a commercial license is required. See [[Optimization#Solvers | Optimization solvers]] for further details.