Version 2.12: Difference between revisions

From Heureka Wiki
Jump to navigation Jump to search
No edit summary
 
(6 intermediate revisions by the same user not shown)
Line 8: Line 8:
*Version 2.12 contains new functonality in RegWise to allow for the simulation of land use changes. Until now the only land use supported has been "Productive forestland". A new control table called "LandUse" has been added to the Domain Settings-type control category (RegWise only). The immediate use of this functionality is for the national greenhouse gas report.
*Version 2.12 contains new functonality in RegWise to allow for the simulation of land use changes. Until now the only land use supported has been "Productive forestland". A new control table called "LandUse" has been added to the Domain Settings-type control category (RegWise only). The immediate use of this functionality is for the national greenhouse gas report.
*Non-productive forestland is now supported as land-use type, and new growth functions have been developed for this (Kenneth Nyström 2018).
*Non-productive forestland is now supported as land-use type, and new growth functions have 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 be handled as a distinct assortment and assumed to be 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 log cull. Pulpwood can be downgraded to fuelwood and log cull. 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).
*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 be handled as a distinct assortment and assumed to be put in a separate log pile 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 log cull. Pulpwood can be downgraded to fuelwood and log cull. 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).
*What was previously called Waste (vrak) has been renamed to Log Cull. It refers to logs downgraded at the industry but has until now been accounted for only as a decrease in saw timber revenue. Now the volume is explicitly reported, from downgrading of timber and pulpwood. This means that the timber and pulpwood volumes will be smaller in the new version (unless the waste proportion is zero).  
*What was previously called Waste (vrak) has been renamed to Log Cull. It refers to logs downgraded at the industry but has until now been accounted for only as a decrease in saw timber revenue. Now the volume is explicitly reported, from downgrading of timber and pulpwood. This means that the timber and pulpwood volumes will be smaller in the new version (unless the waste proportion is zero).  
*The default price for Log Cull (previously called Waste) has been changed from 80 to 0 SEK per volume unit.
*The default price for Log Cull (previously called Waste) has been changed from 80 to 0 SEK per volume unit.
Line 15: Line 15:
*All random seeds that were previously located in different control tables have been replaced with one single seed that you enter when you start a simulation.  
*All random seeds that were previously located in different control tables have been replaced with one single seed that you enter when you start a simulation.  
*The HeurekaAPI has several fixes.
*The HeurekaAPI has several fixes.
*Understorey cleaning introduced in version 2.11 has new default parameters: 500 instead of 800 stems/ha with diameter < 7 cm is enough to trigger an understorey cleaning before a thinning. Also, 200 instead of 500 stems/ha of these are kept as default. All understorey stems in strip roads are removed if understorey cleaning is conducted. No percentage of the proportion to remove is entered, instead the number of residual stems determine how many understorey trees that are removed.
*Understorey cleaning introduced in version 2.11 has new default parameters: 500 instead of 800 stems/ha with diameter < 7 cm is enough to trigger an understorey cleaning before a thinning. Also, 200 instead of 500 stems/ha are kept as default. All understorey stems in strip roads are removed if understorey cleaning is conducted. No percentage of the proportion to remove is entered, instead the number of residual stems determine how many understorey trees that are removed.
*The minimum thinning diameter was increased from 4 cm to 8 cm in version 2.11. This may lead to unintended thinnings from above in young stands, if no understorey cleaning is conducted. The minimum diameter has been increased to 7 cm. This is also the new diameter limit for understorey trees.  
*The minimum thinning diameter was increased from 4 cm to 8 cm in version 2.11. This may lead to unintended thinnings from above in young stands, if no understorey cleaning is conducted. The minimum diameter has been increased to 7 cm. This is also the new diameter limit for understorey trees.  
   
   
Line 22: Line 22:
<endFeed />
<endFeed />


<!--
==Updates for version 2.12==
==Updates for version 2.12==
<startFeed />
<startFeed />
====Version 2.12.1====
====Version 2.12.1====
<feedDate>2018-11-xx</feedDate>
The default pricelist file embedded in the installation was corrupt.
<feedDate>2018-11-28</feedDate>
<endFeed />
 
<startFeed />
====Version 2.12.2====
Minor bug fixes.
<feedDate>2019-01-07</feedDate>
<endFeed />
 
<startFeed />
====Version 2.12.3====
Bug fixes, including fix of import error introduced in 2.12.2
<feedDate>2019-02-01</feedDate>
<endFeed />
<endFeed />
-->


<startFeed />
<startFeed />
==New result variables==
==New result variables==
<feedDate>2018-11-27</feedDate>
<feedDate>2018-11-27</feedDate>
Line 40: Line 52:
| style="background:#f0f0f0;width:12%;"|'''Result Group'''
| style="background:#f0f0f0;width:12%;"|'''Result Group'''
| style="background:#f0f0f0;width:10%;;"|'''Unit'''
| style="background:#f0f0f0;width:10%;;"|'''Unit'''
| style="background:#f0f0f0;width:56%;;"|'''Description'''
| style="background:#f0f0f0;width:56%;;"|'''Comment'''
|-style = "vertical-align: top;"
|-style = "vertical-align: top;"
| <div id="Fuelwood Volume"></div>Fuelwood Volume || Financial Value || m<sup>3</sup>fub/ha ||  ...   
| <div id="Fuelwood Volume"></div>Fuelwood Volume || Financial Value || m<sup>3</sup>fub/ha ||  ...   
Line 51: Line 63:
|-style = "vertical-align: top;"
|-style = "vertical-align: top;"
| <div id="LandUse></div>Land Use Data|| Land Use Data ||  || New result group (RegWise only) with several new result variables
| <div id="LandUse></div>Land Use Data|| Land Use Data ||  || New result group (RegWise only) with several new result variables
|-style = "vertical-align: top;"
| Decay Class per Species|| Dead Wood Data || m<sup>3</sup>/ha || Volume per decay class and species group (pine, spruce, other)
|}
|}
A detailed list of the assortment variables are described [{{HeurekaHelpLink}}sortiment.htm in a new Help section].  
A detailed list of the assortment variables are described [{{HeurekaHelpLink}}sortiment.htm in a new Help section].  
Line 64: Line 78:


<startFeed />
<startFeed />
==Bug fixes and other changes==
==Bug fixes and other changes==
<feedDate>2018-11-27</feedDate>
<feedDate>2018-11-27</feedDate>
Line 70: Line 85:
status = resolved, closed
status = resolved, closed
color = false
color = false
fixed_in_version = 2.12.0, 2.12.1, 2.12.2
fixed_in_version = 2.12.0, 2.12.1, 2.12.2, 2.12.3
orderby = fixed_in_version desc, category desc
orderby = fixed_in_version desc, category desc
show = id,category,severity,summary,fixed_in_version,resolution
show = id,category,severity,summary,fixed_in_version,resolution
summary_as_comment = true
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.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.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.  

Latest revision as of 13:58, 5 March 2019

2018-11-27

<startFeed />

Summary

  • Version 2.12 contains new functonality in RegWise to allow for the simulation of land use changes. Until now the only land use supported has been "Productive forestland". A new control table called "LandUse" has been added to the Domain Settings-type control category (RegWise only). The immediate use of this functionality is for the national greenhouse gas report.
  • Non-productive forestland is now supported as land-use type, and new growth functions have 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 be handled as a distinct assortment and assumed to be put in a separate log pile 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 log cull. Pulpwood can be downgraded to fuelwood and log cull. 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).
  • What was previously called Waste (vrak) has been renamed to Log Cull. It refers to logs downgraded at the industry but has until now been accounted for only as a decrease in saw timber revenue. Now the volume is explicitly reported, from downgrading of timber and pulpwood. This means that the timber and pulpwood volumes will be smaller in the new version (unless the waste proportion is zero).
  • The default price for Log Cull (previously called Waste) has been changed from 80 to 0 SEK per volume unit.
  • Harvesting and forwarding costs in storm-felled stands can be adjusted with time consumption adjustment factors (RegWise).
  • The Dead Wood result variables now also include decay class distribution per species class.
  • All random seeds that were previously located in different control tables have been replaced with one single seed that you enter when you start a simulation.
  • The HeurekaAPI has several fixes.
  • Understorey cleaning introduced in version 2.11 has new default parameters: 500 instead of 800 stems/ha with diameter < 7 cm is enough to trigger an understorey cleaning before a thinning. Also, 200 instead of 500 stems/ha are kept as default. All understorey stems in strip roads are removed if understorey cleaning is conducted. No percentage of the proportion to remove is entered, instead the number of residual stems determine how many understorey trees that are removed.
  • The minimum thinning diameter was increased from 4 cm to 8 cm in version 2.11. This may lead to unintended thinnings from above in young stands, if no understorey cleaning is conducted. The minimum diameter has been increased to 7 cm. This is also the new diameter limit for understorey trees.


<feedDate>2018-11-27</feedDate> <endFeed />

Updates for version 2.12

<startFeed />

Version 2.12.1

The default pricelist file embedded in the installation was corrupt. <feedDate>2018-11-28</feedDate> <endFeed />

<startFeed />

Version 2.12.2

Minor bug fixes. <feedDate>2019-01-07</feedDate> <endFeed />

<startFeed />

Version 2.12.3

Bug fixes, including fix of import error introduced in 2.12.2 <feedDate>2019-02-01</feedDate> <endFeed />

<startFeed />

New result variables

<feedDate>2018-11-27</feedDate> <endFeed /> The following result variables have been added.

Name Result Group Unit Comment
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
Decay Class per Species Dead Wood Data m3/ha Volume per decay class and species group (pine, spruce, other)

A detailed list of the assortment variables are described in a new Help section.


<startFeed />

Bug fixes and other changes

<feedDate>2018-11-27</feedDate> <endFeed /> <mantis> status = resolved, closed color = false fixed_in_version = 2.12.0, 2.12.1, 2.12.2, 2.12.3 orderby = fixed_in_version desc, category desc show = id,category,severity,summary,fixed_in_version,resolution summary_as_comment = true 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>