Known issues

From GLOW Visualization
Revision as of 21:38, 24 June 2010 by Walter (talk | contribs) (add an issue)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search
Warning.pngAs is expected with pre-release software, there are bound to be some bugs. We will try our best to resolve them as quickly as possible. If your issue is not listed here, see the troubleshooting page.

ATI Radeon HD freezes on Inverted Radial Tree layout

Some newer ATI Radeon HD cards exhibit problems when choosing the "Inverted Radial Tree" layout. The problem causes spurious textures to be drawn, and may cause the GLOW user interface to "freeze" for seconds.

Workaround: If this problem happens, do not use the Inverted Radial Tree layout. Select another layout using the "layout" drop-down at the bottom of the plug-in. It may take some time for the interface to become responsive.

Duplicated leaf nodes

There is a known issue with spurious duplication of leaf nodes, if multiple inheritance exists higher up in the class hierarchy. Under a certain parent, a leaf node might appear multiple times.

Workaround: There is no workaround. When counting individuals, enable the display of labels for leaves in order to spot duplicates.

Switching ontologies in Protégé causes instability

From time to time, closing an ontology and opening a new ontology in Protégé causes graph drawing to stop. An error message may appear.

Workaround: Close Protégé before opening a new ontology.

FaCT++ returns empty results

When using FaCT++ as a reasoner, no OWL objects are returned, creating an empty graph.

Workaround: Use another reasoner, such as Pellet.

Modifier buttons cause spurious panning

Laptops may not have a middle/right mouse button which are used to perform zooming and rotation of the graph. Option and Command keys are modifiers that can be combined with a left-click to do zooming and rotation, but in this case, the graph pans simultaneously.

Workaround: Connect a mouse, or pan the graph back to its oroginal location using only the left mouse button, after it has been incorrectly moved.