Version 1.6 - Revision history

Rickardw: Replaced salix FTP links with heurekaslu equivalents.

2019-12-11T14:56:48Z

Replaced salix FTP links with heurekaslu equivalents.

Peder at 14:25, 14 November 2017

2017-11-14T14:25:01Z

Peder at 08:35, 9 September 2013

2013-09-09T08:35:40Z

Peder at 08:04, 15 November 2011

2011-11-15T08:04:27Z

Peder: /* Bug fixes */

2011-11-11T16:14:57Z

Bug fixes

Peder: /* Next release */

2011-11-11T15:19:13Z

Next release

Peder at 15:18, 11 November 2011

2011-11-11T15:18:50Z

Peder at 15:02, 11 November 2011

2011-11-11T15:02:20Z

Peder: /* Bug fixes */

2011-11-11T14:43:18Z

Bug fixes

Peder at 14:40, 11 November 2011

2011-11-11T14:40:38Z

@@ Line 66: / Line 66: @@
 *When using period midpoints in PlanWise strategic TPG, period 0 now refers to year 0, not year 2.5. Instead, the period midpoint for period 1 is year 2.5, and so forth. Hence, period 0 is not an actual period, but a point in time, followed by a series of 5-year periods. The problem have been that treatments applied in year 0, for example regeneration in recently clear cut stands, were not reported when using period midpoint, but now they are. Note that '''no regular harvesting''' will take place in period 0, only removal of existing seed trees and shelterwoods. This will probably affect existing optimization models, if you have restrictions that include harvesting in period 0. Add condition "with p > 0" when declaring such constraints, for example
 :<code><nowiki>forall <p> in periods with p > 0 do </nowiki></code>
-*A set of report templates (in Swedish!) can be downloaded from ftp://salix.slu.se/download/Heureka/Rapportmallar/. See the readme-file there for instructions were to put the templates. One useful template is called Översikt (Overview), check it out!
+*A set of report templates (in Swedish!) can be downloaded from https://www.heurekaslu.se/filerepository/Rapportmallar/. See the readme-file there for instructions were to put the templates. One useful template is called Översikt (Overview), check it out!

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

@@ Line 22: / Line 22: @@
 *When editing conditions in a forest domain, expressions can now hold variables with modifiers as expression types. This means that a condition can include a relation between two variables (instead of one variable and a constant value), for example MeanAge >= 1.1*MinFinalFellingAge.
-*RegWise has a new method for calculating forest development to a user-defined start year. The pre-growth-is independent of the settings in the actual scenarios to run. This makes it possible to use exactly the same starting condition for different scenarios when the start year is not the same as the inventory year.
+*RegWise has a new method for calculating forest development to a user-defined start year. The "pre-growth-step" is independent of the settings in the actual scenarios to run. This makes it possible to use exactly the same starting condition for different scenarios when the start year is not the same as the inventory year.
 *Two new thinning guides are available (see control table Treatment Model > Thinning Guide):
@@ Line 47: / Line 47: @@
 ==Performance improvements==
-*The treatment program generator in PlanWise is faster on multi-core processor PCs (which most PC:s are today). This has been achieved through parallelization of the program so that the s capacity is better utilized.
+*The treatment program generator in PlanWise is faster on multi-core processor PCs (which most PC:s are today). This has been achieved through parallellization of the program so that the computer's capacity is better utilized.
 *The evaluation of forest domains when running Tactical Treatment Program Generator has been very time consuming, but this has been fixed.
@@ Line 57: / Line 57: @@
 *For ingrown trees, the function for uneven-aged stands is now used to compute tree age, independent of whether the stand is classified as even-aged or uneven-aged. As a consequence of this fix, ingrown trees get smaller ages, which in turn gives a larger growth than before. In an example that we ran for a spruce stand with H100 = 33 m and a mean age of 68 years, a certain ingrown tree is now 29 years, compared to 59 years before the change.
-* When adding a new user defined integer to an optimization model, an error occured in the index for existing parameters due to a naming conflict. This has been corrected, so that a unique index is generated.
+* When adding a new "user defined integer set" to an optimization model, an error occured in the index for existing parameters due to a naming conflict. This has been corrected, so that a unique index is generated.
 * In the Timber Pricelist editor (control table Pricelist, section Prices > Timber), there is a setting "Pulpwood proportion" for  how many of the butt logs, middle logs, and top logs, respectively, that are downgraded to pulp. Probably, few users have changed these settings which are 10 % by default. However, changing these values have not lead not to expected results, because the value for top log and but log had been switched. This has been fixed. Also, the focus is always on the first tab (Pine) when opening the editor.
@@ Line 64: / Line 64: @@
 ==Other stuff you should know==
-*When using period midpoints in PlanWise strategic TPG, period 0 now refers to year 0, not year 2.5. Instead, the period midpoint for period 1 is year 2.5, and so forth. Hence, period 0 is not an actual period, but a point in time, followed by a series of 5-year periods. The problem have been that treatments applied in year 0, for example regeneration in recently clear cut stands, were not reported when using period midpoint, but now they are. Note that '''no regular harvesting''' will take place in period 0, only removal of existing seed trees and shelterwoods. This will probably affect existing optimization models, if you have restrictions that include harvesting in period 0. Add condition with p > when declaring such constraints, for example
+*When using period midpoints in PlanWise strategic TPG, period 0 now refers to year 0, not year 2.5. Instead, the period midpoint for period 1 is year 2.5, and so forth. Hence, period 0 is not an actual period, but a point in time, followed by a series of 5-year periods. The problem have been that treatments applied in year 0, for example regeneration in recently clear cut stands, were not reported when using period midpoint, but now they are. Note that '''no regular harvesting''' will take place in period 0, only removal of existing seed trees and shelterwoods. This will probably affect existing optimization models, if you have restrictions that include harvesting in period 0. Add condition "with p > 0" when declaring such constraints, for example
-:<code><nowiki>forall <p> in periods with p > 0 </nowiki></code>
+:<code><nowiki>forall <p> in periods with p > 0 do </nowiki></code>
-*A set of report templates (in Swedish!) can be downloaded from ftp://salix.slu.se/download/Heureka/Rapportmallar/. See the readme-file there for instructions were to put the templates. One useful template is called (Overview), check it out!
+*A set of report templates (in Swedish!) can be downloaded from ftp://salix.slu.se/download/Heureka/Rapportmallar/. See the readme-file there for instructions were to put the templates. One useful template is called Översikt (Overview), check it out!

@@ Line 15: / Line 15: @@
 *Dead wood is reported separately for coniferous and deciduous trees.
-<br>'''Important''': When using period midpoints in PlanWise, period 0 now refers to year 0, and period 1 to year 2.5, which can affect your optimization models, see below.
+<br>'''Important''': When using period midpoints in PlanWise, period 0 now refers to a point in time (year 0). Period 1 refers to activities bewteen year 0 to 5, with midpoint 2.5. This can affect your optimization models, see below.
 ==New features ==
@@ Line 64: / Line 64: @@
 ==Other stuff you should know==
-*When using period midpoints in PlanWise strategic TPG, period 0 now refers to year 0, not year 2.5. Instead, period 1 refers to year 2.5, and so forth. Hence, period 0 is 2.5 years long, followed by a series of 5-year period
+*When using period midpoints in PlanWise strategic TPG, period 0 now refers to year 0, not year 2.5. Instead, the period midpoint for period 1 is year 2.5, and so forth. Hence, period 0 is not an actual period, but a point in time, followed by a series of 5-year periods

← Older revision		Revision as of 16:14, 11 November 2011
Line 55:		Line 55:

	*When calculating initial tree age a function is used to determine if a tree should be considered an overstorey tree. If so, a specific age function is used. For different reasons, this functionality had been removed, but is now re-implemented.		*When calculating initial tree age a function is used to determine if a tree should be considered an overstorey tree. If so, a specific age function is used. For different reasons, this functionality had been removed, but is now re-implemented.
−	*For ingrown trees, the function for uneven-aged stands is now used to compute tree age, independent of whether the stand is classified as even-aged or uneven-aged. As a consequence of this fix, ingrown trees get smaller ages, which in turn gives a larger growth than before. In an example that we ran for a spruce stand with H100 = 33 m and a mean age of 68 years, ~~an cetain~~ ingrown tree is now 29 years, compared to 59 years before the change.	+	*For ingrown trees, the function for uneven-aged stands is now used to compute tree age, independent of whether the stand is classified as even-aged or uneven-aged. As a consequence of this fix, ingrown trees get smaller ages, which in turn gives a larger growth than before. In an example that we ran for a spruce stand with H100 = 33 m and a mean age of 68 years, a certain ingrown tree is now 29 years, compared to 59 years before the change.

@@ Line 71: / Line 71: @@
 ==Next release==
 *Date is not decided...
-*A new stand register version (2) will be released (actually PlanStart supports it but we have not documented it yet). The new version has columns for initial dead wood volume. The previuous version (1) will still be supported.
+*A new stand register version (2) will be released (actually PlanStart supports it but we have not documented it yet). The new version has columns for initial dead wood volume. The previous version (1) will still be supported.

← Older revision		Revision as of 15:02, 11 November 2011
Line 66:		Line 66:

	==Other stuff you should know==		==Other stuff you should know==
−	""	+
		+	:<code><nowiki></nowiki></code>

← Older revision		Revision as of 14:43, 11 November 2011
Line 57:		Line 57:

	*When calculating initial tree age a function is used to determine if a tree should be considered an overstorey tree. If so, a specific age function is used. For different reasons, this functionality had been removed, but is now re-implemented.		*When calculating initial tree age a function is used to determine if a tree should be considered an overstorey tree. If so, a specific age function is used. For different reasons, this functionality had been removed, but is now re-implemented.
−	*For ingrown trees, the function for uneven-aged stands is now used to compute tree age, independent of whether the stand is classified as even-aged or uneven-aged. As a consequence of this fix, ingrown trees ~~gets~~ smaller ages, which in turn gives a larger growth than before. In an example that we ran for a spruce stand with H100 = 33 m and a mean age of 68 years, an cetain ingrown tree is now 29 years, compared to 59 years before the change.	+	*For ingrown trees, the function for uneven-aged stands is now used to compute tree age, independent of whether the stand is classified as even-aged or uneven-aged. As a consequence of this fix, ingrown trees get smaller ages, which in turn gives a larger growth than before. In an example that we ran for a spruce stand with H100 = 33 m and a mean age of 68 years, an cetain ingrown tree is now 29 years, compared to 59 years before the change.