Difference between revisions of "Version 1.9.4"
Jump to navigation
Jump to search
| Line 13: | Line 13: | ||
*A new type of user defined set called Formula Set is available in the optimization model, as an alternative to an integer set. With Formula Set, you write the definition of the set yourself. A Formula Set can for example be a subset of another set. For example. {<p> in Periods with p < 10 } is a subset of Periods, where period index is less than 10. A definition of a Formula Set is enclosed by brackets { }; See Zimpl User's guide, page 10: http://zimpl.zib.de/download/zimpl.pdf. | *A new type of user defined set called Formula Set is available in the optimization model, as an alternative to an integer set. With Formula Set, you write the definition of the set yourself. A Formula Set can for example be a subset of another set. For example. {<p> in Periods with p < 10 } is a subset of Periods, where period index is less than 10. A definition of a Formula Set is enclosed by brackets { }; See Zimpl User's guide, page 10: http://zimpl.zib.de/download/zimpl.pdf. | ||
| − | *The following feature is for test purposes and is not "water-proof" yet! The mortality in retention patches within a main "parent" stand is usually increased during some years after final felling the main stand. The new functionality includes three new features: (1) possibility to define retention patches in the stand register import template as an alternative to let the program set aside "NC-areas", (2) a new parameter in control table Production Model for adjusting mortality rate in these patches, and (3) generation of alternative developments at the retention patches depending on whether the main stand has been clear cut or not. Previously, in partial set asides ( | + | *The following feature is for test purposes and is not "water-proof" yet! The mortality in retention patches within a main "parent" stand is usually increased during some years after final felling the main stand. The new functionality includes three new features: (1) possibility to define retention patches in the stand register import template as an alternative to let the program set aside "NC-areas", (2) a new parameter in control table Production Model for adjusting mortality rate in these patches, and (3) generation of alternative developments at the retention patches depending on whether the main stand has been clear cut or not. Previously, in retenetion patches, also called partial set asides ("NC-areas"), there was only one alternative generated, for unmanaged conditions. Now, one alternative is generated for each alternative simulated for the parent stand. In RegWise, there are no further changes needed, but in PlanWise you should add a constraint to the optimization models that enforced the correct alternative of the retention patch to be selected. This linkage is automatically added when creating a new optimization model (but inactivated). The linkage uses the fact the alternative index of a retention patch is the same as the index for the main stand. |
<!-- | <!-- | ||
Also, the retention patch always has an index +1 of the main stand. An optimization model called "Max nuvärde med två sorters jämnhetskrav ver 6" is included when installing PlanWise version 1.9.4. The stand register import template now includes a column for setting aside a retention patch within another stand. The retention patch is defined as a specific stand in the import template, in a separate row, and can therefore have another state than the parent stand that is belongs to. If and when the parent stand is clear cut, the retention patch stand will be subject to an increased mortality the first 10 years after the clear cut. | Also, the retention patch always has an index +1 of the main stand. An optimization model called "Max nuvärde med två sorters jämnhetskrav ver 6" is included when installing PlanWise version 1.9.4. The stand register import template now includes a column for setting aside a retention patch within another stand. The retention patch is defined as a specific stand in the import template, in a separate row, and can therefore have another state than the parent stand that is belongs to. If and when the parent stand is clear cut, the retention patch stand will be subject to an increased mortality the first 10 years after the clear cut. | ||
Revision as of 15:15, 20 December 2012
Version 1.9.4
 |
Languages: |
[[::Version 1.9.4|English]] |
Summary
Version 1.9.4 is a minor upgrade. It includes new functionality for taking into account that the tree mortality in retention patches is usually increased after final felling the stand which the retention patch is part of. The functionality is somewhat in a beta-version and will be tested in a specific research project.
New features
- A new control table parameter called "Include Contorta" in control table Treatment Model, section Fertilization, controls whether Lodgepole pine should be included when calculating conifer proportion or not,, and it is NOT included by default. The criteria "Min Conifer Proportion" says that at least 70 percent of the volume (excluding overstorey trees) must be conifers to do a fertilization. Until now, Lodgepole pine has been included, but from version 1.9.4 you must explictly change the parameter to True to include contorta.
- A new type of user defined set called Formula Set is available in the optimization model, as an alternative to an integer set. With Formula Set, you write the definition of the set yourself. A Formula Set can for example be a subset of another set. For example. {
in Periods with p < 10 } is a subset of Periods, where period index is less than 10. A definition of a Formula Set is enclosed by brackets { }; See Zimpl User's guide, page 10: http://zimpl.zib.de/download/zimpl.pdf.
- The following feature is for test purposes and is not "water-proof" yet! The mortality in retention patches within a main "parent" stand is usually increased during some years after final felling the main stand. The new functionality includes three new features: (1) possibility to define retention patches in the stand register import template as an alternative to let the program set aside "NC-areas", (2) a new parameter in control table Production Model for adjusting mortality rate in these patches, and (3) generation of alternative developments at the retention patches depending on whether the main stand has been clear cut or not. Previously, in retenetion patches, also called partial set asides ("NC-areas"), there was only one alternative generated, for unmanaged conditions. Now, one alternative is generated for each alternative simulated for the parent stand. In RegWise, there are no further changes needed, but in PlanWise you should add a constraint to the optimization models that enforced the correct alternative of the retention patch to be selected. This linkage is automatically added when creating a new optimization model (but inactivated). The linkage uses the fact the alternative index of a retention patch is the same as the index for the main stand.
Improvements
- The stand register import is now using column headings for variable mapping, instead of column order. This means that the data import is more robust to changes of the stand register template. However, you must supply correct column headings. Import files of version 1 will still work without column headings though. If the import routine finds a column with a column heading that has no match, it will try map into the first free UserDefinedVariable-column.
- The prognosis model for soil carbon and soil nitrogen (the Q-model) has several parameters. Two of these are Css and Alfa0 which are calculated by the model, or can be set by the user. These are now saved as result variables, in result table Carbon and Nitrogen.
- Result variables IsSetAside and ForestDomain have been moved to result table TreatmentUnit from AlternativeSummaryData and ForestDomainData, respectively. The reason for this is that a stand belongs the same forest domain throughout the planning horizon.
- Some parameters have been updated in the Q-model, according to a revised model description.
Bug fixes
- Report templates put in the report root directory can now be edited.
- Thinning history and fertilization history was not handled when using FMPP data. It was imported, but not taken care of. The fix affects growth (thinning and fertilization response was not included before the fix, and "locking" of harvest treatments recently fertilized stands.
- Renaming or adding an optimization set would sometimes raise an error, this has been fixed.
- It was sometimes not possible to select polygons. This has been fixed.
- Dominant Species of a TreatmentUnit will now remain the same for the entire generation. Previously, Dominant Species was recalculated for every period during growth. Now, instead of recalculating dominant species each period, the same dominant species will be used for the entire generation. If a regeneration species is available, it will be used as dominant species. The problem could lead to the final felling periods were based on a different dominant species, than the dominant species at
- When exporting result details to csv-files from column-view result view, semicolon separators between column labels were missing.
- Result variable AreaFactor is now visible in column-wise result view
- Fertilizations are applied in a way that could cause the fertilizations to change the control category history of a previous generation.