Difference between revisions of "Version 2.2.0"

Revision as of 13:54, 22 December 2014

Summary

Version 2.2 contains several stability issue fixes and some bug fixes.
A new Changelog page is available that contains information on minor updates.

Heading

Text

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.

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: Larch explicit species group in stand register import file (optional)

You can now enter species information for larch just as you can do for pine, spruce and other species. Before this, you had to enter data for larch in the columns containing the string "SpeciesUser". However, you can still use those column (for larch or another species).

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.

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. feedDate>2014-12-22</feedDate>

Bug: Larch trees were remapped to pine

Imported larch trees were remapped to pine after importing. This has now been fixed.

Bug: MIP problem rasied an expception when solved with MOSEK

Solving MIP optimization problems with MOSEK caused an exception, which has now been fixed (PlanWise).

Bug: Rounding to integer solution of optimization result did not work

Rounding to integer solution of optimization result has not worked since version 1.9. The problem occurred after moving the optimization settings to project level from application level.

Bug: Importing treatment proposals