Known Issues: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 6: | Line 6: | ||
== THIS PAGE IS UNDER CONSTRUCTION == | == THIS PAGE IS UNDER CONSTRUCTION == | ||
The Heuerka team is constantly working on improving the performance and user experience of the applications. The currently known issues are listed here: | The Heuerka team is constantly working on improving the performance and user experience of the applications. The currently known issues are listed here: | ||
Do you know about a bug or issue not listed here? [[Bug Tracking|Report a bug]] | |||
''Do you know about a bug or issue not listed here? [[Bug Tracking|Report a bug]]'' | |||
<startFeed /> | <startFeed /> | ||
| Line 26: | Line 27: | ||
<mantis> | <mantis> | ||
resolution = open | resolution = open | ||
status = new, assigned, acknowledged, confirmed | |||
version = 2.23.0, 2.23.0.1, 2.23.0.2 | |||
severity = major | severity = major | ||
show = id,category,summary | show = id,category,summary, version, status | ||
</mantis> | </mantis> | ||
<endFeed /> | <endFeed /> | ||
Revision as of 11:01, 27 November 2024
THIS PAGE IS UNDER CONSTRUCTION
The Heuerka team is constantly working on improving the performance and user experience of the applications. The currently known issues are listed here:
Do you know about a bug or issue not listed here? Report a bug <startFeed />
Version 2.23
Known problems
- Generating reports with large dataset and several columns can lead to "Time out expired" from the connected SQL Server. If so, try one of the following:
- Try to set "Query Wait" in SQl Server Management Studio (for the database server) to a larger value (http://msdn.microsoft.com/en-us/library/ms189539(v=sql.105).aspx).
- A workaround is to export data from Optimization Results > Details, and use pivot tables in Excel. Also avoid selecting more than one simulation or plan at a time when creating reports.
- Another work-around is to use SQL Server Profiler (not available in Express version) to get the SQL Query and run the query in SQL Server Management Studio.
- When a stand leaves the young stand phase and transfers into established phase, there are is often a "glitch" in annual volume increment. Also, trees with a diameter less than 4 cm are not transferred, because ingrowth functions predicts the ingrowth of trees with into the 4-cm class. This may give inconsistent results when studying young stand management.
- It is possible that dead wood "stays to long" in the final decay class.
- The simulation of tree lists from stand data currently only handles even-aged stands, with bell-shaped diameter distributions. Distribution parameters for inverse J-shaped distributions (as tyoical for uneven-aged stands) are currently not available.
Details from bugtracker
<mantis> resolution = open status = new, assigned, acknowledged, confirmed version = 2.23.0, 2.23.0.1, 2.23.0.2 severity = major show = id,category,summary, version, status </mantis>
<endFeed />