Version 1.9.1

Languages:

[[::Version 1.9.1|English]]

2012-09-14

Version 1.9.1 is a major update. It has a new approach to define thinnings. Moreover, pre-defined treatment proposals can now be imported and analyzed.

Special notes

• A new column called SiteIndexManagement has been added to Stand register template version 3. So if you intend to import an old version 3-template, you must add this column. See below what this column is used for. You can download the stand register template from our ftp-server here: download ImportTemplate_ver3.xlsm. Next version (1.9.2) will use column names instead of column order, so this is hopefully the last time you have to worry about changes in the stand register template.

New features

• An improved thinning model has been added that allows a more detailed control of what species to retain, and how to thin each species. You can also define different specifications for first and other thinnings. Read more about this in our help documentation (in Swedish only). However, the old version (thinning algorithm = "HuginOld") is still used as default, but we encourage you to try out the new model!

• New report (result) variables have been added for species-level thinning grade, thinning form and harvested mean diameter. They are available for all harvest activities. As with other variables, you must select the variables of interest before running a simulation in RegWise and in PlanWise in order to save them as results.

• You can now import your own treatment proposals in PlanWise and "fix" these for a certain number of time periods. This makes it possible to enforce treatments that you consider mandatory. You can also evaluate differences in what the system consider as optimal management programs, and programs proposed by a planner. Read more about it in our help documentation (in Swedish only).

• A new result variable for minimum final felling age is called ForestData_MinFinalFellingAge (see help documentation chapter "Slutavverkning", sektion "Resultatvariabler"). It can, for example, be used in a report for total area of stands that have reached this age (using a condition such as ForestData.MeanAge >= ForestData_MinFinalFellingAge). It is also usable in optimization models, to keep track of the area of stands that have reached minimum final felling age (using a condition such as WITH age[i,j,p] >= minFinalFellingAge[i,j,p]...). Note: TreatmentUnit_MinFinalFellingAge has been available since long, but should now be replaced with ForestData_MinFinalFellingAge, since TreatmentUnit_MinFinalFellingAge only refers to the first period while ForestData_MinFinalFellingAge is recalculated in each time period. MinFinalFellingAge can change over time when using the climate model (it affects site index), and after final felling depending on regeneration species.

• A new input variable called "SI Management" (for "management site index") can be imported and used as input when the system determines Minimum Final Felling Age (according to the Swedish Forestry Act). Site index as determined from site factors (SIS) is still used as input in growth functions. Read more here: Slutavverkning och SI.

Other improvements

• When activating Breeding Effect, it will be assumed that seedlings with "high-genetic gain" are used (in Swedish: högförädlat plantmaterial).

Bug fixes

• In PlanWise, too few treatment programs were sometimes generated when activating Breeding Effect.

• Even if all control table settings have been identical, small growth differences have been obtained for separate data imports, even if the imported data file has been the same. This may cause some pedagogic problems when running a deterministic simulation. It is caused by a stochastic component in the damage simulation model for trees in young stands (plantations), in which a certain "index key" has been used as seed in the random number generation. This has been replaced with a parameter called RandomSeed in control table Production Model. If set to a value larger than 0, the value will be used as seed. If set to 0, a random seed will be used.

• An error when saving and loading a list of treatment units has been fixed (PlanWise and RegWise).

• Since version 1.9.0, no fertilization have been simulated in RegWise. This occured after adding a list of soil moisture classes where fertilization may be applied, but a silly mistake made the list faulty.

• Thinning algorithm LOEriksson did not result in correct thinning grades in stands with more than one sample plot. This has been fixed.

• In StandWise, and in PlanWise since version 1.9.0.3, a thinning could not be applied earlier than 15 years after fertilization, instead of 10 years after.

• A forest domain-condition using an interval with the In-operator, for example 50 <= MeanAge <= 60 is defined as MeanAge In 50:60, did not work. This has been fixed.

• When running the treatment program generator in PlanWise, parallellization is used, but there have been several reports on problems that have been caused by threading conflicts, noted when running large problems. Hopefully this problem is now solved.

Known issues

see Known Issues

More information

For more information see: https://arbetsplats.slu.se/sites/srh/heureka/Lists/Release%20notes/Default.aspx