Difference between revisions of "Test"
Jump to navigation
Jump to search
| Line 34: | Line 34: | ||
==Bug fixes == | ==Bug fixes == | ||
| − | * | + | *Fixed a problem that occured when importing a stand register with a minimal set of columns, not using a predefined stand regiter template but only relying on column names. |
| − | *Fixed memory leak that occurred when running large simulations with linked retention patches ( | + | *Fixed memory leak that occurred when running large simulations with linked retention patches (new functionality in version 1.9.4). |
| − | *In version 1.9.4, reports | + | *In version 1.9.4, an error occured when generating reports in RegWise. This was due to the moving of variable ForestDomain to the TreatmentUnit result category. This has been fixed. |
*Fixed problem when creating or removing reports located in the root folder for the report templates. | *Fixed problem when creating or removing reports located in the root folder for the report templates. | ||
| Line 44: | Line 44: | ||
*Conditions in reports and forest domain with 'not equal to' or 'not in' did not work with missing values (null values), this have been fixed. | *Conditions in reports and forest domain with 'not equal to' or 'not in' did not work with missing values (null values), this have been fixed. | ||
| − | *Additional indices (for example | + | *Additional indices (for example an additional period index) in optimization models are now stored correctly. |
| − | *Simulation of fertilization caused memory leak after introducing | + | *Simulation of fertilization caused memory leak after introducing the possibility in version 1.9.4 to include multiple pricelists. This has been fixed. |
*A problem with an internal numbering of control categories has been fixed that sometimes caused the TPG to crash with an out of bounds exception. This sometimes occurred after adding or removing control categories in a certain order. | *A problem with an internal numbering of control categories has been fixed that sometimes caused the TPG to crash with an out of bounds exception. This sometimes occurred after adding or removing control categories in a certain order. | ||
| − | *Recently fertilized stand are by default not eligible for harvesting until 10 years have passed since fertilization. The TPG would under certain condtions | + | *Recently fertilized stand are by default not eligible for harvesting until 10 years have passed since fertilization. The TPG would under certain condtions fail to generate a treatment program for such stands, more specifically if a stand was old and the user had set Final Felling Period Min to 0. This has been fixed, so that Min Final Felling Period Min is adjusted to a value large enough to allow at least one final felling period. |
| − | * | + | *A period index error in the report builder has been fixed, that occured when simultaneously simulating fertilization and enforcing user defined treatment proposals. |
| + | |||
| + | *If Treatment Proposals have been imported in PlanWise, they are now activated and run by default. In previous versions, you had to activate them by setting Apply Proposals = True in control table Treatment Program Generator). Also, option LetTpgDecide is set to True by default, meaning that treatments are simulated from period 0 for stands that have no treatment proposals. In previous versions, LetTpgDecide was False by default, meaning that no treatments were simulated for these stands during the first 10 years when Apply Proposals was set to true. | ||
| − | |||
*Fixed problem when using variables from TretmentUnit result category in report conditions, for example ForetData.MeanAge >= TreatmentUnit.MinFinalFellingAge would raise an exception error. | *Fixed problem when using variables from TretmentUnit result category in report conditions, for example ForetData.MeanAge >= TreatmentUnit.MinFinalFellingAge would raise an exception error. | ||
==New chapter in help documentation== | ==New chapter in help documentation== | ||