Version 2.13 - Revision history

Peder at 12:39, 25 June 2019

2019-06-25T12:39:36Z

Peder at 12:38, 25 June 2019

2019-06-25T12:38:07Z

Peder at 14:47, 18 June 2019

2019-06-18T14:47:48Z

Peder at 14:39, 18 June 2019

2019-06-18T14:39:32Z

Peder at 14:38, 18 June 2019

2019-06-18T14:38:23Z

Peder: /* Bug fixes and other changes */

2019-06-18T14:25:08Z

Bug fixes and other changes

Peder: /* Bug fixes and other changes */

2019-06-18T14:24:35Z

Bug fixes and other changes

Peder: /* Bug fixes and other changes */

2019-06-18T14:23:32Z

Bug fixes and other changes

Peder: /* Bug fixes and other changes */

2019-06-18T14:17:50Z

Bug fixes and other changes

Peder at 14:12, 18 June 2019

2019-06-18T14:12:21Z

@@ Line 3: / Line 3: @@
 {{Languages| Version 2.13}}
 [[Category:Release]]
-[[newsdate::2019-06-19]]  [[language::en| ]]
+[[newsdate::2019-06-25]]  [[language::en| ]]
 </noinclude>
 <startFeed />
 ==Summary==
 *Version 2.13.0 contains bug fixes and improvements.
 *The time for building an optimization model in PlanWise has been reduced to about one third.
-<feedDate>2019-06-19</feedDate>
+<feedDate>2019-06-25</feedDate>
 <endFeed />
@@ Line 16: / Line 15: @@
 ====Optimization time reduced====
 The time for compiling an optimization problem has been reduced to about 35 % of what is was before. This has been accomplished by compiling the ZIMPL source code with a less extreme precision requirement than the ZIMPL-default. We now use double (16 digits) precision, which is more than enough for the kind of problems solved.
-<feedDate>2019-06-19</feedDate>
+<feedDate>2019-06-25</feedDate>
 <endFeed />
 For more info on the ZIMPL mathematical program language, see https://zimpl.zib.de.

@@ Line 1: / Line 1: @@
 <noinclude>
 Version 2.13
@@ Line 6: / Line 5: @@
 [[newsdate::2019-06-19]]  [[language::en| ]]
 </noinclude>
--->
 <startFeed />
 ==Summary==

@@ Line 1: / Line 1: @@
 <!--
 <noinclude>
-Version 2.13.0
+Version 2.13
-{{Languages| Version 2.13.0}}
+{{Languages| Version 2.13}}
 [[Category:Release]]
 [[newsdate::2019-06-19]]  [[language::en| ]]

@@ Line 4: / Line 4: @@
 {{Languages| Version 2.13.0}}
 [[Category:Release]]
-[[newsdate::2019-06-14]]  [[language::en| ]]
+[[newsdate::2019-06-19]]  [[language::en| ]]
 </noinclude>
 -->
@@ Line 11: / Line 11: @@
 *Version 2.13.0 contains bug fixes and improvements.
 *The time for building an optimization model in PlanWise has been reduced to about one third.
-<feedDate>2019-06-14</feedDate>
+<feedDate>2019-06-19</feedDate>
 <endFeed />
@@ Line 17: / Line 17: @@
 ====Optimization time reduced====
 The time for compiling an optimization problem has been reduced to about 35 % of what is was before. This has been accomplished by compiling the ZIMPL source code with a less extreme precision requirement than the ZIMPL-default. We now use double (16 digits) precision, which is more than enough for the kind of problems solved.
-<feedDate>2019-06-14</feedDate>
+<feedDate>2019-06-19</feedDate>
 <endFeed />
 For more info on the ZIMPL mathematical program language, see https://zimpl.zib.de.
@@ Line 23: / Line 23: @@
 <startFeed />
 ====Bug fixes and other changes====
-<feedDate>2019-06-14</feedDate>
+<feedDate>2019-06-19</feedDate>
 <endFeed />
 <mantis>

@@ Line 9: / Line 9: @@
 <startFeed />
 ==Summary==
-Version 2.13.0 is ...
+*Version 2.13.0 contains bug fixes and improvements.
 <feedDate>2019-06-14</feedDate>
 <endFeed />

@@ Line 42: / Line 42: @@
 comment.260 = When importing a stand register without basal area, it will be assumed to be a young stand (sapling plot), even if the tree heights are far above the young stand phase. This may cause errors in the simulation. this has been fixed by raising a warning if the mean height is larger than 7 m but basal area is missing.
 comment.254 = Fixed
-comment.262 = In the optimization model explorer, you can now also copy parameters of type "formula" and "single value".
+comment.262 = In the optimization model explorer, you can now also copy a parameter of type "formula" and "single value".
 comment.270 = The simplified view did now work for control tables that contained parameters that are no longer in use.
 </mantis>

@@ Line 33: / Line 33: @@
 comment.268 = Result variable "Generation" in result table RESULT was not assigned (this variable is not available in reports, only for users creating reports with their own SQL-queries).
 comment.256 = For some treatment units, no tactical program were generated in the following specific case: A strategic optimization was used as starting point when running the Tactical Treatment Program Generator, and some treatments hade been assigned from user-imported treatment proposals. These were not recognized as plausible alternatives when running the tactical TPG. This has been fixed so the tactical TPG enforces a management schedule as close as possible to the one in the strategic solution.
-comment.244 = Extraction of harvest residues when final felling was controlled by the settings for the subsequent generation instead of the setting of the current generation. For example, if generation 1 and generation 2 had different settings for whether harvest residues should be extracted, the generation 2 was applied for all generations. This has now been fixed.
+comment.244 = Extraction of harvest residues after final felling was controlled by the settings for the subsequent instead of the current generation. For example, if generation 1 and generation 2 had different settings for whether harvest residues should be extracted or not, then generation 2 was applied for all generations. This has now been fixed.
 comment.268 = "B3" is an NFI maturity class that corresponds to R2. This error is very specific for simulations where NFI-data is used input data, and when the young stand B3-plot is located within an older stands.
 comment.257 = It has come to our attention that the volume function for larch (by Charles Carbonnier) is not applicable for trees with dbh larger than 50 cm, because after that the volume decreases with increasing diameter, due to the function's mathematical form. Volume may even be negativ when diameter approaches 70 cm. Until better functions are available, Brandels volume function for pine (in southern Sweden) is now used for larches with dbh > 50 cm.

@@ Line 31: / Line 31: @@
 show = id,category,severity,summary,fixed_in_version,resolution
 summary_as_comment = true
 comment.268 = Result variable "Generation" in result table RESULT was not assigned (this variable is not available in reports, only for users creating reports with their own SQL-queries).
 comment.256 = For some treatment units, no tactical program were generated in the following specific case: A strategic optimization was used as starting point when running the Tactical Treatment Program Generator, and some treatments hade been assigned from user-imported treatment proposals. These were not recognized as plausible alternatives when running the tactical TPG. This has been fixed so the tactical TPG enforces a management schedule as close as possible to the one in the strategic solution.
@@ Line 44: / Line 42: @@
 comment.260 = When importing a stand register without basal area, it will be assumed to be a young stand (sapling plot), even if the tree heights are far above the young stand phase. This may cause errors in the simulation. this has been fixed by raising a warning if the mean height is larger than 7 m but basal area is missing.
 comment.254 = Fixed
--->
+summary.262 = In the optimization model explorer, you can now also copy parameters of type "formula" and "single value".