Difference between revisions of "Test"
Jump to navigation
Jump to search
| Line 18: | Line 18: | ||
==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 stand may vary from | + | *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 | + | *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 |
| − | *Forest fuel extraction results have until now been represented as total harvest residues and stumps. | + | *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 | + | *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 == | ||