Version 2.14 - Revision history

Peder: /* Explicit dates saved */

2020-01-07T11:23:39Z

Explicit dates saved

Peder at 11:22, 7 January 2020

2020-01-07T11:22:43Z

Peder at 14:14, 8 November 2019

2019-11-08T14:14:20Z

Peder: /* Bug fixes and other changes */

2019-11-08T11:21:09Z

Bug fixes and other changes

Peder: /* Bug fixes and other changes */

2019-11-08T11:11:35Z

Bug fixes and other changes

Peder: /* Bug fixes and other changes */

2019-11-08T11:06:52Z

Bug fixes and other changes

Peder at 11:04, 8 November 2019

2019-11-08T11:04:55Z

Peder: /* Explicit dates saved */

2019-11-05T15:09:07Z

Explicit dates saved

Peder at 15:01, 5 November 2019

2019-11-05T15:01:35Z

Peder: /* PlanWise: Let non-fertilization alternatives be generated automatically */

2019-11-05T14:29:03Z

PlanWise: Let non-fertilization alternatives be generated automatically

@@ Line 49: / Line 49: @@
 <startFeed />
-====Explicit dates saved ====
+====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.
 <feedDate>2019-11-08</feedDate>

@@ Line 10: / Line 10: @@
 *"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
 <feedDate>2019-11-08</feedDate>
@@ Line 47: / Line 48: @@
 <endFeed />
 <startFeed />

@@ Line 1: / Line 1: @@
 <noinclude>
 Version 2.14
 {{Languages| Version 2.14}}
 [[Category:Release]]
 [[newsdate::2019-11-08]]  [[language::en| ]]
 </noinclude>
 <startFeed />

@@ Line 66: / Line 66: @@
 comment.284=New result variable added: See note above concerning new result variable for total dead wood
 comment.261=New feature added: See note above on possiblity to let fertilization-free programs be generated automatically alongside fertilization programs
-</mantis>
+comment.279=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.</mantis>

@@ Line 64: / Line 64: @@
 comment.290=The bug occurs for overstorey layers only in version 2.13 when either AreaLevel2 or AreaLevel3 is empty.
 comment.288=Error fixed that occurred when importing a FMPP-file with a format that was used under a test phase.
 </mantis>

@@ Line 4: / Line 4: @@
 {{Languages| Version 2.14}}
 [[Category:Release]]
-[[newsdate::2019-11-01]]  [[language::en| ]]
+[[newsdate::2019-11-08]]  [[language::en| ]]
 -->
 </noinclude>
@@ Line 13: / Line 13: @@
 *New result variable summarizes total dead wood
-<feedDate>2019-11-01</feedDate>
+<feedDate>2019-11-08</feedDate>
 <endFeed />
@@ Line 19: / Line 19: @@
 ====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.
-<feedDate>2019-11-01</feedDate>
+<feedDate>2019-11-08</feedDate>
 <endFeed />
 See the help documentation for more information: [{{HeurekaHelpLinkEng}}projectstartdate.htm English] [{{HeurekaHelpLink}}projectstartdate.htm Swedish]
@@ Line 26: / Line 26: @@
 ====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.
-<feedDate>2019-11-01</feedDate>
+<feedDate>2019-11-08</feedDate>
 <endFeed />
 See the help documentation for more information: [{{HeurekaHelpLinkEng}}kontrolltabeller.htm#conditional_controltables English] [{{HeurekaHelpLink}}kontrolltabeller.htm#conditional_controltables Swedish]
@@ Line 33: / Line 33: @@
 ====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.
-<feedDate>2019-11-01</feedDate>
+<feedDate>2019-11-08</feedDate>
 <endFeed />
@@ Line 39: / Line 39: @@
 ====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.
-<feedDate>2019-11-01</feedDate>
+<feedDate>2019-11-08</feedDate>
 <endFeed />
 <br>You can read more about this new feature here: [{{HeurekaHelpLinkEng}}godsling.htm#fertplanwise Fertilization in PlanWise]
@@ Line 46: / Line 46: @@
 ====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).
-<feedDate>2019-11-01</feedDate>
+<feedDate>2019-11-08</feedDate>
 <endFeed />
@@ Line 53: / Line 53: @@
 ====Bug fixes and other changes====
-<feedDate>2019-11-01</feedDate>
+<feedDate>2019-11-08</feedDate>
 <endFeed />
 <mantis>