Version 2.10

Languages:

English  • svenska

2018-02-05

<startFeed />

Summary

Version 2.10.0 contains bug fixes and improvements of existing functionality. A new feature is that the program can split treatment units when importing data, including the GIS polygons. <feedDate>2018-02-05</feedDate> <endFeed />

Minor updates for version 2.10

<startFeed />

Version 2.10.1

Version 2.10.1 contains the following bug fixes:

• An infinite loop could occur when making growth projections, due to recent code changes in the sapling damage model.
• A database script required SQL Server version 2012 or later, but some users still use version 2008 R2, the oldest version supported by Heureka. The script has been rewritten.

<feedDate>2018-02-07</feedDate> <endFeed /> <startFeed />

Version 2.10.2

Fixed some issues with the new function for splitting treatment units, see below. <feedDate>2018-02-13</feedDate> <endFeed />

New features

<startFeed />

New feature: Split treatment units

It is now possible to let the program automatically split a treatment unit into a main stand and a retention patch ("NC-areas"). Also the GIS polygon is split, if provided. <feedDate>2018-02-05</feedDate> <endFeed /> You can do this when importing data, or by cloning an already imported area.

<startFeed />

FMPP custom import options

The import of FMPP (Indelningspaketet) data has been made a bit more flexible. The importer allows user-defined species code mappings and additional site variables för Heureka. You can read more about it here: <feedDate>2018-02-05</feedDate> <endFeed /> Import customized FMPP data

<startFeed />

Bug fixes and other changes

<feedDate>2018-02-05</feedDate> <endFeed /> <mantis> status = resolved, closed color = false fixed_in_version = 2.10.0, 2.10.1, 2.10.2, 2.10.3 orderby = fixed_in_version desc, category desc show = id,category,severity,summary,fixed_in_version,resolution comment.167=If forest domain said CCF but an imported management proposal said final felling there was a conflict. Now final felling is done according to proposal, after that the control category is followed. comment.169=Added support for Gurobi 7.5 and Mosek 8.1 optimization solvers (latest versions). Support for Gurobi version 5.6 was dropped. comment.171=An exception occurred when a project template was spplied to an existing project if the result database did not exist. comment.172=If "?request=GetCapabilities&service=wmts" argument was missing from url when adding a custom WMTS-service an exception occurred. This is now added automatically if missing. comment.173=If a custom WMTS service was added, it was not stored and not added to the list if predefined services. This was only implmented for WMS-services, but now works for WMTS as well. comment.174=If an optimization model item, for example a parameter, was included in a constraint or another definition, then no warning was given if the parameter was marked to be excluded. comment.175=An optimization should automatically be revalidated when an excluded item is reincluded. comment.176=After solver has terminated, inform user of the obtained solution status. This has only been displayed in the output window, so a user may have missed that a solution is suboptimal, for example if solver was terminated due to the time limit. comment.177=If a stand was opened in StandWise, and you chose to remove the analysis are to which the stand belonged, you could still select the stand after the data removal. If you then click on Refresh an exception occurred. comment.179=If you change the language from Swedish to English or vice versa, the application will be restarted immediately with the new language settings. comment.8=Windows built-in Datagrid control does not allow custom formatting of columns. comment.161=Previous map settings, included manually added shape files etc, are now saved between session. comment.182=If using the (recently added) LandUse-variable in a forest domain condition, an exception would occur if LandUse had no value. comment.166=All previously imported treatment proposals were removed when importing a new treatment proposal file, even in other area nodes. comment.180=An error occurred when opening an imported StandWise project if the database was unavailable. This error was unfortunatley introduced in version 2.9.3. comment.184=The Initial State details table view was emptied after clicking the Update-button when the imported data was FMPP-data comment.157=Same type of "copy to Excel"-function as in PlanWise is now available in StandWise. comment.183=Tree retention settings were ignored when imported treatment proposal were applied, this has been changed so that tree retention settings are always considered. See also 181. comment.181=Tree retention did not work as expected in selection fellings, when for a certain species all other trees than the retained should be removed. See also 183. comment.135=The column aliases for used-defined variables are now displayed in stand-level TPG-result table views. However, no table views where multiple stands can be displayed simultaneously support this feature, since two stands may originate from different stand registers, with different column aliases. comment.186=A database script required SQL Server version 2012 or later, but some users still use version 2008 R2, the oldest version supported by Heureka. The script has been rewritten. comment.185=An infinite loop could occur when making growth projections, due to recent code changes in the sapling damage model. </mantis>