Version 1.9.2: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{Languages}} | {{Languages}} | ||
[[Category:Release]] | [[Category:Release]] | ||
[[Release date::2012-10- | [[Release date::2012-10-16]] | ||
(DRAFT) | (DRAFT) | ||
| Line 13: | Line 13: | ||
==New features== | ==New features== | ||
*Version 1.9.2 has an improved control for linking generation 1 and generation 2 control categories in a forest domain. With the new dialog, you can select explicitly what generation 2 category or categories to link to each generation 1 category. | *Version 1.9.2 has an improved control for linking generation 1 and generation 2 control categories in a forest domain. With the new dialog, you can select explicitly what generation 2 category or categories to link to each generation 1 category. See http://heureka.ad.slu.se/help/index.html?kontrollkategori.htm, section "Koppla kontrollkategori till skogsdomän i PlanVis". | ||
*Report templates can be installed from within PlanWise and RegWise. From the Table and Results tab, choose Download Default Templates. | |||
*Report templates can be installed from within PlanWise and RegWise. From the Table and Results tab, choose Download Default Templates (http://heureka.ad.slu.se/help/index.html?skapa_rapportmallar.htm (section "Hämta rapportmallar från SLU:s FTP-server)). | |||
==Bug fixes== | ==Bug fixes== | ||
*In a treatment unit (stand) with several sample plots (using FMPP data), in which some plot was bare land but the other plots established forest, the treatment program generator could give wrong results when Thinning Decision Level was set to PlotLevel. | *In a treatment unit (stand) with several sample plots (using FMPP data), in which some plot was bare land but the other plots established forest, the treatment program generator could give wrong results when Thinning Decision Level was set to PlotLevel. | ||
*Trees with a diameter dbh < Min Diameter in Final Fellings (control table Treatment Model), have been ignored, but they were supposed to be part of the soil carbon input pool as harvest residues. This has been fixed. Note that in clear cutting, thinning grade is reported as 100 %, unless nature conservation trees or seed trees are retained, without consideration to if small trees are actually not cut. | *Trees with a diameter dbh < Min Diameter in Final Fellings (control table Treatment Model), have been ignored, but they were supposed to be part of the soil carbon input pool as harvest residues. This has been fixed. Note that in clear cutting, thinning grade is reported as 100 %, unless nature conservation trees or seed trees are retained, without consideration to if small trees are actually not cut. | ||
<!--As a consequence, the thinning grade in clear cuts may be less than 100 %, and in StandWise where state variables directly after treatment can be displayed, you will see that there are some stems left if Min Diameter in Final Fellings is large enough. However, the volume after clear cutting is set to 0, in order to get growth values correct (they could be negative otherwise since small trees disappear after clearcut). (Note that clear cutting is not the same final felling method as final felling with seed trees or shelterwood). Another problem was that trees�?�--> | <!--As a consequence, the thinning grade in clear cuts may be less than 100 %, and in StandWise where state variables directly after treatment can be displayed, you will see that there are some stems left if Min Diameter in Final Fellings is large enough. However, the volume after clear cutting is set to 0, in order to get growth values correct (they could be negative otherwise since small trees disappear after clearcut). (Note that clear cutting is not the same final felling method as final felling with seed trees or shelterwood). Another problem was that trees�?�--> | ||
<!--Note: If you want to harvest trees with diameter (dbh) less than �??Min Diameter in Final Fellings�?� for extraction as harvest residues, you should set the minimum diameter to for example 5. Then these trees will be included in the cost calculation for the harvester, and also be available as extractable harvest residues. --> | <!--Note: If you want to harvest trees with diameter (dbh) less than �??Min Diameter in Final Fellings�?� for extraction as harvest residues, you should set the minimum diameter to for example 5. Then these trees will be included in the cost calculation for the harvester, and also be available as extractable harvest residues. --> | ||
* In reports of Treatment Data or Financial Data results (such as volume harvested), and with numeric-type conditions from Treatment Data (such as �??volume harvested where dgv of harvested trees is at least 20 cm�?�), wrong results were obtained (larger values with than without condition!). | * In reports of Treatment Data or Financial Data results (such as volume harvested), and with numeric-type conditions from Treatment Data (such as �??volume harvested where dgv of harvested trees is at least 20 cm�?�), wrong results were obtained (larger values with than without condition!). | ||
*Result types StandObjectData and TreatmentData were not available as condition variables in the report builder. This has been fixed. | *Result types StandObjectData and TreatmentData were not available as condition variables in the report builder. This has been fixed. | ||
*Minor edits have been made to cost functions for harvesting and forwarding, to take into account that trees can be cut for bio fuel instead of timber or pulpwood. If top diameter is changed to a larger value a larger proportion of a tree is available for bio fuel extraction (if this is activated), and forwarding cost should be adjusted accordingly, which is was not. A new result variable has been added under Financial Value, calls Stems Cut Timber & Pulp, for the number of trees which are at least partly cut into timber or pulpwood logs. The difference between TreatmentData.StemsHarvested and FinancialData.StemsCutPulpAndTimber is the number of small trees left after final felling (trees in with dbh < minimum diameter). | *Minor edits have been made to cost functions for harvesting and forwarding, to take into account that trees can be cut for bio fuel instead of timber or pulpwood. If top diameter is changed to a larger value a larger proportion of a tree is available for bio fuel extraction (if this is activated), and forwarding cost should be adjusted accordingly, which is was not. A new result variable has been added under Financial Value, calls Stems Cut Timber & Pulp, for the number of trees which are at least partly cut into timber or pulpwood logs. The difference between TreatmentData.StemsHarvested and FinancialData.StemsCutPulpAndTimber is the number of small trees left after final felling (trees in with dbh < minimum diameter). | ||
*Saving a map view as a jpeg-image now works as it should. | *Saving a map view as a jpeg-image now works as it should. | ||
*Treatment Proposal handling introduced in 1.9.1 had some problem which have now been solved. Especially, planting immediately and regeneration did not work as expected. | *Treatment Proposal handling introduced in 1.9.1 had some problem which have now been solved. Especially, planting immediately and regeneration did not work as expected. | ||
*Swedish language was not available when installing with MSI packages. | *Swedish language was not available when installing with MSI packages. | ||
*In StandWise, you could not select Final Felling with Seed Trees (fröträd). | *In StandWise, you could not select Final Felling with Seed Trees (fröträd). | ||
*A problem when calculating net present value in StandWise that could lead to an infinite loop has been fixed. | *A problem when calculating net present value in StandWise that could lead to an infinite loop has been fixed. | ||
==Other improvements that are not really bugs== | ==Other improvements that are not really bugs== | ||
*When running a simulation on different computers, slightly different results were obtained if the data import had been done locally (to each computer�??s own SQL Server database). This was due to a random component invoked when calculating occurrence of damages on sapling that affect growth. Unique identity keys created when importing data were there used as random seeds, hence why results differed. The problem has been fixed by a fixed seed for the random generator as default (this seed can be set in control table Production Model). | *When running a simulation on different computers, slightly different results were obtained if the data import had been done locally (to each computer�??s own SQL Server database). This was due to a random component invoked when calculating occurrence of damages on sapling that affect growth. Unique identity keys created when importing data were there used as random seeds, hence why results differed. The problem has been fixed by a fixed seed for the random generator as default (this seed can be set in control table Production Model). | ||
==Known Issues== | |||