Version 2.14

Version 2.14

Summary

• A new feature allows you to project an imported data set to a new start date.
• "Conditional control tables" is also a new feature. It can help you keep the number of control categories and forest domains down to a minimum by letting the choice of specific control tables be determined by for example geographic location.
• New result variable summarizes total dead wood

Project imported data set to new start date (Beta)

Heureka now has a function (Beta version) for projecting the state of an imported data set, from the inventory date specified for each stand, to a desired start date for a new analysis. The program then creates a new area and the old data is not affected. In the projection, the program asks if you want to include treatments that have been carried out since the inventory. See the help documentation for more information: English Swedish

Conditional control tables - direct linking of control tables to stands

"Conditional control tables" is a way to link specific control tables to stands, and takes precedence over the links created via forest domains and control categories. The feature is particularly useful if you have many different geographical regions in an analysis area, for example price regions, and can help keep the number of forest domains and control categories down to a minimum. See the help documentation for more information: English Swedish

New result variable for total dead wood volume

To get total dead wood volume, you must sum volumes over decay classes manually, which prevents making graphs and tables that shows the total volume of dead wood. Therefore, a new result variable called "Volume Deadwood All Decay Classes to Include" has been added. You can select what decay classes that should be included in this variable in the Dead Wood control table. For example, you may prefer to exclude the classes with almost completely decayed wood. All decay classes are included by default.

PlanWise: Let non-fertilization alternatives be generated automatically

The main approach to include fertilization as an optional activity in PlanWise, is to let the program generate alternatives both with and without fertilization. Then in the optimization model you can, for example, create constraints to allow or prevent fertilization, or set maximum allowed fertilization areas, to do a sensitivity analysis. Heureka will not simulate fertilzations unless certain critera are met, such as the site index must belong to a certain interval. Assume that you have created a control category called "Spruce management with fertiliziation", but that resulting programs contain no fertilizations. Assume also that you have linked another control category (with a no fertilization setting) called "Spruce management" to the same domain. This means that the alternatives generated with the two control categories may be identical, and that duplicate alternatives will be generated for those stand where no fertilization is allowed. To avoid this, there is a new setting in the Treatment Program Generator control table called "Also Generate Programs without Fertilization". This parameter is displayed when you select a fertilization policy (FP) other than "FP_NONE". If it is set to true, you will not need a second control category to generate non-fertilized alternatives, they will be generated anyway.

Note! We still recomend that you add conditions to a "fertilizable" forest domain that at least excludes unsuitable sites for fortilization.
You can read more about this new feature here: Fertilization in PlanWise

Bug fixes and other changes

Id	Category	Severity	Summary	Fixed_in_version	Resolution	Comment
0000261	TPG	feature	Duplicate programs may be generated in PlanWise if treatment criteria are not met	2.14.0	fixed	Duplicate programs may be generated in PlanWise if treatment criteria are not met
0000279	TPG	crash	TPG-error for birch-stand: "Invalid sapling volume, must be >= 0"	2.14.0	fixed	TPG-error for birch-stand: "Invalid sapling volume, must be >= 0"
0000283	TPG	major	Tactical TPG simulates planting in the wrong period	2.14.0	fixed	Tactical TPG simulates planting in the wrong period
0000294	Project handling	crash	Application crashes if an error is raised when importing data during project creation	2.14.0	fixed	Application crashes if an error is raised when importing data during project creation
0000289	Other	feature	Total area in overview table is actually productive area	2.14.0	open	Total area in overview table is actually productive area
0000284	Other	feature	Add result variable for sum of dead wood	2.14.0	fixed	Add result variable for sum of dead wood
0000286	Optimization	feature	Allow user to set the location of temporary optimization files	2.14.0	fixed	Allow user to set the location of temporary optimization files
0000278	Optimization	minor	Optimization list won't update after a new optimization was saved	2.14.0	fixed	Optimization list won't update after a new optimization was saved
0000292	Optimization	minor	Duplicate optimizations after performing Habitat model calculation	2.14.0	fixed	Duplicate optimizations after performing Habitat model calculation
0000293	Optimization	minor	Habitat models display no name if no Display name is set	2.14.0	fixed	Habitat models display no name if no Display name is set
0000291	HeurekaAPI	minor	Volume and mean age per species differ from those entered in the Heureka API	2.14.0	fixed	Volume and mean age per species differ from those entered in the Heureka API
0000282	General	feature	New default pricelists require recalculation	2.14.0	fixed	New default pricelists require recalculation
0000285	Data import	major	Can not import comma separated tree lists	2.14.0	fixed	Can not import comma separated tree lists
0000288	Data import	major	Error when importing FMPP test data set	2.14.0	fixed	Error when importing FMPP test data set
0000265	Data import	feature	Use date instead of inventory year	2.14.0	fixed	Use date instead of inventory year
0000290	Data import	major	Error when importing stand register with overstorey layer	2.14.0	fixed	The bug occurs for overstorey layers only in version 2.13 when either AreaLevel2 or AreaLevel3 is empty.