Difference between revisions of "Version 2.16"

From Heureka Wiki
Jump to: navigation, search
Line 8: Line 8:
{{DISPLAYTITLE:Version 2.16}}
{{DISPLAYTITLE:Version 2.16}}
<endFeed />
<endFeed />
*Version 2.16 contains bug fixes, improvements of existing functionality (mostly UI-related), and one new feature.
*Version 2.16 contains bug fixes, improvements of existing functionality (mostly UI-related), and one new feature.
Line 15: Line 15:
<startFeed />
<startFeed />
====Bug fixes and improvements====
====Bug fixes and improvements====
<endFeed />
<endFeed />

Latest revision as of 22:34, 6 July 2020

Version 2.16



  • 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
0000370 Other feature Certain result variables are not available 2.16.2 fixed Several result variables, for example TreatmentUnit.Description and TreatmentUnit.AreaFactor, are not available for selection i result views.


StandObjectData StandId StandObjectData Register StandObjectData AreaLevel2 TreatmentUnit TreatmentUnitType reatmentUnit AreaFactor

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, även om har ställt in att dessa ska lämnas orörd i Nature Conservation Settings.
0000362 RegWise simulation major No selection felling in NC areas 2.16.1 fixed RegWise does not do any selection fellings in NC areas, even though I have chosen Retention Patches Treatment = Selection. The NC areas are left unmanaged instead. Newest version,
0000354 Other major Database error message 'DF__Treatment__Inven__03F0984C' is not a constraint' 2.16.1 not a bug Error message when opening an existing project created before version 2.16:

"Result database structure is invalid, check the result db connection. Reason: 'DF__Treatment__Inven__03F0984C' is not a constraint. Could not drop constraint. See previous errors."

Source: .Net SqlClient Data Provider


  vid System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
  vid System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
  vid System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
  vid System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async, Int32 timeout, Boolean asyncWrite)
  vid System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)
  vid System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
  vid Slu.Heureka.DomainLayer.ResultHandling.ResultDBUpgradeHandler.upgradeToVersion(String version)
  vid Slu.Heureka.DomainLayer.ResultHandling.ResultDBUpgradeHandler.UpgradeResultDatabase()
  vid Slu.Heureka.BaseLayer.HeurekaForms.ProgressForm.backgroundWorker1_DoWork(Object sender, DoWorkEventArgs e)
  vid System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
  vid System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
0000358 General minor Det går inte att visa userdefined under Initial State - Details 2.16.1 fixed Under Initial State - Details så försvinner allt när man selekterar en variabel från Stand Register Data - UserDefined.
0000355 Data import major Insufficient error message when importing stand register file 2.16.1 reopened Error message does not help the user to identify the problem:

Indatasträngen hade ett felaktigt format.

- at line 2
- at line 3
- at line 4

The problem in this case is the comment-kolumn (at the end of the file). The user should be informed what is the problem.

0000280 TPG feature Setting Min Final Felling Period to a large number causes an exception in TPG 2.16.0 fixed Ger felmeddelandet:

TPG Error for treatment unit 1 : Error occured when updating aggregated tree values in period 369 for prediction unit Slu.Heureka.DomainLayer.Forest.TreeCollection+AggregatedValues. Incorrect values: Mean Age Total

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
0000345 TPG major TPG runtime exception after adding ProductionModel control table to a control category 2.16.0 fixed "Object reference" exception when running TPG after adding Production Model to control category. Must close and reopen project to get rid of problem.
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.
0000351 TPG block Timeout expection and high memory consumption when running PlanWise TPG 2.16.0 fixed When running a relatively time-consuming TPG-simulation a time out expcetion occurs after several hours:

"TPG Error for treatment unit xxxx: Tidsgränsen för körning har upphört. Tidsgränsen uppnåddes innan åtgärden kunde slutföras, eller så svarar inte servern. The statement has been terminated."

0000352 TPG block TPG-exception Incorrect syntax near 'stringvalue' where stringvalue is a text string in a forest domain condition 2.16.0 fixed Felet uppstår i UpdateSimulationReport om man har med villkor i en skogsdomän som inkluderar textvärden och dessa textsträngar omges av enkla citationstecken, t ex

AreaLevel2 = 'Skifte1'. Felet uppstår inte om man skriver AreaLevel2 = Skifte1

Incorrect syntax near 'Mitt'

Stacktrace: ... vid Slu.Heureka.DomainLayer.ResultsHandling.ResultDb.UpdateSimulationReport(...)

0000353 TPG feature Problem when adding control table (production model) to control category 2.16.0 not a bug When adding a new control table (in this case production model) to a control category, I get an error when running the TPG. I could not attach a picture, but the error message states that "TPG Error for treatment unit 1110040_BZ_1 : object reference not set to an instance of an object." for several treatment units. The problem is not in the table settings (since I get the same error even when the settings in the production model table is all default)
0000343 Report generator feature Arithmetic expressions for report conditions 2.16.0 fixed Users want the ability to create more complex expressions for report conditions. The left hand side of an equality shall be able to hadnel multiple result variables and arithmetic expressions.
0000349 Report generator minor Results from HabitatModels can not be shown in reports until project restart 2.16.0 fixed After running HabitatModels, the project must be restarted in order for reports with HabitatModel references to work
0000342 RegWise simulation major RegVis creates no NC-areas 2.16.0 fixed NC-areas management programs were not saved correctly in RegWise
0000332 Other feature Custom user defined column names should be displayed if applicable, instead of generic "UserDefined" 2.16.0 fixed For user defined columns imported during stand register import, the user-specified column names should be visible when selecting variables, and when showing the results in the results grid. This is applicable if all treatment units come from the same stand register, and therefore share the same column names for all user defined variables.
0000334 Other minor Long standid-names are not displayed in window Optimization Result Details 2.16.0 fixed Två problem med långa standid.

-Om man har långa standid-namn (och därmed långa TreatmentUnit.Description) syns de inte i komboboxen i Optimization Results > Details. -Kolumnen Description har fast bredd, så samma problem där.

0000338 Other minor Interfacet för optimering, textrutor för små, text syns inte. 2.16.0 fixed Text visas inte i fönster för egenskap för variabel; textrutan (egenskapsrutan) klicka på raden Sets och klicka

sedan på symbolen ….

Se skärmdump i bifogad fil.

0000330 Optimization minor Exception when viewing DiameterClassCuttingData results without Treatment column 2.16.0 fixed Application throws an SQLException when viewing results including DiameterClassCuttingData when the result table does not include the Treatment column
0000333 Optimization crash Cloning a set or parameter crashes the program 2.16.0 fixed In optimization view, cloning a user created parameter or a variable crashes the application
0000337 Optimization minor Saving an optimization model with Opening Size constraints will corrupt the model 2.16.0 fixed A model saved with opening size constraint will throw an exception when being opened.
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
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 If there is an error in an overstorey or nature conservation layer, incorrect row number is reported