Version 2.9: Difference between revisions
| Line 20: | Line 20: | ||
<mantis> | <mantis> | ||
status = resolved, closed | status = resolved, closed | ||
color = false | |||
fixed_in_version = 2.8.1, 2.9.0 | fixed_in_version = 2.8.1, 2.9.0 | ||
orderby = Severity desc, Category asc | orderby = Severity desc, Category asc | ||
Revision as of 08:31, 13 November 2017
<startFeed />
Maintenance release
Version 2.9.0 is a maintenance release with bug fixes and impovements. It does not include new features. <feedDate>2017-11-14</feedDate> <endFeed />
<startFeed /> <feedDate>2017-11-14</feedDate>
Change log
<endFeed /> <mantis> status = resolved, closed color = false fixed_in_version = 2.8.1, 2.9.0 orderby = Severity desc, Category asc show = id,category,severity,summary,fixed_in_version,resolution comment.150 = If user has declined to update an old price list when prompted and runs a simulation, the error message in inconclusive. comment.147 = The selection of variables to display in different tables are now specific for each table view. comment.144 = The form for selecting and configuring alternative values in PlanEval had been made more intuitive. comment.127 = A participant in a PlanEval-project can ask the system to restore a forgotten password. comment.148 = Fixed broken links after recent server migration (version 2.8) comment.130 = Cosmetic fix comment.146 = Fixed updating av preview comment.151 = When creating a new optimization model the area[i]-paramter will refer to variable TreatmentUnit.AdjustedAreaFactor. This is adjusted for the numbe rof inventory years, and is the same as AreaFactor except when using NFI-data plots. In that case, the area factors are asjusted for the number of inventory years selected. comment.145 = A used was led to believe that more than one simulation could be selected as input to an optimization problem, which is not possible. comment.149 = Fixed implementation to include multi-line intersection type between adjacent polygons when calculating common border length. comment.124 = Fixed threading problem in map view that caused a false out of memory exception. comment.120 = Cross-thread exception fixed comment.140 = Map export function would throw a KeyNotFoundException when trying to export the map for an optimization that does not contain all treatment units in the selected area. comment.131 = Added help documention for PlanEval administration (installation of PlanEvalWeb and how to add online user) comment.152 = Minskning i höjdutveckling i tallplantering blir knappt märkbar när man anger parametern "Moose Browsing Damage (test)" till t ex 20%. Parametern är som namnet antyder avsedd för test och finns i kontrolltabellen Production Model. comment.137 = (StandWise) When planting with breeded plants in period 0, the result variable BreedingLevel was still "None". comment.141 = Could not remove if to may rows. Now remove in chunks of 500 rows. comment.133 = Unit label "SEK/ha" was missing. comment.142 = Problem occurred when creating a forest domain by selecting treatment units from the map. comment.143 = Sometimes when creating a new forest domain, an exception would be thrown when trying to add a tree to a TreeCollection </mantis>
New documentation
<feedDate>2017-11-14</feedDate>
Help section for PlanEval projekt admininstrators
<endFeed /> https://www.heurekaslu.se/help/index.html?planeval_administration.htm
<feedDate>2017-11-14</feedDate>
Help for installing PlanEvalWeb on your own server
PlanEvalWeb <endFeed />