This plug-in is still in development! Very probably you may experience faulty and unexpected behaviour such as deadlocks, exceptions etc. You may report any bugs you experience in our [feedback](http://isbi.aau.at/ontodebug/feedback). We will try to fix them as soon as possible. Thank you!
**This plug-in is still in development!**
* Very probably you may experience faulty and unexpected behaviour such as deadlocks, exceptions etc. You may report any bugs you experience in our [feedback](http://isbi.aau.at/ontodebug/feedback). We will try to fix them as soon as possible.
* There are still many features missing that we plan to implement ([see the list of open issues](https://git-ainf.aau.at/interactive-KB-debugging/debugger/issues)). If you have ideas for features that would be nice to have we would be pleased if you [send us your request](http://isbi.aau.at/ontodebug/feedback).
# Installation
# Installation
...
@@ -93,9 +97,10 @@ Below the set of Acquired Test Cases the **Original Test Cases** are shown that
...
@@ -93,9 +97,10 @@ Below the set of Acquired Test Cases the **Original Test Cases** are shown that
Finally, the leftmost part shows us the most important information during a debugging session.
Finally, the leftmost part shows us the most important information during a debugging session.
In the **Queries** view we have 3 buttons that control the debugging session:
In the **Queries** view we have 3 buttons that control the debugging session:
- Once an ontology is loaded we have to **Start** a new debugging session to start the interaction with the user. Once a debugging session has been started, the start-button changes to **Restart**. This enables the user to start again the debugging session. 
- Once an ontology is loaded we have to **Start** a new debugging session to start the interaction with the user. Once a debugging session has been started, the start-button changes to **Restart**. This enables the user to start the debugging session again. 
- The **Stop**-button stops a running debugging session. As long there is no running session this button is disabled (greyed out) 
- The **Stop**-button stops a running debugging session. As long as there is no running session this button is disabled (greyed out) 
- The **Submit**-button is used to **answer a query**. This button is greyed out as long as a session has not been started or - once started - as long as the user has not yet classified any axiom in the query as entailed or non-entailed. 
- The **Submit**-button is used to **answer a query**. This button is greyed out as long as a session has not been started or - once started - as long as the user has not yet classified any axiom in the query as entailed or non-entailed. 
-**Note**: when you restart or stop a debugging session then all given answers are lost! For a future version of the debugger it is planned to let the user save the dialog in order to continue later.
