Version 2.14/sv
2019-11-08
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
- Multiple TPG-simulation results can be included in the optimization model
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
A new setting in the Treatment Program Generator control table called "Also Generate Programs without Fertilization" simplifies things if you want create treatment programs both with and without fertilization. If the parameter is set to true, you do not need to add a separate control category to generate non-fertilized alternatives, they will be generated anyway.
You can read more about this new feature here: Fertilization in PlanWise
Explicit dates saved
In previous versions only the inventory year has been saved in the database when importing data, but now on the explicit date is kept (if available). The column name "InventoryYear" in the stand register is renamed to "Date" (although "InventoryYear" can still be used as column name).
Multiple TPG-simulation can be included in the same optimization model
When solving an optimization problem, multiple TPG-simulation results can now be selected as input data. A condition is that no two TPG-simulations contains the same treatment unit, and an error message will be displayed of that criteria is violated.
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 | New feature added: See note above on possiblity to let fertilization-free programs be generated automatically alongside fertilization programs |
| 0000279 | TPG | crash | TPG-error for birch-stand: "Invalid sapling volume, must be >= 0" | 2.14.0 | fixed | Repeated moose grazing on young birch trees could lead to erors in volume calculation, where for example a birch could be 70 years but only 2 m high. To prevent the creation of extreme outliers in a simulation, a tree is therefore killed if its height has been reduced to less than 2 m during two periods in a row. |
| 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 |
| 0000284 | Other | feature | Add result variable for sum of dead wood | 2.14.0 | fixed | New result variable added: See note above concerning new result variable for total dead wood |
| 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 |
| 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 |
| 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 |
| 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 |
| 0000265 | Data import | feature | Use date instead of inventory year | 2.14.0 | fixed | Use date instead of inventory year |
| 0000288 | Data import | major | Error when importing FMPP test data set | 2.14.0 | fixed | Error fixed that occurred when importing a FMPP-file with a format that was used under a test phase. |
| 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. |