Version 1.0.8 - Revision history

Peder at 14:19, 14 November 2017

2017-11-14T14:19:57Z

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

	==New features==		==New features==
Line 9:		Line 9:
	==Bug fixes and improvements==		==Bug fixes and improvements==
	====PlanWise and RegWise====		====PlanWise and RegWise====
	*The handling of treatment categories within a forest domain has been made more intuitive. A new dialog is opened when you right-click on a forest domain and select ??Edit control category ?.		*The handling of treatment categories within a forest domain has been made more intuitive. A new dialog is opened when you right-click on a forest domain and select �??Edit control category connections�?�.
	**In PlanWise, there are checkboxes for ???and ???.		**In PlanWise, there are checkboxes for �??Gen1�?� and �??Gen2�?�.
	**In RegWise, area percentages for each treatment category can be entered.		**In RegWise, area percentages for each treatment category can be entered.
	*In RegWise, the simulation rules for calculating total harvesting in each period for thinning, selection harvesting and final felling has been developed and is almost complete.		*In RegWise, the simulation rules for calculating total harvesting in each period for thinning, selection harvesting and final felling has been developed and is almost complete.
Line 20:		Line 20:

	====PlanWise,RegWise, and StandWise====		====PlanWise,RegWise, and StandWise====
	*A result variable for timber harvested (total and per species) has been added. It replaces ??timber volume top ?, ??timber volume middle ?, and ??timber volume butt ?. NOTE! If you have graphs and diagrams with the old variables, you must edit the report template. You must also edit optimization models that use timber volumes as parameters.		*A result variable for timber harvested (total and per species) has been added. It replaces �??timber volume top log�?�, �??timber volume middle log�?�, and �??timber volume butt log�?�. NOTE! If you have graphs and diagrams with the old variables, you must edit the report template. You must also edit optimization models that use timber volumes as parameters.

	====StandWise====		====StandWise====
Line 26:		Line 26:

	====PlanStart====		====PlanStart====
	*When linking stand register data to existing Heureka data, all subnodes within the selected areanode are searched. This means that you do not have to enter values for ???and ???in the stand register (csv) if you just want to link the stand register data to existing Heureka data. Note that the standid should always be unique within the area.		*When linking stand register data to existing Heureka data, all subnodes within the selected areanode are searched. This means that you do not have to enter values for �??AreaLevel2�?� and �??AreaLevel3�?� in the stand register (csv) if you just want to link the stand register data to existing Heureka data. Note that the standid should always be unique within the area.
	*The import of stand register data has been made more effective, importing 20000 stands takes about 20 sec instead of several minutes.		*The import of stand register data has been made more effective, importing 20000 stands takes about 20 sec instead of several minutes.
	*An error in sample tree height calibration when importing FMPP data (Indelningspaket) has been fixed.		*An error in sample tree height calibration when importing FMPP data (Indelningspaket) has been fixed.
	*A couple of errors when importing incomplete stand register data has been fixed. If the data is not needed for simulating tree lists, then the only field required is ???.		*A couple of errors when importing incomplete stand register data has been fixed. If the data is not needed for simulating tree lists, then the only field required is �??standid�?�.

	==Tests==		==Tests==

Peder: /* Tests */

2010-11-23T14:00:24Z

Tests

← Older revision		Revision as of 15:00, 23 November 2010
Line 32:		Line 32:

	==Tests==		==Tests==
	*~~Comparisons~~ have been made between PlanWise and FMPP (Indelningspaketet). The investigation is not completed but prelimnary results show that differences are rather small, when using the same growth models.		*A comparison have been made between growth calculations under no management in PlanWise and FMPP (Indelningspaketet). The investigation is not completed but prelimnary results show that differences are rather small, when using the same growth models.

	==Next release==		==Next release==

Peder at 12:49, 23 November 2010

2010-11-23T12:49:40Z

← Older revision		Revision as of 13:49, 23 November 2010
Line 12:		Line 12:
	**In PlanWise, there are checkboxes for �??Gen1�?� and �??Gen2�?�.		**In PlanWise, there are checkboxes for �??Gen1�?� and �??Gen2�?�.
	**In RegWise, area percentages for each treatment category can be entered.		**In RegWise, area percentages for each treatment category can be entered.
	*In RegWise, the simulation rules for calculating total harvesting in each period for thinning, selection harvesting and final felling has been developed and is almost complete.		*In RegWise, the simulation rules for calculating total harvesting in each period for thinning, selection harvesting and final felling has been developed and is almost complete.
			**Treatments can now also be simulated in the first period.
			**Harvest levels are met.
			**Selection harvesting can be simulated.
	*In the PlanWise optimization tool, formula parameters with tuple indexes had an error in the index definition. The fix enables defining an indexed parameter as a function of another indexed parameter.		*In the PlanWise optimization tool, formula parameters with tuple indexes had an error in the index definition. The fix enables defining an indexed parameter as a function of another indexed parameter.
	*An error in the computation of conditional and weighted averages in reports has been fixed. For example, average diameter in thinnings was faulty.		*An error in the computation of conditional and weighted averages in reports has been fixed. For example, average diameter in thinnings was faulty.

Peder: Created page with '{{Languages}} Category:Release Release date::2010-11-23 ==New features== In RegWise, management system can be selected explictly in the same way as in PlanWise. In Pla�?�'

2010-11-23T12:20:03Z

Created page with '{{Languages}} Category:Release Release date::2010-11-23 ==New features== *In RegWise, management system can be selected explictly in the same way as in PlanWise. *In Pla�?�'

New page

{{Languages}}
[[Category:Release]]
[[Release date::2010-11-23]]

==New features==
*In RegWise, management system can be selected explictly in the same way as in PlanWise.
*In PlanWise and RegWise, it is possible to deactive forest domains so that all treatment units that belong to a certain domain are excluded from simulation.
*Pricelists can be named and described, thanks two new settings for a pricelist: Comment and Name.
==Bug fixes and improvements==
====PlanWise and RegWise====
*The handling of treatment categories within a forest domain has been made more intuitive. A new dialog is opened when you right-click on a forest domain and select �??Edit control category connections�?�.
**In PlanWise, there are checkboxes for �??Gen1�?� and �??Gen2�?�.
**In RegWise, area percentages for each treatment category can be entered.
*In RegWise, the simulation rules for calculating total harvesting in each period for thinning, selection harvesting and final felling has been developed and is almost complete.
*In the PlanWise optimization tool, formula parameters with tuple indexes had an error in the index definition. The fix enables defining an indexed parameter as a function of another indexed parameter.
*An error in the computation of conditional and weighted averages in reports has been fixed. For example, average diameter in thinnings was faulty.

====PlanWise,RegWise, and StandWise====
*A result variable for timber harvested (total and per species) has been added. It replaces �??timber volume top log�?�, �??timber volume middle log�?�, and �??timber volume butt log�?�. NOTE! If you have graphs and diagrams with the old variables, you must edit the report template. You must also edit optimization models that use timber volumes as parameters.

====StandWise====
*An error has been fixed in the net present value calculator, which lead to that the discount rate entered was not updated correctly when calculating soil expectation values.

====PlanStart====
*When linking stand register data to existing Heureka data, all subnodes within the selected areanode are searched. This means that you do not have to enter values for �??AreaLevel2�?� and �??AreaLevel3�?� in the stand register (csv) if you just want to link the stand register data to existing Heureka data. Note that the standid should always be unique within the area.
*The import of stand register data has been made more effective, importing 20000 stands takes about 20 sec instead of several minutes.
*An error in sample tree height calibration when importing FMPP data (Indelningspaket) has been fixed.
*A couple of errors when importing incomplete stand register data has been fixed. If the data is not needed for simulating tree lists, then the only field required is �??standid�?�.

==Tests==
*Comparisons have been made between PlanWise and FMPP (Indelningspaketet). The investigation is not completed but prelimnary results show that differences are rather small, when using the same growth models.

==Next release==
The next release is planned December 20, 2010.

==Known issues==
[[Known issues]]

Version 1.0.8 - Revision history

Peder at 14:19, 14 November 2017

Peder: /* Tests */

Peder at 12:49, 23 November 2010

Peder: Created page with '{{Languages}} Category:Release Release date::2010-11-23 ==New features== *In RegWise, management system can be selected explictly in the same way as in PlanWise. *In Pla�?�'

Peder: Created page with '{{Languages}} Category:Release Release date::2010-11-23 ==New features== In RegWise, management system can be selected explictly in the same way as in PlanWise. In Pla�?�'