... | ... | @@ -6,7 +6,7 @@ |
|
|
|
|
|
* 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](http://isbi.aau.at/ontodebug/team) 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](http://isbi.aau.at/ontodebug/team) would be pleased if you [send us your request](http://isbi.aau.at/ontodebug/feedback).
|
|
|
* Please note that this plugin is a BETA ! **If you experience a faulty behaviour of your Protégé instance** (for example your Protege cannot start), it *may* be that this plugin causes the error. You can test this in the following way: delete the file called "*org.exquisite.protege-\<x.y.z>.BETA.jar*" in the "*plugins*" subdirectory of your Protege installation directory and restart Protégé (the *\<x.y.z>* represents the current version such as 0.1.3). In the same way you can also check other plugins if they are responsible for the fault. If this plugin is not causing the error you can later reinstall it.
|
|
|
* Please note that this plugin is a BETA ! **If you experience a faulty behaviour of your Protégé instance** (for example your Protege cannot start), it *may* be that this plugin causes the error. You can test this in the following way: delete the file called "*org.exquisite.protege-\<x.y.z>.BETA.jar*" in the "*plugins*" subdirectory of your Protege installation directory and restart Protégé (the *\<x.y.z>* represents the current version such as 0.1.4). In the same way you can also check other plugins if they are responsible for the fault. If this plugin is not causing the error you can later reinstall it.
|
|
|
|
|
|
<br><br>
|
|
|
# Installation
|
... | ... | @@ -14,7 +14,7 @@ |
|
|
These steps are necessary in order to run the plug-in:
|
|
|
* Download the latest version of Protégé Desktop from [http://protege.stanford.edu/](http://protege.stanford.edu/) and follow the installation instructions.
|
|
|
* Note that **the Debugger Plug-In is not compatible with Protégé version 4 and below**.
|
|
|
* Install the Ontology Debugger Plugin with Protégé's Update Function```File->Check for Plugins...``` and select *Ontology Debugger* ![installation_plugin](/uploads/19bb8181c61d7982936f275fe877d2b4/installation_plugin.png)
|
|
|
* Install the Ontology Debugger Plugin with Protégé's Update Function```File->Check for Plugins...``` and select *Ontology Debugger* ![installation_plugin](/uploads/93eff0f60980596022e284b38bc3679e/installation_plugin.PNG)
|
|
|
* **As an alternative** you can also download the [latest jar-file](http://isbi.aau.at/ontodebug/plugin) of the *Ontology Debugger* and copy the jar-File into the ```plugins``` subfolder of your Protégé 5 desktop client.
|
|
|
* If your Protégé client is already running, you will have to restart the client to load the plugin.
|
|
|
* After your Protégé client has restarted you will see the additional menu entry ```Tools->Debug Ontology ...```
|
... | ... | @@ -240,7 +240,7 @@ In the above debugging session the default settings and the *HermiT* reasoner we |
|
|
|
|
|
### Preferences for Fault Localization
|
|
|
|
|
|
![pref1](/uploads/37328ed2d3c99259200a8a28e895eb5c/pref1.png)
|
|
|
![pref1](/uploads/4d99be46e71a9f621cc2c851a42682e4/pref1.PNG)
|
|
|
|
|
|
##### Engine Types
|
|
|
|
... | ... | @@ -260,12 +260,9 @@ If you want to debug an __incoherent ontology__, the process quite often can be |
|
|
|
|
|
### Preferences for Query computation
|
|
|
|
|
|
![pref2](/uploads/328117a41b994b95cf088fe49e4ecd24/pref2.png)
|
|
|
![pref2](/uploads/fb85edeca2870e18e5a5ec669bb4c719/pref2.PNG)
|
|
|
|
|
|
Query Computation is a 3-stage process ...
|
|
|
|
|
|
#### Stage 1
|
|
|
Stage 1 has as goal the minimization of the overall number of queries in the debugging session. There are several measures for this purpose (default: Entropy).
|
|
|
age 1 has as goal the minimization of the overall number of queries in the debugging session. There are several measures for this purpose (default: Entropy).
|
|
|
|
|
|
##### Query Quality Measure
|
|
|
You can define Query Quality Measure for query selection such as **Entropy** (default), **Split in Half** and **RIO**. These aim at minimizing the number of queries to be answered by the interacting user until obtaining the correct repair.
|
... | ... | |