Version 1.9.5 - Revision history

Lnilsson at 10:47, 9 February 2021

2021-02-09T10:47:52Z

Peder at 14:27, 14 November 2017

2017-11-14T14:27:57Z

Peder at 15:20, 18 January 2014

2014-01-18T15:20:57Z

Peder: /* New features */

2013-05-29T06:58:51Z

New features

Peder: /* New chapter in help documentation */

2013-05-29T06:58:34Z

New chapter in help documentation

Peder at 14:22, 13 February 2013

2013-02-13T14:22:06Z

Peder: /* New features */

2013-02-13T07:35:31Z

New features

Peder: /* New features */

2013-02-13T07:34:54Z

New features

2013-02-13T07:34:17Z

Created page with 'Version 1.9.5 {{Languages}} Category:Release Release date::2012-02-13 ==Summary== *If vegetation type is missing, site index and soil moisture are used to set a default�?�'

New page

@@ Line 5: / Line 5: @@
 ==Summary==
-*If vegetation type is missing, site index and soil moisture are used to set a default value for it.
+*If vegetation type is missing, site index and soil moisture are used to set a default value for it. [[VegetationType_from_site_features|Read more]]
 *Several bugs have been discovered and fixed that affected the new functionality for handling retention patches introduced in version 1.9.4.
 *Some bugs have been discovered and fixed that affected the handling of user defined treatment proposals.
@@ Line 13: / Line 13: @@
 ==New features ==
-*If vegetation type has been missing, the program has set it to the most common vegetation type in Sweden, which is bilberry (blåbärsttyp). A more refined lookup table has now been implemented, using site index and soil moisture class as lookup variables if vegetation type is missing.
+*If vegetation type has been missing, the program has set it to the most common vegetation type in Sweden, which is bilberry (blåbärsttyp). A more refined [[VegetationType_from_site_features|lookup table]] has now been implemented, using site index and soil moisture class as lookup variables if vegetation type is missing.
 *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.

@@ Line 1: / Line 1: @@
 Version 1.9.5
 {{Languages}}
-[[Category:Release]]
+[[Category:ReleaseNotes archive]]
 [[newsdate::2013-02-13]]

@@ Line 2: / Line 2: @@
 {{Languages}}
 [[Category:Release]]
-[[Release date::2013-02-13]]
+[[newsdate::2013-02-13]]
 ==Summary==

@@ Line 16: / Line 16: @@
 *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.
-*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.dat in a specific order, as a "tail" to the original records of type �??posttyp 1�?�.
+*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.dat in a specific order, as a "tail" to the original records of type "posttyp 1".
 *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".

@@ Line 16: / Line 16: @@
 *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.
-*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.dat in a specific order, as a "tail" to the original records of type ??posttyp ?.
+*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.dat in a specific order, as a "tail" to the original records of type �??posttyp 1�?�.
 *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".
@@ Line 63: / Line 63: @@
 ==New chapter in help documentation==
-Chapter Skapa skötselprogram i (http://heureka.ad.slu.se/help/index.html?skapa_skotselprog_planvis.htm) has been extended with a comprehensive description of the treatment program generator (TPG), and the difference between the strategic and the tactical TPG.
+Chapter "Skapa skötselprogram i PlanVise" (http://heureka.ad.slu.se/help/index.html?skapa_skotselprog_planvis.htm) has been extended with a comprehensive description of the treatment program generator (TPG), and the difference between the strategic and the tactical TPG.