Version 2.12

<startFeed />

Summary

• Next version will be labelled 2.12 and is planned for release in October 2018.
• It will contain new functonality in RegWise to allow for simulation of land use changes. Until now the only land use supported been "Productive forest land". A new control table called "LandUse" has been added to the Domain Settings-type control category (RegWise only). Using this functionality requires a special-purpose adapted forest database.
• Low-productive forest land is a now supported as land-use type, and new growth functions has been developed for this (Kenneth Nyström 2018).
• The bucking algorithm (utbytesberäkningen) now includes a possibility to let roundwood logs (both timber and pulpwwod) be downgraded to fuelwood. This is a decision made at the harvesting site, so fuelwood will handled as a distinct assortment and put in its own pile of logs at the road side. There are separate settings for pulpwood and timber. For example, you could enter a higher downgrading proportion for pulpwood. Timber can be downgraded to pulpwwod, fuel wood and to waste. Pulpwood can be downgraded to fuelwood and waste. Fuelwood from downgraded logs is reported as a new assortment, in volume units. This is distinct from harvest residues which is reported in biomass dry weight units (branches and tree tops, and whole trees from bio fuel thinnings).
• Waste (vrak) refers to logs downgraded at the industry but has until now only been accounted for as a decrease in saw timber revenue. Now the volume is explicitly reported, from downgrading of timber and pulpwood. This means that the timber volume and pulpwood volume will be smaller in the new version if you have had a postive value for the waste proportion in the timber pricelist. A new result variable called "Waste Volume All Species" has now been added to result group Financial Value.
• The default price for waste has been changed from 80 to 0 SEK per volume unit.

• The HeurekaAPI has several fixes

<feedDate>2018-05-17</feedDate> <endFeed />

<startFeed />

New result variables

The following result variables have been added, see more info in the help documentation

Name	Result Group	Unit	Description
Fuelwood Volume	Financial Value	m3fub/ha	...
">Fuelwood Revenue	Financial Value	revenue per ha	...
Log Cull Volume	Financial Value	m3fub/ha	...
Log Cull Revenue	Financial Value	revenue per ha	...
Land Use Data	Land Use Data		New result group (RegWise only) with several new result variables

<startFeed />

Bug fixes and other changes

<feedDate>2018-10-31</feedDate> <endFeed /> <mantis> status = resolved, closed color = false fixed_in_version = 2.12.0, 2.12.1, 2.12.2 orderby = fixed_in_version desc, category desc show = id,category,severity,summary,fixed_in_version,resolution comment.215=(RegWise) When running the function "Rerun simulation" on a simulation that included both unmanaged and evenaged management programs, the unmanaged programs were not recreated. comment.219=When starting a new project and selecting databases, the loading of previously selected databases is performed on the GUI thread, locking the user interface. This could lead to a uynexpected program termination. comment.221=Random seed is now configured in the Simulation dialog only. An additional random seed is added to RegWise for Control category assignment comment.220=LPSolve, and maybe others, will not return an "Infeasible" solver status when a solution could not be found. The resulting dialog showed a confusing error message. comment.218=The project is now loaded AFTER the entire main form has finished loading comment.217=Even if all random seed were set to fixed values, two simulation results that weer expected to be identical were not. Reason was that for some function, the random seed could not be set to a fixed value. comment.225=Soil expectation value and terminal value were incorrectly calculated when the final felling treatment occurred in the period after the last planning period. comment.226=Newly deserialized control tables will always be a new instance instead of a cached copy of a previous instance comment.227=Error introduced in version 2.11. If young stand thinning type was set to "Biofuel thinning", then in subsequent thinning and final fellings, all roundwood was extracted as bio fuel instead of timber and pulpwood. comment.228=If you right-clicked a control category to delete it, but aborted the delete-operation by choosing Cancel, the control category apparently was removed anyway. But it was actually still there, if you reopened the project you could see it had not been deleted. The expected behaviour is of course that it should be visible after choosing Cancel which has no wbeen fixed. comment.229=Zip files can sometimes fail to extract, probably due to system culture settings. comment.230=For an optimization model parameter, there was a property called "Missing Value Substitute" which is redundant since the "Default value" takes care of missing values. comment.232=If the used had entered a custom path, this path was not used for log files and DotSpatial plugin handling. comment.233=If the user had set a custom Common directory in the path settings and but had no write permission or was unable to write to this diretory for some other reason (for example disk removed), the program would crash and then attempt to write to that location again when restarting the program, etc. comment.223=The result variables AlternativeSummaryData.ManagementSystem and TreatmentData.ManagementSystem were missing values if the control category used did not contain a distinct Treatment Program Generator control table. </mantis>