Difference between revisions of "Version 2.3.2"
(Created page with "<noinclude> Version 2.3.2 (Minor upgrades 2.3.1-2.3.2) {{Languages|Version 2.3.2}} Category:Release newsdate::2015-10-15 </noinclude> <startFeed /...") |
|||
| Line 7: | Line 7: | ||
<startFeed /> | <startFeed /> | ||
| − | == | + | ==Versions 2.3.1 and 2.3.2 are minor updates of version 2.3.0== |
<feedDate>2015-10-15</feedDate> | <feedDate>2015-10-15</feedDate> | ||
Versions 2.3.1 and 2.3.2 are minor updates of version 2.3.0 and contains the following fixes: | Versions 2.3.1 and 2.3.2 are minor updates of version 2.3.0 and contains the following fixes: | ||
| Line 13: | Line 13: | ||
<startFeed /> | <startFeed /> | ||
| − | + | ==Added feature: Optional rounding of result variable== | |
You can now choose if result variable values should be rounded. You do this in results view (Settings -> Language/Interface -> Round decimals) | You can now choose if result variable values should be rounded. You do this in results view (Settings -> Language/Interface -> Round decimals) | ||
<feedDate>2015-10-15</feedDate> | <feedDate>2015-10-15</feedDate> | ||
| Line 19: | Line 19: | ||
<startFeed /> | <startFeed /> | ||
| − | + | ==Improvement: Faster forest domain assignment when only the default domain is present or active== | |
<feedDate>2015-10-15</feedDate> | <feedDate>2015-10-15</feedDate> | ||
<endFeed /> | <endFeed /> | ||
<startFeed /> | <startFeed /> | ||
| − | + | ==Improvement: Handle missing values in optimization model == | |
An optimization model may contain a parameter that is linked to a Heureka result variable that does not necessarily has a value. This means that value may be null (=missing), which may lead to errors if the variable is part of, for example, an expression (in a constraint or accounting variable). To handle this, you can now set a default value for parameters that are linked to a Heureka result variable. Note that for defined parameters ("Formula parameter") this has already been possible by adding for example "default 0;" at the end of the definition. | An optimization model may contain a parameter that is linked to a Heureka result variable that does not necessarily has a value. This means that value may be null (=missing), which may lead to errors if the variable is part of, for example, an expression (in a constraint or accounting variable). To handle this, you can now set a default value for parameters that are linked to a Heureka result variable. Note that for defined parameters ("Formula parameter") this has already been possible by adding for example "default 0;" at the end of the definition. | ||
<feedDate>2015-10-15</feedDate> | <feedDate>2015-10-15</feedDate> | ||
| Line 31: | Line 31: | ||
<startFeed /> | <startFeed /> | ||
| − | + | ==Bug fix: Intial state graph for Volume per species showed wrong species == | |
In the Intial State window in PlanWise and RegWise there is a diagram called Volume per species. This showed wrong species. This has been fixed. | In the Intial State window in PlanWise and RegWise there is a diagram called Volume per species. This showed wrong species. This has been fixed. | ||
<feedDate>2015-10-15</feedDate> | <feedDate>2015-10-15</feedDate> | ||
| Line 37: | Line 37: | ||
<feedDate>2015-10-15</feedDate> | <feedDate>2015-10-15</feedDate> | ||
| − | + | ==Bug fix: Forest domain properties re-enabled == | |
If you select a forest domain, a property window has shown some metadata for the forest domain, such as the number of treatment units in the forest domain and the total productive area. This function has been broken since version 2.1 was relased but has now been re-enabled. | If you select a forest domain, a property window has shown some metadata for the forest domain, such as the number of treatment units in the forest domain and the total productive area. This function has been broken since version 2.1 was relased but has now been re-enabled. | ||
<feedDate>2015-10-15</feedDate> | <feedDate>2015-10-15</feedDate> | ||
| Line 43: | Line 43: | ||
<startFeed /> | <startFeed /> | ||
| − | + | ==Bug fix: Exception for stand with 100 % impediment == | |
If a treatment unit was imported from a stand register but contained 100 % impediment, the forest domain evaluation would lead to un unhandled exception in PlanWise and RegWise. This has now been fixed. However, stands woth 100% impediment should not be imported, since they are not included in the simulations. | If a treatment unit was imported from a stand register but contained 100 % impediment, the forest domain evaluation would lead to un unhandled exception in PlanWise and RegWise. This has now been fixed. However, stands woth 100% impediment should not be imported, since they are not included in the simulations. | ||
<feedDate>2015-10-15</feedDate> | <feedDate>2015-10-15</feedDate> | ||
<endFeed /> | <endFeed /> | ||
Revision as of 08:29, 23 November 2015
Version 2.3.2 (Minor upgrades 2.3.1-2.3.2)
 |
Languages: |
2015-10-15
Versions 2.3.1 and 2.3.2 are minor updates of version 2.3.0
Versions 2.3.1 and 2.3.2 are minor updates of version 2.3.0 and contains the following fixes:
Added feature: Optional rounding of result variable
You can now choose if result variable values should be rounded. You do this in results view (Settings -> Language/Interface -> Round decimals)
Improvement: Faster forest domain assignment when only the default domain is present or active
Improvement: Handle missing values in optimization model
An optimization model may contain a parameter that is linked to a Heureka result variable that does not necessarily has a value. This means that value may be null (=missing), which may lead to errors if the variable is part of, for example, an expression (in a constraint or accounting variable). To handle this, you can now set a default value for parameters that are linked to a Heureka result variable. Note that for defined parameters ("Formula parameter") this has already been possible by adding for example "default 0;" at the end of the definition.
Bug fix: Intial state graph for Volume per species showed wrong species
In the Intial State window in PlanWise and RegWise there is a diagram called Volume per species. This showed wrong species. This has been fixed.
Bug fix: Forest domain properties re-enabled
If you select a forest domain, a property window has shown some metadata for the forest domain, such as the number of treatment units in the forest domain and the total productive area. This function has been broken since version 2.1 was relased but has now been re-enabled.
Bug fix: Exception for stand with 100 % impediment
If a treatment unit was imported from a stand register but contained 100 % impediment, the forest domain evaluation would lead to un unhandled exception in PlanWise and RegWise. This has now been fixed. However, stands woth 100% impediment should not be imported, since they are not included in the simulations.