Version 2.16
Version 2.16
2020-07-01
Summary
- Version 2.16 contains bug fixes, improvements of existing functionality (mostly UI-related), and one new feature.
- The new feature allows you to include complex expressions in reports (PlanWise and RegWise). With this, you can create report variable conditions that are functions of other variables. This feature resembles the Sql Query-builder tools often found in GIS-applications.
Bug fixes and improvements
| Id | Category | Severity | Summary | Fixed_in_version | Resolution | Comment |
|---|---|---|---|---|---|---|
| 0000373 | Report generator | minor | Report conditions are not applied when grouping on forest domain and showing the results in the same report | 2.16.4 | fixed | Report conditions are not applied when grouping on forest domain and showing the results in the same report |
| 0000377 | Project handling | major | Unable to open StandWise projects with a result database having a simulation with a planning horizon of 0. | 2.16.4 | fixed | Unable to open StandWise projects with a result database having a simulation with a planning horizon of 0. |
| 0000369 | General | feature | Verify that high stumps do not end up in the soil model. | 2.16.4 | fixed | Verify that high stumps do not end up in the soil model. |
| 0000380 | General | feature | Test report internal activity | 2.16.4 | fixed | Test report internal activity |
| 0000374 | General | major | Last result variable selection is not loaded when opening a new simulation dialog | 2.16.4 | fixed | Last result variable selection is not loaded when opening a new simulation dialog |
| 0000375 | Data import | minor | SiteIndex = 0 accepted although data should be used for tree simulation | 2.16.4 | fixed | SiteIndex = 0 accepted although data should be used for tree simulation |
| 0000376 | Data import | feature | Importing a stand register of a sapling plot that calculates the height to be > 7m causes the import to halt | 2.16.4 | fixed | Importing a stand register of a sapling plot that calculates the height to be > 7m causes the import to halt |
| 0000378 | Data import | minor | Unable to import stand registers when splitting NC areas and have left an AreaLevel field empty. | 2.16.4 | fixed | Unable to import stand registers when splitting NC areas and have left an AreaLevel field empty. |
| 0000371 | Data import | feature | Jag kan inte importera NC area som egna bestånd | 2.16.4 | fixed | Jag kan inte importera NC area som egna bestånd |
| 0000370 | Other | feature | Certain result variables are not available | 2.16.2 | fixed | Certain result variables are not available |
| 0000363 | General | minor | Previously selected result properties are not loaded upon starting another simulation | 2.16.2 | open | Previously selected result properties are not loaded upon starting another simulation |
| 0000357 | RegWise simulation | major | Det sker slutavverkningar i NC ytor i RegVis | 2.16.1 | open | Det sker slutavverkningar i NC ytor i RegVis |
| 0000362 | RegWise simulation | major | No selection felling in NC areas | 2.16.1 | fixed | No selection felling in NC areas |
| 0000354 | Other | major | Database error message 'DF__Treatment__Inven__03F0984C' is not a constraint' | 2.16.1 | not a bug | Database error message 'DF__Treatment__Inven__03F0984C' is not a constraint' |
| 0000358 | General | minor | Det går inte att visa userdefined under Initial State - Details | 2.16.1 | fixed | Det går inte att visa userdefined under Initial State - Details |
| 0000355 | Data import | major | Insufficient error message when importing stand register file | 2.16.1 | reopened | Insufficient error message when importing stand register file |
| 0000280 | TPG | feature | Setting Min Final Felling Period to a large number causes an exception in TPG | 2.16.0 | fixed | Setting Min Final Felling Period to a large number causes an exception in TPG |
| 0000351 | TPG | block | Timeout expection and high memory consumption when running PlanWise TPG | 2.16.0 | fixed | Timeout expection and high memory consumption when running PlanWise TPG |
| 0000352 | TPG | block | TPG-exception Incorrect syntax near 'stringvalue' where stringvalue is a text string in a forest domain condition | 2.16.0 | fixed | TPG-exception Incorrect syntax near 'stringvalue' where stringvalue is a text string in a forest domain condition |
| 0000344 | TPG | major | Treatment proposal "Remove Overstorey" applied in wrong period and also removes saplings | 2.16.0 | fixed | Removal of overstorey propsals are now performed in the period closest to the defined year |
| 0000353 | TPG | feature | Problem when adding control table (production model) to control category | 2.16.0 | not a bug | Problem when adding control table (production model) to control category |
| 0000345 | TPG | major | TPG runtime exception after adding ProductionModel control table to a control category | 2.16.0 | fixed | TPG runtime exception after adding ProductionModel control table to a control category |
| 0000346 | TPG | major | Wrong breeding effect settings used after removing redundant control table | 2.16.0 | fixed | Production.cs always used the ProductionModelControlTable's parent ControlCategory for construction of (plugin) models, meaning the TreatmentModelControlTable supplied to plugins were the TMCT from the ProductionModelControlTable's parent ControlCategory. For built-in models, this only applied to SaplingHeightGrowthElfving, which gets its breeding settings from the TreatmentModelControlTable. |
| 0000349 | Report generator | minor | Results from HabitatModels can not be shown in reports until project restart | 2.16.0 | fixed | Results from HabitatModels can not be shown in reports until project restart |
| 0000343 | Report generator | feature | Arithmetic expressions for report conditions | 2.16.0 | fixed | Arithmetic expressions for report conditions |
| 0000342 | RegWise simulation | major | RegVis creates no NC-areas | 2.16.0 | fixed | NC-areas management programs were not saved correctly in RegWise |
| 0000334 | Other | minor | Long standid-names are not displayed in window Optimization Result Details | 2.16.0 | fixed | Long standid-names are not displayed in window Optimization Result Details |
| 0000338 | Other | minor | Interfacet för optimering, textrutor för små, text syns inte. | 2.16.0 | fixed | Interfacet för optimering, textrutor för små, text syns inte. |
| 0000332 | Other | feature | Custom user defined column names should be displayed if applicable, instead of generic "UserDefined" | 2.16.0 | fixed | Custom user defined column names should be displayed if applicable, instead of generic "UserDefined" |
| 0000337 | Optimization | minor | Saving an optimization model with Opening Size constraints will corrupt the model | 2.16.0 | fixed | Saving an optimization model with Opening Size constraints will corrupt the model |
| 0000330 | Optimization | minor | Exception when viewing DiameterClassCuttingData results without Treatment column | 2.16.0 | fixed | Exception when viewing DiameterClassCuttingData results without Treatment column |
| 0000333 | Optimization | crash | Cloning a set or parameter crashes the program | 2.16.0 | fixed | Cloning a set or parameter crashes the program |
| 0000347 | Data import | minor | Unable to import stand register where AreaLevel2 is empty. | 2.16.0 | fixed | Linking of retention patches to parent stands failed if AreaLevel2 and AreaLevel3 were missing. |
| 0000350 | Data import | minor | Incorrect row number indicated when there is an error during stand register import | 2.16.0 | fixed | Incorrect row number indicated when there is an error during stand register import |
| 0000329 | Data import | major | Bristfälligt felmeddelande vid import av denna registerfil | 2.16.0 | fixed | Wrong array was updated when program corrected DiameterType in input data |