Version 1.5 - Revision history

Peder at 14:23, 14 November 2017

2017-11-14T14:23:57Z

← Older revision		Revision as of 15:23, 14 November 2017
Line 1:		Line 1:
	{{Languages}}		{{Languages}}
	[[Category:~~Release~~]]		[[Category:ReleaseNotes archive]]
	[[~~Release date~~::2011-09-01]]		[[newsdate::2011-09-01]]

	==Summary==		==Summary==

Peder: /* Bug fixes */

2011-09-01T13:58:43Z

Bug fixes

← Older revision		Revision as of 14:58, 1 September 2011
Line 15:		Line 15:

	==Bug fixes==		==Bug fixes==
	* In March 2011 an error was ~~accidently~~ introduced that '''prevented second and later thinnings''' to take place. Hence, the problem should exist in version 1.3 and 1.4, but not in versions before that. This has been fixed.		* In March 2011 an error was unfortunately introduced that '''prevented second and later thinnings''' to take place. Hence, the problem should exist in version 1.3 and 1.4, but not in versions before that. This has been fixed.
	* In existing stands (not in stands where regeneration is simulated) with major species other than Scots pine or spruce, for example contorta or oak, the [[Variable:Dominant_Height\|dominant height]] for the site index species has been used as input to the '''thinning guide''' insted of dominant height for the [[Variable:Dominant_Species\|dominant species]]. '''For example, in contorta stands, the dominant height for Scots pine has been used instead of dominant height for contorta.''' Note that the system only handles site index for pine and spruce (site index for birch can be imported but is then converted). This may have lead to that some thinnings in contorta stands have not been simulated, or that the timing of thinnings has been faulty.		* In existing stands (not in stands where regeneration is simulated) with major species other than Scots pine or spruce, for example contorta or oak, the [[Variable:Dominant_Height\|dominant height]] for the site index species has been used as input to the '''thinning guide''' insted of dominant height for the [[Variable:Dominant_Species\|dominant species]]. '''For example, in contorta stands, the dominant height for Scots pine has been used instead of dominant height for contorta.''' Note that the system only handles site index for pine and spruce (site index for birch can be imported but is then converted). This may have lead to that some thinnings in contorta stands have not been simulated, or that the timing of thinnings has been faulty.
	* En error that lead to '''overestimation of tree height''' has been fixed (for tree height development option "ElfvingEriksson". You can expect 1-5 % lower growth rates than in previous versions.		* En error that lead to '''overestimation of tree height''' has been fixed (for tree height development option "ElfvingEriksson". You can expect 1-5 % lower growth rates than in previous versions.

Peder: /* Next release */

2011-09-01T13:58:14Z

Next release

← Older revision		Revision as of 14:58, 1 September 2011
Line 35:		Line 35:
	*Add user-defined thinning guides.		*Add user-defined thinning guides.
	*Add handling of initial dead wood when using stand register data as initial data.		*Add handling of initial dead wood when using stand register data as initial data.
	*Some other things.		*Some other things!

Peder: /* Next release */

2011-09-01T13:58:04Z

Next release

← Older revision		Revision as of 14:58, 1 September 2011
Line 34:		Line 34:
	Probably in October 2011. Planned activities:		Probably in October 2011. Planned activities:
	*Add user-defined thinning guides.		*Add user-defined thinning guides.
	*Add handling of ~~intial~~ dead wood when using stand register data as ~~intial~~ data.		*Add handling of initial dead wood when using stand register data as initial data.
	*Some other things.		*Some other things.

Peder at 13:57, 1 September 2011

2011-09-01T13:57:42Z

← Older revision		Revision as of 14:57, 1 September 2011
Line 8:		Line 8:
	==New features==		==New features==
	* Abundance of large trees are important for biodiversity. You can now define your own [[Result_Variables#User-defined_result_variables \| '''result variables''']] for volume or number of large trees, and select species and diameter criteria for these variables. Read more [[Result_Variables#User-defined_result_variables \| here]]. ''Note! Not to be confused with user-defined input variables when importing stand data!''		* Abundance of large trees are important for biodiversity. You can now define your own [[Result_Variables#User-defined_result_variables \| '''result variables''']] for volume or number of large trees, and select species and diameter criteria for these variables. Read more [[Result_Variables#User-defined_result_variables \| here]]. ''Note! Not to be confused with user-defined input variables when importing stand data!''
	* (PlanWise and StandWise) The thinning criteria for the first thinning has been relaxed, so that it is sufficient that the basal area is ≥ 90 % of that dictated by the thinning guide to consider a thinning (instead of 100 %). This is more in accordance with how the thinning guide should be interpreted in practice (as a basal area interval, not only a midpoint value). This should lead to more thinning alternatives.		* (PlanWise and StandWise) The thinning '''criteria for the first thinning has been relaxed''', so that it is sufficient that the basal area is ≥ 90 % of that dictated by the thinning guide to consider a thinning (instead of 100 %). This is more in accordance with how the thinning guide should be interpreted in practice (as a basal area interval, not only a midpoint value). This should lead to more thinning alternatives.
	* When making a prognosis for a period length less than 5 years, interpolation is applied to each tree object. In previous verioins, linear intepolation was used for tree diameter, stem number and height. In '''an ongoing validation project''', it was discovered that the interpolation ''per se'' causes deviations of up to 2 % on stand volume after 20 years, if starting with an interpolation to 2.5 years (to use period midpoints). A new non-linear interpolation algorithm was therefore implemented that minimizes the interpolation error to neglectable values. The algorithm uses growth, change of stems, etc. for two growth period ahead to estimate the rate of change (i.e. second derivative) for each tree attribute. This information is then used to compute interpolated values.		* When making a prognosis for a period length less than 5 years, '''interpolation''' is applied to each tree object. In previous verioins, linear intepolation was used for tree diameter, stem number and height. In '''an ongoing validation project''', it was discovered that the interpolation ''per se'' causes deviations of up to 2 % on stand volume after 20 years, if starting with an interpolation to 2.5 years (to use period midpoints). A new non-linear interpolation algorithm was therefore implemented that minimizes the interpolation error to neglectable values. The algorithm uses growth, change of stems, etc. for two growth period ahead to estimate the rate of change (i.e. second derivative) for each tree attribute. This information is then used to compute interpolated values.
	* PlanEval now supports participatory planning, so that several stakeholders can "vote". Only preliminary version though.		* PlanEval now supports '''participatory planning''', so that several stakeholders can "vote". Only preliminary version though.
	* In PlanWise, a new fertilization policy is available that allows fertilization every ten years before final felling, starting from established forest stands (i.e. not in young stands).		* In PlanWise, a new fertilization policy is available that allows fertilization every ten years before final felling, starting from established forest stands (i.e. not in young stands).
	* When importing [[Import_of_stand_register \| stand register data]], there are a number of data columns open for you to enter any additional data (called UsedDefinedVariable1 - UserDefinedVariable10). You can now rename the headings of these columns, and these names will be available in table views etc (currently, they are only visible in StandWise).		* When importing [[Import_of_stand_register \| stand register data]], there are a number of data columns open for you to enter any additional data (called UsedDefinedVariable1 - UserDefinedVariable10). You can now rename the headings of these columns, and these names will be available in table views etc (currently, they are only visible in StandWise).

	==Bug fixes==		==Bug fixes==
	* In March 2011 an error was accidently introduced that prevented second and later thinnings to take place. Hence, the problem should exist in version 1.3 and 1.4, but not in versions before that. This has been fixed.		* In March 2011 an error was accidently introduced that '''prevented second and later thinnings''' to take place. Hence, the problem should exist in version 1.3 and 1.4, but not in versions before that. This has been fixed.
	* In existing stands (not in stands where regeneration is simulated) with major species other than Scots pine or spruce, for example contorta or oak, the [[Variable:Dominant_Height\|dominant height]] for the site index species has been used as input to the thinning guide insted of dominant height for the [[Variable:Dominant_Species\|dominant species]]. '''For example, in contorta stands, the dominant height for Scots pine has been used instead of dominant height for contorta.''' Note that the system only handles site index for pine and spruce (site index for birch can be imported but is then converted). This may have lead to that some thinnings in contorta stands have not been simulated, or that the timing of thinnings has been faulty.		* In existing stands (not in stands where regeneration is simulated) with major species other than Scots pine or spruce, for example contorta or oak, the [[Variable:Dominant_Height\|dominant height]] for the site index species has been used as input to the '''thinning guide''' insted of dominant height for the [[Variable:Dominant_Species\|dominant species]]. '''For example, in contorta stands, the dominant height for Scots pine has been used instead of dominant height for contorta.''' Note that the system only handles site index for pine and spruce (site index for birch can be imported but is then converted). This may have lead to that some thinnings in contorta stands have not been simulated, or that the timing of thinnings has been faulty.
	* En error that lead to '''overestimation of tree height''' has been fixed (for tree height development option "ElfvingEriksson". You can expect 1-5 % lower growth rates than in previous versions.		* En error that lead to '''overestimation of tree height''' has been fixed (for tree height development option "ElfvingEriksson". You can expect 1-5 % lower growth rates than in previous versions.
	* Prediction of '''mortality and damages in young stands''' has been modified to be better adapted to tree group list (where a tree object may represent several trees). Also, some bugs have been fixed. Mortality rates are often slightly higher in version 1.5, and amount of non-lethal damages that cause height growth reductions are slightly lower. The effect on total production is probably less than 1 %.		* Prediction of '''mortality and damages in young stands''' has been modified to be better adapted to tree group list (where a tree object may represent several trees). Also, some bugs have been fixed. Mortality rates are often slightly higher in version 1.5, and amount of non-lethal damages that cause height growth reductions are slightly lower. The effect on total production is probably less than 1 %.

Peder: /* New features */

2011-09-01T13:54:57Z

New features

← Older revision		Revision as of 14:54, 1 September 2011
Line 9:		Line 9:
	* Abundance of large trees are important for biodiversity. You can now define your own [[Result_Variables#User-defined_result_variables \| '''result variables''']] for volume or number of large trees, and select species and diameter criteria for these variables. Read more [[Result_Variables#User-defined_result_variables \| here]]. ''Note! Not to be confused with user-defined input variables when importing stand data!''		* Abundance of large trees are important for biodiversity. You can now define your own [[Result_Variables#User-defined_result_variables \| '''result variables''']] for volume or number of large trees, and select species and diameter criteria for these variables. Read more [[Result_Variables#User-defined_result_variables \| here]]. ''Note! Not to be confused with user-defined input variables when importing stand data!''
	* (PlanWise and StandWise) The thinning criteria for the first thinning has been relaxed, so that it is sufficient that the basal area is ≥ 90 % of that dictated by the thinning guide to consider a thinning (instead of 100 %). This is more in accordance with how the thinning guide should be interpreted in practice (as a basal area interval, not only a midpoint value). This should lead to more thinning alternatives.		* (PlanWise and StandWise) The thinning criteria for the first thinning has been relaxed, so that it is sufficient that the basal area is ≥ 90 % of that dictated by the thinning guide to consider a thinning (instead of 100 %). This is more in accordance with how the thinning guide should be interpreted in practice (as a basal area interval, not only a midpoint value). This should lead to more thinning alternatives.
	* When making a prognosis for a period length less than 5 years, ~~'''~~interpolation~~'''~~ is applied to each tree object. In previous verioins, linear intepolation was used for tree diameter, stem number and height. In '''an ongoing validation project''', it was discovered that the interpolation ''per se'' causes deviations of up to 2 % on stand volume after 20 years, if starting with an interpolation to 2.5 years (to use period midpoints). A new non-linear interpolation algorithm was therefore implemented that minimizes the interpolation error to neglectable values. The algorithm uses growth, change of stems, etc. for two growth period ahead to estimate the rate of change (i.e. second derivative) for each tree attribute. This information is then used to compute interpolated values.		* When making a prognosis for a period length less than 5 years, interpolation is applied to each tree object. In previous verioins, linear intepolation was used for tree diameter, stem number and height. In '''an ongoing validation project''', it was discovered that the interpolation ''per se'' causes deviations of up to 2 % on stand volume after 20 years, if starting with an interpolation to 2.5 years (to use period midpoints). A new non-linear interpolation algorithm was therefore implemented that minimizes the interpolation error to neglectable values. The algorithm uses growth, change of stems, etc. for two growth period ahead to estimate the rate of change (i.e. second derivative) for each tree attribute. This information is then used to compute interpolated values.
	* PlanEval now supports participatory planning, so that several stakeholders can "vote". Only preliminary version though.		* PlanEval now supports participatory planning, so that several stakeholders can "vote". Only preliminary version though.
	* In PlanWise, a new fertilization policy is available that allows fertilization every ten years before final felling, starting from established forest stands (i.e. not in young stands).		* In PlanWise, a new fertilization policy is available that allows fertilization every ten years before final felling, starting from established forest stands (i.e. not in young stands).

Peder: /* New features */

2011-09-01T13:52:08Z

New features

← Older revision		Revision as of 14:52, 1 September 2011
Line 8:		Line 8:
	==New features==		==New features==
	* Abundance of large trees are important for biodiversity. You can now define your own [[Result_Variables#User-defined_result_variables \| '''result variables''']] for volume or number of large trees, and select species and diameter criteria for these variables. Read more [[Result_Variables#User-defined_result_variables \| here]]. ''Note! Not to be confused with user-defined input variables when importing stand data!''		* Abundance of large trees are important for biodiversity. You can now define your own [[Result_Variables#User-defined_result_variables \| '''result variables''']] for volume or number of large trees, and select species and diameter criteria for these variables. Read more [[Result_Variables#User-defined_result_variables \| here]]. ''Note! Not to be confused with user-defined input variables when importing stand data!''
	* (PlanWise and StandWise) The thinning criteria for the first thinning has been relaxed, so that a sufficient ~~critera to cponsider a thinning is~~ that the basal area is ~~at least~~ 90 % of that dictated by the thinning guide. This is more in accordance to how the thinning guide should be interpreted in practice (an interval, not only midpoint value). This should lead to more thinning alternatives.		* (PlanWise and StandWise) The thinning criteria for the first thinning has been relaxed, so that it is sufficient that the basal area is ≥ 90 % of that dictated by the thinning guide to consider a thinning (instead of 100 %). This is more in accordance with how the thinning guide should be interpreted in practice (as a basal area interval, not only a midpoint value). This should lead to more thinning alternatives.
	* When making a prognosis for a period length less than 5 years, '''interpolation''' is applied to each tree object. In previous verioins, linear intepolation was used for tree diameter, stem number and height. In '''an ongoing validation project''', it was discovered that the interpolation ''per se'' causes deviations of up to 2 % on stand volume after 20 years, if starting with an interpolation to 2.5 years (to use period midpoints). A new non-linear interpolation algorithm was therefore implemented that minimizes the interpolation error to neglectable values. The algorithm uses growth, change of stems, etc. for two growth period ahead to estimate the rate of change (i.e. second derivative) for each tree attribute. This information is then used to compute interpolated values.		* When making a prognosis for a period length less than 5 years, '''interpolation''' is applied to each tree object. In previous verioins, linear intepolation was used for tree diameter, stem number and height. In '''an ongoing validation project''', it was discovered that the interpolation ''per se'' causes deviations of up to 2 % on stand volume after 20 years, if starting with an interpolation to 2.5 years (to use period midpoints). A new non-linear interpolation algorithm was therefore implemented that minimizes the interpolation error to neglectable values. The algorithm uses growth, change of stems, etc. for two growth period ahead to estimate the rate of change (i.e. second derivative) for each tree attribute. This information is then used to compute interpolated values.
	* PlanEval now supports participatory planning, so that several stakeholders can "vote". Only preliminary version though.		* PlanEval now supports participatory planning, so that several stakeholders can "vote". Only preliminary version though.

Peder: /* New features */

2011-09-01T13:41:44Z

New features

← Older revision		Revision as of 14:41, 1 September 2011
Line 7:		Line 7:

	==New features==		==New features==
	* Abundance of large trees are important for biodiversity. You can now define your own [[Result_Variables#User-defined_result_variables \| '''result variables''']] for volume or number of large trees, and select species and diameter criteria for these variables. Read more [[Result_Variables#User-defined_result_variables \| here]]. Not to be confused with user-defined input variables when importing stand data!		* Abundance of large trees are important for biodiversity. You can now define your own [[Result_Variables#User-defined_result_variables \| '''result variables''']] for volume or number of large trees, and select species and diameter criteria for these variables. Read more [[Result_Variables#User-defined_result_variables \| here]]. ''Note! Not to be confused with user-defined input variables when importing stand data!''
	* (PlanWise and StandWise) The thinning criteria for the first thinning has been relaxed, so that a sufficient critera to cponsider a thinning is that the basal area is at least 90 % of that dictated by the thinning guide. This is more in accordance to how the thinning guide should be interpreted in practice (an interval, not only midpoint value). This should lead to more thinning alternatives.		* (PlanWise and StandWise) The thinning criteria for the first thinning has been relaxed, so that a sufficient critera to cponsider a thinning is that the basal area is at least 90 % of that dictated by the thinning guide. This is more in accordance to how the thinning guide should be interpreted in practice (an interval, not only midpoint value). This should lead to more thinning alternatives.
	* When making a prognosis for a period length less than 5 years, '''interpolation''' is applied to each tree object. In previous verioins, linear intepolation was used for tree diameter, stem number and height. In '''an ongoing validation project''', it was discovered that the interpolation ''per se'' causes deviations of up to 2 % on stand volume after 20 years, if starting with an interpolation to 2.5 years (to use period midpoints). A new non-linear interpolation algorithm was therefore implemented that minimizes the interpolation error to neglectable values. The algorithm uses growth, change of stems, etc. for two growth period ahead to estimate the rate of change (i.e. second derivative) for each tree attribute. This information is then used to compute interpolated values.		* When making a prognosis for a period length less than 5 years, '''interpolation''' is applied to each tree object. In previous verioins, linear intepolation was used for tree diameter, stem number and height. In '''an ongoing validation project''', it was discovered that the interpolation ''per se'' causes deviations of up to 2 % on stand volume after 20 years, if starting with an interpolation to 2.5 years (to use period midpoints). A new non-linear interpolation algorithm was therefore implemented that minimizes the interpolation error to neglectable values. The algorithm uses growth, change of stems, etc. for two growth period ahead to estimate the rate of change (i.e. second derivative) for each tree attribute. This information is then used to compute interpolated values.

Peder: /* New features */

2011-09-01T13:36:27Z

New features

← Older revision		Revision as of 14:36, 1 September 2011
Line 12:		Line 12:
	* PlanEval now supports participatory planning, so that several stakeholders can "vote". Only preliminary version though.		* PlanEval now supports participatory planning, so that several stakeholders can "vote". Only preliminary version though.
	* In PlanWise, a new fertilization policy is available that allows fertilization every ten years before final felling, starting from established forest stands (i.e. not in young stands).		* In PlanWise, a new fertilization policy is available that allows fertilization every ten years before final felling, starting from established forest stands (i.e. not in young stands).
	* When importing [[Import_of_stand_register \| stand register data]], there are a number of data columns open for you to enter any additional data (called UsedDefinedVariable1 - UserDefinedVariable10). You can now rename the headings of these columns, and these names will be available in table views etc.		* When importing [[Import_of_stand_register \| stand register data]], there are a number of data columns open for you to enter any additional data (called UsedDefinedVariable1 - UserDefinedVariable10). You can now rename the headings of these columns, and these names will be available in table views etc (currently, they are only visible in StandWise).

	==Bug fixes==		==Bug fixes==

Peder: /* Bug fixes */

2011-09-01T12:37:49Z

Bug fixes

← Older revision		Revision as of 13:37, 1 September 2011
Line 15:		Line 15:

	==Bug fixes==		==Bug fixes==
	* In March 2011 an error was accidently introduced that prevented second and later thinnings to take place. ~~This mean that~~ the problem should exist in version 1.3 and 1.4, but not in versions before that. This has been fixed.		* In March 2011 an error was accidently introduced that prevented second and later thinnings to take place. Hence, the problem should exist in version 1.3 and 1.4, but not in versions before that. This has been fixed.
	* In existing stands (not in stands where regeneration is simulated) with major species other than Scots pine or spruce, for example contorta or oak, the [[Variable:Dominant_Height\|dominant height]] for the site index species has been used as input to the thinning guide insted of dominant height for the [[Variable:Dominant_Species\|dominant species]]. '''For example, in contorta stands, the dominant height for Scots pine has been used instead of dominant height for contorta.''' Note that the system only handles site index for pine and spruce (site index for birch can be imported but is then converted). This may have lead to that some thinnings in contorta stands have not been simulated, or that the timing of thinnings has been faulty.		* In existing stands (not in stands where regeneration is simulated) with major species other than Scots pine or spruce, for example contorta or oak, the [[Variable:Dominant_Height\|dominant height]] for the site index species has been used as input to the thinning guide insted of dominant height for the [[Variable:Dominant_Species\|dominant species]]. '''For example, in contorta stands, the dominant height for Scots pine has been used instead of dominant height for contorta.''' Note that the system only handles site index for pine and spruce (site index for birch can be imported but is then converted). This may have lead to that some thinnings in contorta stands have not been simulated, or that the timing of thinnings has been faulty.
	* En error that lead to '''overestimation of tree height''' has been fixed (for tree height development option "ElfvingEriksson". You can expect 1-5 % lower growth rates than in previous versions.		* En error that lead to '''overestimation of tree height''' has been fixed (for tree height development option "ElfvingEriksson". You can expect 1-5 % lower growth rates than in previous versions.