Difference between revisions of "Version 1.2"

From Heureka Wiki
Jump to navigation Jump to search
(Created page with '{{Languages}} Category:Release Release date::2011-02-16')
 
Line 2: Line 2:
 
[[Category:Release]]
 
[[Category:Release]]
 
[[Release date::2011-02-16]]
 
[[Release date::2011-02-16]]
 +
 +
{| {{table}}
 +
| align="left" width = "10" style="background:#f0f0f0;"|'''Release version'''
 +
| align="left" width = "10"  style="background:#f0f0f0;"|'''Task type'''
 +
| align="left" width = "60"  style="background:#f0f0f0;"|'''Description'''
 +
| align="left" width = "20"  style="background:#f0f0f0;"|'''Application'''
 +
|-
 +
| 1.2.0||Bugfix||Problem:  For some users en error occurs when build opimization problem in PlanWise because \"ZIMPL exe cannot be found\".. Solution: Fixed by including absolute file path to ZIMPL binary file.||All
 +
|-
 +
| 1.2.0||Bugfix||Problem: Stands imported from stand register data with mean height < 0.5 m obtains no initial state. Solution: Problem was that regeneration year had not been set in stand register file. Added support to handle such missing data, so that if regeneration year is missing, but there are plants/stems and age > 0, then regenration year is set to inventory year - stand age + 2 (+2 for assumed plant age when planting) ||PlanStart
 +
|-
 +
| 1.2.0||Bugfix||Problem: DominantSpecies in young stands varies from period to period. Solution: In young stands (\"sapling plots\") is determined by stem density instead of basal area. Of determined by basal area, a spruce plantation will often be classified as a deciduous stand because of fast growth of birch. This will lead to erronuous final felling age for the spruce stand.||All
 +
|-
 +
| 1.2.0||Bugfix||Problem: Planted beech is not growing. Solution: Problem was that wrong type av height function was applied for beech, which is now corrected.||All
 +
|-
 +
| 1.2.0||Bugfix||Problem: Values for overstorey trees are not updated after treatment. Fixed.||Common
 +
|-
 +
| 1.2.0||Bugfix||Conditions with typed variables (such as Species Code, Soil Moisture Code etc.) in Forest Domain Builder did not work when selecting multiple values. This has been fixed.||All
 +
|-
 +
| 1.2.0||Bugfix||In StandWise 3D-view, deciduous trees other than birch were visualized as pines. We still have no picture for other deciduous trees than birch, but birch pcitures are now used for all deciduous trees.||StandWise
 +
|-
 +
| 1.2.0||Bugfix||A control table called Species Classes was possible to select as part of a control category in RegWise and PlanWise, but lead to an exception error. This has been fixed, the control table is not possible to select anymore.||PlanWise
 +
|-
 +
| 1.2.0||Bugfix||Problem: Sometimes an error \"Object reference not set to an instance of an object.\" occurred when changing project, which has been fixed.||PlanWise
 +
|-
 +
| 1.2.0||Bugfix||Problem: \"OutOfMemoryException\" when running Treatment Program Generator (TPG) in PlanWise for large datasets. Solution: There is still a limitation for how large datasets can be run, but some code optimization has been done to prevent this problem to occur as far as possible. We have succesfully run more than 20000 treatment units.\'||PlanWise, RegWise
 +
|-
 +
| 1.2.0||Bugfix||Initial soil carbon storage was erroneous due to a unit error and should be 10 times larger. Also, funtion for spruce was mistakenly used for pine when calculating carbon in  debris from tree logs. These errors have been fixed||All
 +
|-
 +
| 1.2.0||Bugfix||When importing data from Stand Register, soil moisture code was not stored but default value used instead. This mean that soil moisture has been set to mesic. This error has been fixed.||All
 +
|-
 +
| 1.2.0||Bugfix||The mortality model for trees in young stands has been faulty, so that mortality was too high. This has been fixed. ||
 +
|-
 +
| 1.2.0||Bugfix||Problem: Calculation of net present values in StandWise fails due to null referencing (\"Object reference not set to an instance of an object\"). Solution: Fixed.||StandWise
 +
|-
 +
| 1.2.0||Bugfix||Problem: Error when using function \"Last periods with treatments\" in StandWise. Solution: This problem occured after version 1.1 but has now been fixed.||StandWise
 +
|-
 +
| 1.2.0||Bugfix||Problem: When editing conditions with coded variables (such as Species or Vegetation Type), and multiple values have been selected, an error occurs. The problem occured when running projects created in versions before 1.1, but has now been fixed. ||PlanWise
 +
|-
 +
| 1.2.0||Improvement||Year (relative from start year 0), is displayed in tables and graphs (x-axis).||PlanWise, RegWise
 +
|-
 +
| 1.2.0||Improvement||TreatmentUnit data can displayed as part of the simulation results.||RegWise
 +
|-
 +
| 1.2.0||Improvement||Aliases for columns in reports: You can now give names (aliases) to columns/variables in reports created with the Report Builder.||PlanWise, RegWise
 +
|-
 +
| 1.2.0||Improvement||Problem: On some PC:s, the prerequisite Visual C++ librarires is installed each time PlanWise is updated, even if VC++ libraries is already installed. This requires administrator\'s access Solution: The libraries files are now inclued as part of the application and not handled as a prerequisite. This means that administrators privilegies is not needed (only for .NET 4 framework which is a one-time installation).||PlanWise
 +
|-
 +
| 1.2.0||New feature||An infeasibility finder report is added to the optimization output. This feature helps in identifying what causes a certain model to be feasible, in case no feasible solution is found. Only available for CPLEX.||PlanWise
 +
|-
 +
|
 +
|}

Revision as of 16:13, 17 February 2011

2011-02-16

Release version Task type Description Application
1.2.0 Bugfix Problem: For some users en error occurs when build opimization problem in PlanWise because \"ZIMPL exe cannot be found\".. Solution: Fixed by including absolute file path to ZIMPL binary file. All
1.2.0 Bugfix Problem: Stands imported from stand register data with mean height < 0.5 m obtains no initial state. Solution: Problem was that regeneration year had not been set in stand register file. Added support to handle such missing data, so that if regeneration year is missing, but there are plants/stems and age > 0, then regenration year is set to inventory year - stand age + 2 (+2 for assumed plant age when planting) PlanStart
1.2.0 Bugfix Problem: DominantSpecies in young stands varies from period to period. Solution: In young stands (\"sapling plots\") is determined by stem density instead of basal area. Of determined by basal area, a spruce plantation will often be classified as a deciduous stand because of fast growth of birch. This will lead to erronuous final felling age for the spruce stand. All
1.2.0 Bugfix Problem: Planted beech is not growing. Solution: Problem was that wrong type av height function was applied for beech, which is now corrected. All
1.2.0 Bugfix Problem: Values for overstorey trees are not updated after treatment. Fixed. Common
1.2.0 Bugfix Conditions with typed variables (such as Species Code, Soil Moisture Code etc.) in Forest Domain Builder did not work when selecting multiple values. This has been fixed. All
1.2.0 Bugfix In StandWise 3D-view, deciduous trees other than birch were visualized as pines. We still have no picture for other deciduous trees than birch, but birch pcitures are now used for all deciduous trees. StandWise
1.2.0 Bugfix A control table called Species Classes was possible to select as part of a control category in RegWise and PlanWise, but lead to an exception error. This has been fixed, the control table is not possible to select anymore. PlanWise
1.2.0 Bugfix Problem: Sometimes an error \"Object reference not set to an instance of an object.\" occurred when changing project, which has been fixed. PlanWise
1.2.0 Bugfix Problem: \"OutOfMemoryException\" when running Treatment Program Generator (TPG) in PlanWise for large datasets. Solution: There is still a limitation for how large datasets can be run, but some code optimization has been done to prevent this problem to occur as far as possible. We have succesfully run more than 20000 treatment units.\' PlanWise, RegWise
1.2.0 Bugfix Initial soil carbon storage was erroneous due to a unit error and should be 10 times larger. Also, funtion for spruce was mistakenly used for pine when calculating carbon in debris from tree logs. These errors have been fixed All
1.2.0 Bugfix When importing data from Stand Register, soil moisture code was not stored but default value used instead. This mean that soil moisture has been set to mesic. This error has been fixed. All
1.2.0 Bugfix The mortality model for trees in young stands has been faulty, so that mortality was too high. This has been fixed.
1.2.0 Bugfix Problem: Calculation of net present values in StandWise fails due to null referencing (\"Object reference not set to an instance of an object\"). Solution: Fixed. StandWise
1.2.0 Bugfix Problem: Error when using function \"Last periods with treatments\" in StandWise. Solution: This problem occured after version 1.1 but has now been fixed. StandWise
1.2.0 Bugfix Problem: When editing conditions with coded variables (such as Species or Vegetation Type), and multiple values have been selected, an error occurs. The problem occured when running projects created in versions before 1.1, but has now been fixed. PlanWise
1.2.0 Improvement Year (relative from start year 0), is displayed in tables and graphs (x-axis). PlanWise, RegWise
1.2.0 Improvement TreatmentUnit data can displayed as part of the simulation results. RegWise
1.2.0 Improvement Aliases for columns in reports: You can now give names (aliases) to columns/variables in reports created with the Report Builder. PlanWise, RegWise
1.2.0 Improvement Problem: On some PC:s, the prerequisite Visual C++ librarires is installed each time PlanWise is updated, even if VC++ libraries is already installed. This requires administrator\'s access Solution: The libraries files are now inclued as part of the application and not handled as a prerequisite. This means that administrators privilegies is not needed (only for .NET 4 framework which is a one-time installation). PlanWise
1.2.0 New feature An infeasibility finder report is added to the optimization output. This feature helps in identifying what causes a certain model to be feasible, in case no feasible solution is found. Only available for CPLEX. PlanWise