Difference between revisions of "Test"

From Heureka Wiki
Jump to navigation Jump to search
 
(24 intermediate revisions by the same user not shown)
Line 1: Line 1:
Version 1.9.5
+
Version 1.9.6
 
{{Languages}}
 
{{Languages}}
 
<!--
 
<!--
 
[[Category:Release]]
 
[[Category:Release]]
[[Release date::2012-02-06]]  
+
[[Release date::2013-03-11]]  
 
-->
 
-->
 
 
==Summary==
 
==Summary==
*Several bugs have been discovered and fixed that affected the new functionality for handling retention patches introduced in version 1.9.4.
+
This release note describes changes since version 1.9.5.0. The changes have partly been released already in patches 1.9.5.1 to 1.9.5.4, but for these patches no newsletters have been published.
 
 
*Some bugs have been discovered and fixed that affected the handling of user defined treatment proposals.
 
 
 
*Additional site feature variables can be imported from FMPP-data (Indelningspaketet).  
 
 
 
*Forest fuel extraction result variables are more detailed and divided into species and tree fractions.
 
 
 
*The help documentation has been extended to describe the Treatment Program Generator (TPG) in PlanWise, and the difference between the Strategic TPG and the Tactical TPG.
 
  
 
==New features ==
 
==New features ==
*The number of tree objects (i.e. number of caliper trees) in a stand has a great impact on computation times and memory usage when running large scale simulations in PlanWise (and in RegWise depending on what data is used). For example, the time to generate treatment programs for a stand may vary from a few seconds to half a minute or even more, depending on the number of sample plots and the number of caliper trees on each plot. In some situations, execution time can be unacceptably long, and to overcome this a tree data aggregation algorithm has been implemented. If activated, this algorithm aggregates tree records stored in the database into fewer "runtime" tree objects by grouping the trees into diameter classes. The aggregation is activated under menu Settings > Performance. For each sample plot, species group, diameter class, and tree type (tree, sapling, overstorey tree, retention tree, etc.), a new "class tree" is thus created which substitutes the trees in the class. The diameter class width is 1 cm by default, and tests show that growth projections are affected only marginally by the aggregation. The diameter of the class tree is the quadratic mean diameter of the trees in the class.
+
*A mailing function has been implemented which makes it easier to share a project with someone else. The function compresses the current project into a zip file and lets you send it by e-mail. There is also a decompressing function which lets you unpack a zipped project. You find this functionality under the File-menu (Arkiv-menyn).
 
+
*Price correction for timber log length is now possible. All users should update their pricelists accordingly. It is possible to enter different corrections for different diameter classes and species, but, for technical reasons, not for different quality classes. When adding price corrections, make sure that the butt log and middle log can be cut up to 5.5 m and 11 m tree height (see below).  
*Import of data from FMPP (Indelningspaketet) has been extended to handle extended versions of the file ytor.dat. CountyCode, VegetationType (Heureka type), LateralWater (rörligt markvatten), Bottom Field Layer, SoilTexture, and sample plot coordinates can be imported this way. These data must be added to the file ytor..  
+
[[File:LogLength.PNG]]
 
+
*The default priclist has been changed. It it based on Mellanskog Stockholm (no. LV 31-51, Jan 2013). Length corrections are included. (http://www.mellanskog.se/Global/Virkesprislistor/S%C3%A5gt%20norr%20M%C3%A4lar%20V%C3%A4rmland%20LV%2031-51.pdf).
*Forest fuel extraction results have until now been represented as total harvest residues and stumps. These are now divided into species groups and tree fractions. The new result variables are placed in the result category Financial Data, as "Biofuel Extracted".
 
 
 
*Since the previous release (1.9.4), retention patches can be imported as their own stands, and be linked to their "parent" stands within which they are located. This functionality is now available in the tree list importer as well (the tree list importer is a more detailed version of the stand register importer, allowing you to import plot and caliper tree data http://heureka.ad.slu.se/help/index.html?importera_bestand_med_provytor.htm).
 
  
 
==Improvements ==
 
==Improvements ==
*Selection of treatment units from file, in the area control in PlanWise and RegWise, is now much faster, and will work on very large datasets.  
+
*A sufficient criteria for a stand to be classified as a conifer stand has been 500 conifer trees per ha. The reason for this is that there may be many decidous trees during the young phase of a conifer stand, so even if the dominant species may be deciduous, the main crop species is usually the conifer species and a larger proprtion of the deciduous trees removed in cleanings and thinnings. This is important since the dominant species is used when setting minimum final felling age (if the regeneration species is unknown, see below), and the minimum final felling age is usually shorter for deciduous species than for conifers. The problem with this criteria is that stands have almost always been classified as conifer stands, because 500 conifer trees is a quite low threshold value. The criteria has therefore been increased to 800 conifer tres/ha, and also been made available as a user parameter in control table TreatmentModel. The parameter is called Conifer Criteria.
<!--
+
*importing stand register data.
*When importing stand register data, overstorey layers with a layer code do no need to follow directly after the main row for the stand. -->
+
*A new result variable called RegenerationSpecies is available in result category ForestData. It corresponds to variable RegenerationSpecies in result category Treatments, but is available for each period (Treatments.RegenerationSpecies is only available for the period if and when a regeneration treatment is applied). ForestData.RegenerationSpecies tells you what species has been used to the RegenerationSpecies and DominantSpecies are usually the same, but not always.
 
+
*When applying forest fuel thinning, utilization grades for different tree fractions have been determined by parameter settings Utilization in control table TreatmentModel. This is intended for harvest residue extraction, and not forest fuel thinning. Therefore parameters Forest Fuel Thinning Utilization have been added to control utilization grades.
*Map legends (teckenförklaringar) for integer variables have been modified to work more consistently.
+
*The user-defined utilization grade for needles and branches in the top of a tree have until now been multiplied with the utilization grade of the top. This has been changed so that the utilization grades for needles and branches refer to the proportion of needles and branches available in the part of the trees referred to. This means that the utilization grades are consistent for all tree fractions. So, if the utilization grade for the top is 90 %, and 90 % of the needles in the top are utilized, you set Utilization.Top = 90 % and Utilization.Needles Top = 90 %. To do this in previous versions, you should have set Utilization.Needles Top = 100 %.
 
+
*Data in categories SiteData and StandObjectData are now available in TPG-result view.
*The activation of user defined treatment proposals in simulations are hopefully more intuitive. If treatment proposals have been imported in PlanWise, they are now activated and run by default. To ignore them, you only have to uncheck the check box when running the TPG. In previous versions, you also had to activate them by setting Apply Proposals = True in control table Treatment Program Generator. Also, the control table parameter "Treatment Proposals Missing" is set to LetTpgDecide by default, meaning that treatments are simulated from period 0 for stands that have no treatment proposals. In previous versions, it was set to NoActivity by default, meaning that no treatments were simulated for these stands during the first 10 years when Apply Proposals was set to true.
+
.) are now displayed when there is a problem with an optimization model or solver.
 +
*Stand register data files (csv-format) can have different column delimiters depending on language settings. The importer now attempts to detect what delimiter is used. If not successful, the user is asked for the delimiter symbol.
  
 
==Bug fixes ==
 
==Bug fixes ==
*Setting "PlantCostArea" in control table Cost and Revenues is now used if the cost per plant ("SaplingPlantCost") is set to 0 for the planted species.
+
* When importing a pricelist with the same identifier as a pricelist already present in the project, it was not saved. This has been fixed.
 
+
*In timber pricelists, there is a column called Waste (vrak). The copy and paste function did not include this column. This has been fixed.
*Sowing of pine in PlanWise is working again.
+
*Resetting Utilization Grade values to default values in control table TreatmentModel now works as expected.
 
+
*The default value for plant density in RegenerationSettings dialog in control table ProductionModel is now properly saved.  
*Retention of nature conservation trees in RegWise is now working, it has never been activated in RegWise.
+
*For biofuel extraction, a model is used to calculate how much of the needle biomass that is located in the (cut) tree top. For this calculation, the length of the tree top is used, which is obtained by multiplying with tree top proportion. Instead of using proportion of length, proportion of volume was used, which may have overestimated the amount of needles extracted. This has been fixed.
 
+
*Reports using conditions with StandObjectData-variables now work as expected.
*Fixed a problem that occured when importing a stand register with a minimal set of columns (i.e. when not using a predefined stand regiter template but only relying on column names).  
+
*The amount of biomass extracted (result category Financial Value) depends on the user-defined utilization grades for different tree fractions (see above), as set in control table TreatmentModel. This control table was mistakenly read from Default Control Category instead of the applied control category. This has been fixed.
 
+
*The result variable DominantSpecies is used to determine minimum final felling age. When simulating a plantation, DominantSpecies  was set to the site index species instead of the main species. For example, a regenerated oak stand would obtain pine as DominantSpecies, despite that the planted species per se was correct. This has led to too long final felling ages in plantations with deciduous trees or contorta as main species. This problem was unfortunately  introduced in version 1.9.4 but has now been solved.
*Fixed memory leak that occurred when running large simulations with linked retention patches (new functionality in version 1.9.4).
 
 
 
*In version 1.9.4, an error occured when generating reports in RegWise. This was due to the moving of variable ForestDomain to the TreatmentUnit result category. This has been fixed.
 
 
 
*Fixed problem when creating or removing reports located in the root folder for the report templates.
 
 
 
*Conditions in reports and forest domain using operator of typ 'not equal to' or 'not in' did not work with missing values (null values). This have been fixed.
 
 
 
*Additional indices (for example an additional period index) in optimization models are now stored correctly.
 
 
 
*Simulation of fertilization caused memory leak after introducing the possibility in version 1.9.4 to include multiple pricelists. This has been fixed.  
 
 
 
*A problem with an internal numbering of control categories that sometimes caused the TPG to crash with an out of bounds exception has been fixed. The problem could occur after adding or removing control categories in a certain order.  
 
 
 
*Recently fertilized stands are by default not eligible for harvesting until 10 years have passed since fertilization. The TPG would under certain conditions fail to generate a treatment program for such stands, more specifically if a stand was old and the user had set Final Felling Period Min to 0. This has been fixed, so that Min Final Felling Period Min is adjusted to a value large enough to allow at least one final felling period.
 
 
 
*A period index error in the report builder has been fixed, that occured when simultaneously simulating fertilization and enforcing user defined treatment proposals.  
 
 
 
*Fixed a problem when using variables from TretmentUnit result category in report conditions, for example ForetData.MeanAge >= TreatmentUnit.MinFinalFellingAge would raise an exception error.
 
 
 
==New chapter in help documentation==
 
has been extended with a comprehensive description of the treatment program generator (TPG), and the difference between the strategic and the tactical TPG.
 

Latest revision as of 17:38, 11 March 2013