Version 2.23 - Revision history

Jonare at 09:26, 18 November 2024

2024-11-18T09:26:23Z

Jonare: /* Version 2.23.0.1 */

2024-11-12T11:15:43Z

Version 2.23.0.1

Jonare at 11:12, 12 November 2024

2024-11-12T11:12:04Z

Jonare at 07:51, 11 November 2024

2024-11-11T07:51:41Z

Jonare at 12:45, 8 November 2024

2024-11-08T12:45:55Z

Jonare at 12:45, 8 November 2024

2024-11-08T12:45:31Z

Jonare at 12:45, 8 November 2024

2024-11-08T12:45:11Z

Jonare at 12:44, 8 November 2024

2024-11-08T12:44:21Z

Jonare at 09:56, 8 November 2024

2024-11-08T09:56:28Z

Jonare at 09:49, 8 November 2024

2024-11-08T09:49:04Z

@@ Line 48: / Line 48: @@
 *In some cases the wrong species was selected as regeneration species if the regeneration settings was set to "auto". This had to do with estimating the dominant species - as that could have change between felling and planting. Now it will work as expected and use dominant species before final felling if dominant species used to determine the regeneration species.
-==Version 2.23.0.1==
+==Version 2.23.0.2==
-*Fixes an issue where height correction factors where not calculated. If you have simulated tree lists in 2.23.0.0 we recommend that you redo the data import. Unfortunately 2.23 was shipped with an new bug where correction factors were not calculated treatment units in sub-areas levels, but only for the root area in the analysis area.
+Unfortunately 2.23 was shipped with an new bug where correction factors were not calculated treatment units in sub-areas levels, but only for the root area in the analysis area.
 <endFeed />
@@ Line 57: / Line 58: @@
 resolution = fixed
 color = true
-fixed_in_version = 2.23.0
+fixed_in_version = 2.23.0, 2.23.0.1, 2.23.0.2
 orderby = severity desc, fixed_in_version desc
 show = id,category,severity,summary,fixed_in_version,resolution
 </mantis>

@@ Line 49: / Line 49: @@
 ==Version 2.23.0.1==
-*Fixes an issue where height correction factors where not calculated. If you have simulated tree lists in 2.23 we recommend that you redo the data import. Unfortunately 2.23 was shipped with an new bug where correction factors were not calculated treatment units in sub-areas levels, but only for the root area in the analysis area.
+*Fixes an issue where height correction factors where not calculated. If you have simulated tree lists in 2.23.0.0 we recommend that you redo the data import. Unfortunately 2.23 was shipped with an new bug where correction factors were not calculated treatment units in sub-areas levels, but only for the root area in the analysis area.
 <endFeed />

@@ Line 47: / Line 47: @@
 *Changed how thinning intensity is handled in treatment proposals. The Thinning guide is now used if a user supplied value is missing in the treatment proposal.
 *In some cases the wrong species was selected as regeneration species if the regeneration settings was set to "auto". This had to do with estimating the dominant species - as that could have change between felling and planting. Now it will work as expected and use dominant species before final felling if dominant species used to determine the regeneration species.
 <endFeed />

@@ Line 1: / Line 1: @@
 <noinclude>
-Version 2.23 RC
+Version 2.23
 {{Languages| Version 2.23}}
-[[Category:Planned Release]]
+[[Category:Release]]
-[[language::en| ]]
+[[newsdate::2024-11-08]]  [[language::en| ]]
 </noinclude>
 <startFeed />

@@ Line 10: / Line 10: @@
 ==New Features==
 ===AMPL===
 AMPL has been added as a supported modeling language in Planwise. AMPL has been added primarily because of the long building times when using ZIMPL with some large optimization problems. In many user-cases it will be easier to switch modeling language rather than trying to optimize the formulation of the optimization problem itself. AMPL requires a user license. For non-commercial use and prototyping there is a [https://ampl.com/ce/ AMPL Community Edition] which comes with restrictions when it comes to using the commercial solvers.

@@ Line 6: / Line 6: @@
 </noinclude>
 <startFeed />
 ==Summary==
 This release includes the addition of AMPL as a supported modeling language, further improvements to the optimization module in PlanWise, improvements to the data import of large stand registers, and bug fixes - especially to the tactical TPG in PlanWise.
 ==New Features==
 ===AMPL===
 AMPL has been added as a supported modeling language in Planwise. AMPL has been added primarily because of the long building times when using ZIMPL with some large optimization problems. In many user-cases it will be easier to switch modeling language rather than trying to optimize the formulation of the optimization problem itself. AMPL requires a user license. For non-commercial use and prototyping there is a [https://ampl.com/ce/ AMPL Community Edition] which comes with restrictions when it comes to using the commercial solvers.
@@ Line 33: / Line 31: @@
 *We have added "Contains" and "BeginsWith" conditionals in domain builder, making it easier for some to quickly add a subset of their stands to a domain by matching, for example, part of a treatment unit's description.
 *A control category's number is now a browsable property, which is viewable in the property display (where control table settings are shown).
 ==Bug Fixes==
@@ Line 50: / Line 47: @@
 *Changed how thinning intensity is handled in treatment proposals. The Thinning guide is now used if a user supplied value is missing in the treatment proposal.
 *In some cases the wrong species was selected as regeneration species if the regeneration settings was set to "auto". This had to do with estimating the dominant species - as that could have change between felling and planting. Now it will work as expected and use dominant species before final felling if dominant species used to determine the regeneration species.
+<endFeed />
 ==Details from bugtracker==

@@ Line 15: / Line 15: @@
 AMPL has been added as a supported modeling language in Planwise. AMPL has been added primarily because of the long building times when using ZIMPL with some large optimization problems. In many user-cases it will be easier to switch modeling language rather than trying to optimize the formulation of the optimization problem itself. AMPL requires a user license. For non-commercial use and prototyping there is a [https://ampl.com/ce/ AMPL Community Edition] which comes with restrictions when it comes to using the commercial solvers.
-Before using the AMPL modeling language in Heureka AMPL must be installed. The path to the exectutable is the entered into the settings in Heureka (figure 1). After setup a new AMPL model can be created by using the Model Wizard in Heureka (figure 2) or changing an existing model to use AMPL instead of ZIMPL (figure 3). If the modeling language is changed user-supplied definitions need to be changed if they fail validation (figure 4). The validation of the AMPL syntax is done by Heureka and has been tested for models generated in Heureka, but some valid AMPL syntax might fail Heureka's validation . If a valid AMPL model is marked as invalid in Heureka please let us know.
+Before using the AMPL modeling language in Heureka AMPL must be installed. The path to the executable is the entered into the settings in Heureka (figure 1). After setup a new AMPL model can be created by using the Model Wizard in Heureka (figure 2) or changing an existing model to use AMPL instead of ZIMPL (figure 3). If the modeling language is changed user-supplied definitions need to be changed if they fail validation (figure 4). The validation of the AMPL syntax is done by Heureka and has been tested for models generated in Heureka, but some valid AMPL syntax might fail Heureka's validation . If a valid AMPL model is marked as invalid in Heureka please let us know.
 One difference between standard AMPL syntax and Heureka is that parameter and contraint declarations should be skipped since the names of a model's members is derived from the name they are assigned in Heureka. A parameter with the name p1 in Heureka and the definition MidPointUsed[0]; will be translated to param p1 := midpointused[0]; in the resulting AMPL model.