Differences

This shows you the differences between two versions of the page.

--- documentation:issues [12:03 05.08.2013] – [Report an issue] Walter
+++ documentation:issues [14:50 17.08.2021] (current) – Uncollapse Diego Jahn
@@ Line 1: / Line 1: @@
 ===== Known Issues =====
+==== Installation ====
-==== GUI ====
+=== Installation on Mac OSX ===
-++++ Added item does not appear (immediately) in Editor (tree view) |
+Please see the page on [[download:osx_10.8_users|troubleshooting for Mac]].
-As a workaround, click on the element in the Document view. This will force updating the tree view.
+==== Simulation ====
-++++
+=== ''Function'' gives erroneous values ===
-++++ Some jobs continue despite stopping multiple jobs in ''JobQueue'' |
+''Function''s have been reported to generate erroneous values in the following situation:
+  * ''Function'' is defined outside of ''System'' but used inside ''System'' (which is allowed) and
+  * OpenMP multithreading is used (i.e. Settings/Local/Threads per jobs > 1).
-If this occurs, you will need to remove the remaining jobs by selecting and removing them again.
+Work around:
+  * Drag ''Function'' inside the ''System''
+  * Or, use only single thread per job.
-++++
+==== Visualization ====
-++++ Morpheus GUI crashes when stopping multiple jobs in ''JobQueue'' |
+=== Gnuplot says "unknown or ambiguous terminal type" ===
-++++
+Morpheus depends on [[http://www.gnuplot.info|Gnuplot]] version 4.4. Please update [[http://www.gnuplot.info|Gnuplot]]. \\ \\
-==== Simulator ====
+In many cases, this error is due to the fact that the ''PDF'' and ''PNG'' terminals depend on ''libcairo''. As a workaround, one can use another terminal such as ''SVG'' or ''JPG''.
-++++ Gnuplot says "unknown or ambiguous terminal type" |
+=== Gnuplotter on-screen output shows flickering ===
-Morpheus depends on [[http://www.gnuplot.info|Gnuplot]] version 4.4. Please update [[http://www.gnuplot.info|Gnuplot]]. \\ \\
+Some gnuplot terminals, such as Aquaterm in Mac OSX, are relatively slow and may show flickering when run under ''interactive'' mode.
-In many cases, this error is due to the fact that the ''PDF'' and ''PNG'' terminals depend on ''libcairo''. As a workaround, one can use another terminal such as ''SVG'' or ''JPG''.
+As a workaround, do one of the following:
+  * In ''interactive'' mode: Use the screen terminal ''X11'' instead of ''aqua''.
+  * In ''local'' mode: Use a file terminal such as ''png'' and ''pdf''.
-++++
+==== Report an issue ====
-++++ GUI crash upon resizing onscreen gnuplot terminal |
+=== Found a bug? Send us a report. ===
-++++
-++++ Gnuplotter on-screen output shows flickering |
+If you experience reproducable crashes in a situation that is not covered here, please send us a [[joern.starruss@tu-dresden.de|bug report]]. \\
-Some gnuplot terminals, such as Aquaterm in Mac OSX, are relatively slow and may show flickering when run under ''interactive'' mode.
+In the bug report, include as much information as possible, such as: \\
+  - How to reproduce the bug
+  - XML model that produced the error (if applicable)
+  - Morpheus version/revision (see ''Settings -> Local -> Check Simulation -> Test'')
+  - Your operating system
+  - Log file of the debugger (''gdb.log'')
+==== GUI ====
+=== Added item does not appear in Editor (tree view) ===
+As a workaround, click on the element in the Document view. This will force updating the tree view.
+=== Drag/dropping items in Editor mixes up subitems ===
+As a workaround, click on the element in the Document view. This will force updating the tree view.
+=== Some jobs continue despite stopping multiple jobs in ''JobQueue'' ===
+If this occurs, you will need to remove the remaining jobs by selecting and removing them again.
+=== Simulation state [SnapShot].xml.gz cannot be restored (under Windows) ===
-As a workaround, you can let the gnuplot output be written to file by running the simulation in ''local'' mode.
+It has been reported that snapshots of simulation states, in compressed model files (''[SnapShot].xml.gz''), cannot be restored under Windows. This is most likely due to a corruption in file compression.
-++++
+A solution or workaround has yet to be found.