Version 2.2.0
Summary
- These release notes covers all changes made since version 2.1.0.0
- Version 2.2 contains several stability issue fixes and some bug fixes.
- The climate model has been improved and extended with more climate scenarios.
- A new Changelog page is available that contains information on minor updates.
New features
Modified climate model and additional climate scenarios
There are now three different climate scenarios available. Read more about importing climate scenarios here:
Help doc: Climate scenarios
Optional adjustment of treatment unit areas when import forest map
When importing a stand register, the productive area and the total area of a stand is retrieved from the corresponding stand register columns. If a forest map is also imported, the areas in the shape file may differ from the treatment unit area in the stand register. If the areas differ, you till be asked if you would like to update the areas based on the shape-file polygon. If so and you accept, the total areas are adjusted according to the GIS-data, and the productive areas are set according to the ratio between total area and productive area as given in the stand register file.
Minor modifications
Leaf area index in climate model adjusted for species proportion
In the climate model the leaf area index for a species is now adjusted for species proportion.
Default model changed for calculating sapling diameter
ProductionModel control table parameter Sapling Diameter Model has been changed back to NystromSoderberg from Elfving, i.e. the same as the one used before version 2.0. With Elfving's model, the diameter assigned to young deciduous trees (birch) is smaller than with NystromSoderberg, which leads to considerably less deciduous volume in long term prognosis.
Report function type "AverageOverSubset" and "AverageOverAll" replaced with "AverageOverSubset" and renamed to only "Average"
Now there is only one type of Average-value. If there are conditions it will apply to the Average value. AverageOverAll is the same as an Average without conditions. Old reports are handled automatically.
New result variables
Additional result variables has been added to result group Forest Data:
- Mean Height Arithmetic All Saplings
- Mean Age Main Saplings (should equal Mean Age (excl overstorey))
- Basal Area Excl Overstorey
- Basal Area Overstorey
Bug fixes and minor improvements
Improvement: Other broad-leaf species than birch in pine and spruce plantations
When the regeneration model creates a new stand, a considerable proportion of the stems consists of other species than the planted or sown species. They represent natural ingrowth. Previously, natural ingrowth of broad-leaves in young stands has been limited to birch, but now a proportion consists of "Other broad-leaves". The proportion of "Other broad-leaves trees" of all naturally ingrown broad-leaves in young stands are based on NFI survey data. It is set to between 4 percent (northern Sweden) and 16 percent (southern Sweden), of all broad-leaves.
Improvement: Occurrence of natural ingrowth of other species in deciduous plantations
The regeneration model has been improved so that when a deciduous species is selected as the main (regeneration) species, additional trees are added that represent naturally ingrowth. This has until now only been the case for conifer plantations. The underlying problem is that the regeneration model does not explicitly handle deciduous plantation. Hopefully, this is an area of future improvements.
Improvement: Initial state update function improved
When changing the analysis area in RegWise and PlanWise the initial state is recalculated in a more consistent way than before. The automatic updating can now also be switched off in 'Settings'
Improvement: Relaxed criteria for cleaning
The height interval criteria for cleaning has been changed so that if either (A) the mean height of main stems or (B) the mean height of all stems are within the height interval (default 2-6 m) the criteria is considered fulfilled. Previously, only (A) was considered.
Improvement: (RegWise only) An oak, beech or southern broad-leaf stand is regenerated with the same species if clear cut
(RegWise only) When a stand with dominating species oak, beech or southern deciduous is clear-cut it is automatically regenerated with the same species.
Improvement: (PlanWise only)Several fixes of optimziation neighborhood area function
(PlanWise only) The calculation of neighborhood areas used in the habitat area optization model element has suffered from several errors. (Do no confuse this model with the tool HabitatPrognosis).
Improvemnt: Empty rows ignored when importing treatment proposal
Empty rows were not handled when importing treatment proposals.
Improvement: Handling poorly formatted tree list input files
If additional columns existed (even if empty) then trees could not be linked to plots and stands. This is now handled so that empty columns located after the mandatory columns are ignored.
Bugfix: Report-level conditions gave unexpected average values
When using OR-condition for a whole report (PlanWise and RegWise), average values was calculated for the whole area, not only the area limited by the report condition.
Bugfix: A selected area that was removed was still selected after the removal
If you removed a Forest Area that was currently selected, the area was still selected internally in the program, which could lead to an exception or unexpected results in the Initial State Overview window. You had to reopen the project to clear the selection from memory. This has been fixed.
Bugfix: Larch trees were remapped to pine
Imported larch trees were remapped to pine after importing. This has now been fixed.
Bugfix: MIP problem rasied an expception when solved with MOSEK
Solving MIP optimization problems with MOSEK caused an exception, which has now been fixed (PlanWise).
Bugfix: Rounding to integer solution of optimization result did not work
Rounding an optimization result to an integer solution has not worked since version 1.9. This option is selected in the Optimization Settings menu ("Round to nearest integer solution"). The problem occurred after moving the optimization settings to project level from application level.
Note that the rounding procedure in PlanWise is not very smart and that rounding to an integer solution should generally be avoided. Rounding is not at all equivalent to solving a problem with binary conditions on the decision variables. Say for example that you have have a solution where 40 % of each stand should be left unmanaged, and the remaining 60 percent divided between two different management alternatives. The rounding algorithm selects for each stand the alternative with the highest decision variable value, so in this case all stands would be left unmanaged. This is of course an extreme example. The maximum number of fractional variables (i.e. "split stands") equals the number of constraints. Note that for a constraint element in PlanWise' optimization model builder may represent several constraints. For example a constraint element that loops over say 20 time periods, generates one constraint for each time period. With an increasing number of constraints, the number of fractional variables may be large and the rounded solution different from the basic LP solution.
Also note that rounding is done after the optimization problem is solved, which means that the results created with the report builder will not be exactly the same as the corresponding optimization results displayed in the optimization output window. A rounded solution may violate a constraint that was not violated in the basic LP solution.
Bugfix: Importing treatment proposals
Solving MIP optimization problems with MOSEK caused an exception, which has now been fixed (PlanWise).
Bugfix: Fertilization in RegWise
In RegWise, fertilization less than 10 years before enforced thinning or final felling lead to errors.
Bugfix: Problem with forest domain template when copying a project
Fixed problem with forest domain templates in RegWise and PlanWise when copying a project with "Save As". The forest domain template could not be found by the program when opening the copied project.
Bugfix: Error when opening copied project with named forest domain template
Fixed problem with forest domain templates in RegWise and PlanWise when copying a project with "Save As". The forest domain template could not be found by the program when opening the copied project.
Bugfix: No thinnings in next generation when final felling with seed trees
No thinnings were simulated in next generation if final felling was done with seed trees or shelterwood. This problem did not occur in version prior to version 1.9.
Help Documentation soon in English
About half of the help documentation is now translated. You can switch between the Swedish and English version by clicking on the flag icon on the right side of a topic header. The translation should be completed in February 2015.