... | ... | @@ -93,8 +93,23 @@ __Correct Axioms__ are axioms that are assumed to be correct. Such axioms have t |
|
|
##### Modifying The Input Ontology
|
|
|
**Note**: When loading the *Koala ontology* the debugger assumes all logical axioms as *Possibly Faulty Axioms*. Thus all 42 logical axioms are *Possibly Faulty* axioms. As long as the Debugging Session has not been started, the user can modify the two lists by clicking on the icons ![possibly_Faulty](/uploads/d152029365ddc44a0946c68e3ece74b7/possibly_Faulty.PNG) and ![correct](/uploads/433f214d1523b2ec6c3ba2ef66aa83f9/correct.PNG) to assume axioms to be either _possibly faulty_ or _correct_, respectively.
|
|
|
|
|
|
#### Queries View
|
|
|
|
|
|
##### Queries
|
|
|
|
|
|
The leftmost part shows us the **Queries** view - the section the user will interact with the debugger the most during a 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 the debugging session again. ![start](/uploads/b93fbef049714ac66a819709aa3015e8/start.PNG) ![restart](/uploads/6d9ee6c92befc0981fe52c24e583928c/restart.PNG)
|
|
|
- The **Stop**-button stops a running debugging session. As long as there is no running session this button is disabled (greyed out) ![stop](/uploads/9a5f30421341fa4ff1a2f94437f6d52d/stop.PNG)
|
|
|
- The **Submit**-button is used to **answer a query**. This button is greyed out as long as a session has not been started and - once started - as long as the user has not yet classified any axiom in the query as entailed or non-entailed. ![submit](/uploads/06b7a61d7a3d6f8fac58bc4ba7a31730/submit.PNG)
|
|
|
|
|
|
##### Possible Ontology Repairs
|
|
|
|
|
|
The **Possible Ontology Repairs** below the Queries shows the user possible candidate axioms as soon as we start a new debugging session.
|
|
|
|
|
|
#### Test Cases View
|
|
|
In the mid section the so called **acquired** and **saved test cases** of the current debugging session are shown.
|
|
|
The mid section shows us the **acquired** and **saved test cases** of the current debugging session.
|
|
|
|
|
|
##### Acquired Test Cases
|
|
|
**Acquired Test Cases** are axioms that have already been answered by the user in previous queries. They are either categorized as _Entailed Test Cases_ when they have been classified by the user as correct statements in the ontology or as _Non Entailed Testcases_ when they must not be entailed in (these statements are not correct) the ontology according to the user's answer.
|
... | ... | @@ -105,6 +120,8 @@ In the image below we see an example with three Entailed Testcases and one Non E |
|
|
|
|
|
*The Acquired Test Cases show us the answers - the yellow background color highlights an inferred axiom*
|
|
|
|
|
|
**Note**: when you restart or stop a debugging session that already contains given answers (i.e. Acquired Test Cases) then user will be asked to save these given answers in order to continue the session later with the already given answers.
|
|
|
|
|
|
##### Saved Test Cases
|
|
|
Next to the set of Acquired Test Cases you have the **Saved Test Cases** showing either manually added or previously saved acquired test cases.
|
|
|
|
... | ... | @@ -117,15 +134,6 @@ Note that the manual addition of test cases is not possible during a running deb |
|
|
*This screenshot shows a handcrafted non entailed test case next to two saved entailed test cases from a previous debugging session*
|
|
|
|
|
|
|
|
|
#### Queries View
|
|
|
|
|
|
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:
|
|
|
- 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. ![start](/uploads/b93fbef049714ac66a819709aa3015e8/start.PNG) ![restart](/uploads/6d9ee6c92befc0981fe52c24e583928c/restart.PNG)
|
|
|
- The **Stop**-button stops a running debugging session. As long as there is no running session this button is disabled (greyed out) ![stop](/uploads/9a5f30421341fa4ff1a2f94437f6d52d/stop.PNG)
|
|
|
- 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. ![submit](/uploads/06b7a61d7a3d6f8fac58bc4ba7a31730/submit.PNG)
|
|
|
- **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.
|
|
|
|
|
|
### Step 5: Starting a new Debugging Session
|
|
|
|
... | ... | |