Difference between revisions of "Version 2.7.0"
| Line 4: | Line 4: | ||
{{Languages| Version 2.7.0}} | {{Languages| Version 2.7.0}} | ||
[[Category:Release]] | [[Category:Release]] | ||
| − | [[newsdate::2017- | + | [[newsdate::2017-05-10]] [[language::en| ]] |
</noinclude> | </noinclude> | ||
--> | --> | ||
| Line 10: | Line 10: | ||
==Summary== | ==Summary== | ||
| − | <feedDate>2017- | + | <feedDate>2017-05-10</feedDate> |
<endFeed /> | <endFeed /> | ||
| Line 17: | Line 17: | ||
====New feature: Possible to populate a set from a file in PlanWise optimization tool==== | ====New feature: Possible to populate a set from a file in PlanWise optimization tool==== | ||
The ZIMPL syntax for reading set elements from a file is now supported in Heureka's optimization model builder. | The ZIMPL syntax for reading set elements from a file is now supported in Heureka's optimization model builder. | ||
| − | <feedDate>2017- | + | <feedDate>2017-05-10</feedDate> |
<endFeed /> | <endFeed /> | ||
| Line 25: | Line 25: | ||
When using cost model "Skogforsk", you can now change the coefficients for the terminal time function component for the forwarder machine (function t4). You can also change the coefficients the felling and processing time in final felling (function t2_finalFelling). | When using cost model "Skogforsk", you can now change the coefficients for the terminal time function component for the forwarder machine (function t4). You can also change the coefficients the felling and processing time in final felling (function t2_finalFelling). | ||
| − | <feedDate>2017- | + | <feedDate>2017-05-10</feedDate> |
<endFeed /> | <endFeed /> | ||
| Line 31: | Line 31: | ||
====New feature: Cost model as plugin==== | ====New feature: Cost model as plugin==== | ||
The plugin framework now also supports adding custom cost models. | The plugin framework now also supports adding custom cost models. | ||
| − | <feedDate>2017- | + | <feedDate>2017-05-10</feedDate> |
<endFeed /> | <endFeed /> | ||
| Line 37: | Line 37: | ||
In StandWise charts, you can now show stacked bars for the number of stems per diameter class and tree species. | In StandWise charts, you can now show stacked bars for the number of stems per diameter class and tree species. | ||
| − | <feedDate>2017- | + | <feedDate>2017-05-10</feedDate> |
<endFeed /> | <endFeed /> | ||
| Line 44: | Line 44: | ||
====Improvement: Calculation of adjacency pairs magnitudes faster ==== | ====Improvement: Calculation of adjacency pairs magnitudes faster ==== | ||
The calculation of shared edge lengths between adjacent stand polygons has been cut down to 2-10 5 compared to previous versions. For a test with 50000 stand polygons it now takes about one minute. Before it would raise an error after more than 30 minutes. | The calculation of shared edge lengths between adjacent stand polygons has been cut down to 2-10 5 compared to previous versions. For a test with 50000 stand polygons it now takes about one minute. Before it would raise an error after more than 30 minutes. | ||
| − | + | <feedDate>2017-05-10</feedDate> | |
| − | <feedDate>2017- | ||
<endFeed /> | <endFeed /> | ||
| + | <startFeed /> | ||
====Improvement: Tactical TPG fixed and improved ==== | ====Improvement: Tactical TPG fixed and improved ==== | ||
The tactical TPG has been subject to major changes. You can now choose to enforce the tactical management programs to only allows harvest treatments in the five-year period that the strategic optimization dictates. The discrepancies between a tactical and strategic program, where a certain treatment is done in the same year, have been minimized. For example, the net present value could differ considerably altough apparently the same managament program was simulated. The tactical TPG would also allow treatment programs that violated constraints the control table settings, this has also been fixed. As a result, the tactical TPG is now generating alternatives that are more conformant with the stategic plan, if such is selected as starting point, and is also faster. | The tactical TPG has been subject to major changes. You can now choose to enforce the tactical management programs to only allows harvest treatments in the five-year period that the strategic optimization dictates. The discrepancies between a tactical and strategic program, where a certain treatment is done in the same year, have been minimized. For example, the net present value could differ considerably altough apparently the same managament program was simulated. The tactical TPG would also allow treatment programs that violated constraints the control table settings, this has also been fixed. As a result, the tactical TPG is now generating alternatives that are more conformant with the stategic plan, if such is selected as starting point, and is also faster. | ||
| + | <feedDate>2017-05-10</feedDate> | ||
| + | <endFeed /> | ||
| + | |||
| + | <startFeed /> | ||
| + | ====Habitat models ==== | ||
| + | The habitat model tool released as a beta version in version 2.6 has been improved, and errors found have been fixed. You can now also create new habitat models. It is still condisered a beta version. The interior edge component for Alectoria sarmentosa (Garnlav) is not yet implemented correctly. | ||
| + | <feedDate>2017-05-10</feedDate> | ||
| + | <endFeed /> | ||
| − | <feedDate>2017- | + | <startFeed /> |
| + | ==== ==== | ||
| + | <feedDate>2017-05-10</feedDate> | ||
<endFeed /> | <endFeed /> | ||
| + | <startFeed /> | ||
====Improvement: Web map settings saved between working sessions ==== | ====Improvement: Web map settings saved between working sessions ==== | ||
| − | When you | + | When you select e a certain web map as background map, the selection will be saved to the next working session. |
| − | + | <feedDate>2017-05-10</feedDate> | |
| − | <feedDate>2017- | ||
<endFeed /> | <endFeed /> | ||
| Line 64: | Line 74: | ||
====Bug fix: Coefficients for cost function "Indelningspaketet" ("FMPP") ==== | ====Bug fix: Coefficients for cost function "Indelningspaketet" ("FMPP") ==== | ||
In control table Cost and Revenue, you can modify the forwarder driving speed, by either using a fixed speed or a function. In cost function "Indelningspaketet/FMPP", the driving speed function was used even if you had entered that a fixed speed should be used. Also, for the same function, the default values for forwarding in final felling have been changed to 74 and 2.16, instead of 60 and 2.84. The latter applies for thinning, not final felling. | In control table Cost and Revenue, you can modify the forwarder driving speed, by either using a fixed speed or a function. In cost function "Indelningspaketet/FMPP", the driving speed function was used even if you had entered that a fixed speed should be used. Also, for the same function, the default values for forwarding in final felling have been changed to 74 and 2.16, instead of 60 and 2.84. The latter applies for thinning, not final felling. | ||
| − | <feedDate>2017- | + | <feedDate>2017-05-10</feedDate> |
<endFeed /> | <endFeed /> | ||
| Line 71: | Line 81: | ||
The function for calculating circular neoghborhood areas aa part of the optimization model builder would raise an exception.... {ANGE NÄR OCH VARFÖR) | The function for calculating circular neoghborhood areas aa part of the optimization model builder would raise an exception.... {ANGE NÄR OCH VARFÖR) | ||
| − | <feedDate>2017- | + | <feedDate>2017-05-10</feedDate> |
<endFeed /> | <endFeed /> | ||
| Line 77: | Line 87: | ||
====Bug fix: The resimulation of a strategic optimizaiton has been fixed ==== | ====Bug fix: The resimulation of a strategic optimizaiton has been fixed ==== | ||
In version 2.6 a beta version of this function was released, but several issues were discovered. These has now hopefully been fixed. | In version 2.6 a beta version of this function was released, but several issues were discovered. These has now hopefully been fixed. | ||
| − | <feedDate>2017- | + | <feedDate>2017-05-10</feedDate> |
<endFeed /> | <endFeed /> | ||
| Line 84: | Line 94: | ||
====Bug fix: User-defined MinFinalFellingAge not copied properly to a new coontrol table ==== | ====Bug fix: User-defined MinFinalFellingAge not copied properly to a new coontrol table ==== | ||
When copying a TreatmentModel control table, the value for MinFinalFellingAge were not copied properly (the references to the source table were kept), meaning that changing a value in one control table, would affect the values in the copied table and in the copy. This has been fixed. | When copying a TreatmentModel control table, the value for MinFinalFellingAge were not copied properly (the references to the source table were kept), meaning that changing a value in one control table, would affect the values in the copied table and in the copy. This has been fixed. | ||
| − | <feedDate>2017- | + | <feedDate>2017-05-10</feedDate> |
<endFeed /> | <endFeed /> | ||
| Line 90: | Line 100: | ||
====Bug fix: "Invalid height growth" ==== | ====Bug fix: "Invalid height growth" ==== | ||
This error would occur in rare cases when a sapling plot was transformed to a tree plot before all saplings were activated. This specficic cause of this error has been fixed (meaning that if the error message turns up again it has othere causes). | This error would occur in rare cases when a sapling plot was transformed to a tree plot before all saplings were activated. This specficic cause of this error has been fixed (meaning that if the error message turns up again it has othere causes). | ||
| − | <feedDate>2017- | + | <feedDate>2017-05-10</feedDate> |
<endFeed /> | <endFeed /> | ||
| Line 96: | Line 106: | ||
====Bug fix: Database error when calculating common border length for very large dataset ==== | ====Bug fix: Database error when calculating common border length for very large dataset ==== | ||
The calculation of shared edge legths between adjacenent polygons would raise an error for a dataset containng 50000 stands or more. | The calculation of shared edge legths between adjacenent polygons would raise an error for a dataset containng 50000 stands or more. | ||
| − | <feedDate>2017- | + | <feedDate>2017-05-10</feedDate> |
<endFeed /> | <endFeed /> | ||
| Line 102: | Line 112: | ||
====Bug fix: Overstory layers not handled correctly in BufferZones tool ==== | ====Bug fix: Overstory layers not handled correctly in BufferZones tool ==== | ||
Import a csv-file created with BufferZone-tool would fail if the original stand register contained rows with overstriy layers. | Import a csv-file created with BufferZone-tool would fail if the original stand register contained rows with overstriy layers. | ||
| − | <feedDate>2017- | + | <feedDate>2017-05-10</feedDate> |
| + | <endFeed /> | ||
| + | |||
| + | ==Other changes == | ||
| + | <startFeed /> | ||
| + | ====DotSpatial GIS-library updated ==== | ||
| + | <feedDate>2017-05-10</feedDate> | ||
| + | The GIS-library used, DotSpatial, has been updated to version 2.0. | ||
<endFeed /> | <endFeed /> | ||
Revision as of 10:09, 8 May 2017
Summary
New features
New feature: Possible to populate a set from a file in PlanWise optimization tool
The ZIMPL syntax for reading set elements from a file is now supported in Heureka's optimization model builder.
New feature: More cost function coefficients can be modified
When using cost model "Skogforsk", you can now change the coefficients for the terminal time function component for the forwarder machine (function t4). You can also change the coefficients the felling and processing time in final felling (function t2_finalFelling).
New feature: Cost model as plugin
The plugin framework now also supports adding custom cost models.
New feature: StandWise chart can show number of stems per species in diameter distribution diagrams
In StandWise charts, you can now show stacked bars for the number of stems per diameter class and tree species.
Improvements
Improvement: Calculation of adjacency pairs magnitudes faster
The calculation of shared edge lengths between adjacent stand polygons has been cut down to 2-10 5 compared to previous versions. For a test with 50000 stand polygons it now takes about one minute. Before it would raise an error after more than 30 minutes.
Improvement: Tactical TPG fixed and improved
The tactical TPG has been subject to major changes. You can now choose to enforce the tactical management programs to only allows harvest treatments in the five-year period that the strategic optimization dictates. The discrepancies between a tactical and strategic program, where a certain treatment is done in the same year, have been minimized. For example, the net present value could differ considerably altough apparently the same managament program was simulated. The tactical TPG would also allow treatment programs that violated constraints the control table settings, this has also been fixed. As a result, the tactical TPG is now generating alternatives that are more conformant with the stategic plan, if such is selected as starting point, and is also faster.
Habitat models
The habitat model tool released as a beta version in version 2.6 has been improved, and errors found have been fixed. You can now also create new habitat models. It is still condisered a beta version. The interior edge component for Alectoria sarmentosa (Garnlav) is not yet implemented correctly.
Improvement: Web map settings saved between working sessions
When you select e a certain web map as background map, the selection will be saved to the next working session.
Bug fixes
Bug fix: Coefficients for cost function "Indelningspaketet" ("FMPP")
In control table Cost and Revenue, you can modify the forwarder driving speed, by either using a fixed speed or a function. In cost function "Indelningspaketet/FMPP", the driving speed function was used even if you had entered that a fixed speed should be used. Also, for the same function, the default values for forwarding in final felling have been changed to 74 and 2.16, instead of 60 and 2.84. The latter applies for thinning, not final felling.
Bug fix: Calculation of neighborhood circle in optimization model fixed
The function for calculating circular neoghborhood areas aa part of the optimization model builder would raise an exception.... {ANGE NÄR OCH VARFÖR)
Bug fix: The resimulation of a strategic optimizaiton has been fixed
In version 2.6 a beta version of this function was released, but several issues were discovered. These has now hopefully been fixed.
Bug fix: User-defined MinFinalFellingAge not copied properly to a new coontrol table
When copying a TreatmentModel control table, the value for MinFinalFellingAge were not copied properly (the references to the source table were kept), meaning that changing a value in one control table, would affect the values in the copied table and in the copy. This has been fixed.
Bug fix: "Invalid height growth"
This error would occur in rare cases when a sapling plot was transformed to a tree plot before all saplings were activated. This specficic cause of this error has been fixed (meaning that if the error message turns up again it has othere causes).
Bug fix: Database error when calculating common border length for very large dataset
The calculation of shared edge legths between adjacenent polygons would raise an error for a dataset containng 50000 stands or more.
Bug fix: Overstory layers not handled correctly in BufferZones tool
Import a csv-file created with BufferZone-tool would fail if the original stand register contained rows with overstriy layers.
Other changes
DotSpatial GIS-library updated
The GIS-library used, DotSpatial, has been updated to version 2.0.