Version 2.21
Version 2.21
2023-04-18
<startFeed />
Summary
New Features
Correction Factors per Species and Period
Monte Carlo-simulations in RegWise
Checkerboard Forestry in PlanWise
Shrub Cover Models
Environmental Goal Indicators
Other Changes
- Updated application suite to .NET Framework 4.8
- Changed name of control table Soil Model to Carbon
- Changed name of result group Recreation to Non-wood ecosystem services, including also the shrub cover model results
- Changed name of result group Harvested Wood Products to Carbon in Harvested Wood Products
- Added settings for Harvested Wood Products to the Carbon control table
- Time between thinning and final felling is now specified in years instead of periods, in the Treatment Program Generator control table
- Faster loading of map control in initial state
- Simplified import format for optimization results (the old format is still supported)
- Birch added as its own category in the Dead Wood result group
- User can now specify a fraction of cut stems to leave in forest as dead wood after a final felling treatment in the Treatment Model control table
Bug Fixes
- RotationAgeFactor was not considered when calculating initial state
- Register Tree Data had a faulty plot type check
- Possible incorrect wait time between thinnings and other treatments in tactical TPG
- Tree List Importer didn't show an error when the mandatory column InventoryYear was missing
- Mortality was sometimes over- or underestimated in RegWise
- Wrong decay class assigned to dead trees in IPAK importer
- NPV incorrectly calculated in the optimization summary (not in the actual results)
- StandWise: Overstorey trees that were previously removed would return when backing to period 0, and never be removed again
- Fixed error when cleaning period overlapped final felling period in TPG
- Fixed error when importing optimization model item
- Fixed crash when calculating cliques and clusters
- Forwarder cost could be calculated to a negative value in very harsh conditions
- After treatment proposals were applied, the control category for the first generation was always used even if a final felling was performed
<feedDate>2023-04-18</feedDate> <endFeed />
Details from bugtracker
<mantis> status = resolved, closed resolution = fixed color = false fixed_in_version = 2.21.0 orderby = fixed_in_version desc, category desc show = id,category,severity,summary,fixed_in_version,resolution summary_as_comment = true </mantis>