Version 2.13: Difference between revisions
No edit summary |
|||
| 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.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.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. | |||
</mantis> | </mantis> | ||
Revision as of 12:35, 14 June 2019
<startFeed />
Summary
Version 2.13.0 is ... <feedDate>2019-06-14</feedDate> <endFeed />
<startFeed />
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> <endFeed /> For more info on the ZIMPL mathematical program language, see https://zimpl.zib.de.
<startFeed />
Bug fixes and other changes
<feedDate>2019-06-14</feedDate> <endFeed /> <mantis> status = resolved, closed color = false fixed_in_version = 2.13.0, 2.13.1, 2.13.2, 2.13.3 orderby = fixed_in_version desc, category desc 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. 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. </mantis>