|
# Protégé Debugger plug-in
|
|
# Protégé Debugger plug-in
|
|
|
|
|
|
This page describes the plug-in
|
|
This page describes the
|
|
[org.exquisite.protege-1.0-SNAPSHOT.jar](/uploads/14b0041bfa33146eb10283d795b745de/org.exquisite.protege-1.0-SNAPSHOT.jar) |
|
[Protégé plug-in](/uploads/14b0041bfa33146eb10283d795b745de/org.exquisite.protege-1.0-SNAPSHOT.jar)
|
|
\ No newline at end of file |
|
|
|
|
|
**NOTE: THIS PLUG-IN IS STILL IN DEVELOPMENT, VERY PROBABLY YOU WILL EXPERIENCE FAULTY AND UNEXPECTED BEHAVIOUR SUCH AS DEADLOCKS**
|
|
|
|
|
|
|
|
# Installation
|
|
|
|
## Prerequisites
|
|
|
|
These requirements are necessary in order to run the plugin:
|
|
|
|
* Java Runtime Version 8. If you do not have it installed, please download it from [https://www.java.com/de/download/](https://www.java.com/de/download/) and follow the installation instructions there.
|
|
|
|
* The most recent Protege Desktop Version. Please download it from [http://protege.stanford.edu/](http://protege.stanford.edu/) and follow the installation instructions. Please not that is recommended to use version 5. The Protégé Debugger Plug-In is not compatible with version 4.
|
|
|
|
* The [Protégé Debugger Plug-In](/uploads/14b0041bfa33146eb10283d795b745de/org.exquisite.protege-1.0-SNAPSHOT.jar)
|
|
|
|
|
|
|
|
## Usage
|
|
|
|
### Some other plugins are necessary
|
|
|
|
Our plugin requires at least one reasoner. Protege 5 comes already with HermiT, but you can also install other reasoners like FaCT++ or Pellet. Installing plugins in Protégé is done by selecting File->Check for plugins... After installing additional reasoner plugins you will have to restart Protégé
|
|
|
|
### Install the Protégé Plugin
|
|
|
|
Copy the protege [Protégé plug-in](/uploads/14b0041bfa33146eb10283d795b745de/org.exquisite.protege-1.0-SNAPSHOT.jar) into the plugins subfolder of your Protégé 5 desktop client. If your Protégé client is running, please restart it to load the Plug-In. You should see now a new tab called Exquisite Debugger!
|
|
|
|
|
|
|
|
![ExquisiteDebuggerTab](/uploads/a25cb9d39e0523e0b9ddfdd83928e50e/ExquisiteDebuggerTab.PNG)
|
|
|
|
|
|
|
|
### Exquisite Ontology Debugging
|
|
|
|
Now load an ontology. For this document we are using [our example ontology](/uploads/f100242ac5e8c655833a21e3ec9143e6/running_example_annotated.owl) with explicit declaration of axioms that are possibly faulty (we name the m the knowledge base, correct axioms or background knowledge as well as entailed and not entailed examples.
|
|
|
|
|
|
|
|
Open the Exquisite Ontology Debug Tab (*Exquisite Debugger -> Open Exquisite Ontology Debug Tab*) and select the tab.
|
|
|
|
![debugger](/uploads/b18b3ea12f8ee4e7e14b07676abbc080/debugger.PNG)
|
|
|
|
|
|
|
|
### Diagnoses
|
|
|
|
With this tool we can search for diagnoses. But first we have to configure which reasoner we want to use for the diagnoses search. Select *Reasoner->and a preferered reasoner*
|
|
|
|
|
|
|
|
### Options for diagnoses
|
|
|
|
Next let us see what option do we have for the diagnoses search. Select *Exquisite Debugger->Options*
|
|
|
|
![options_diagnoses](/uploads/085d60225ca537dd5df02a8e543e9086/options_diagnoses.PNG)
|
|
|
|
|
|
|
|
* As diagnoses engine we can choose between Juncker's QuickXPlain (default), HS-DAG and HS-Tree.
|
|
|
|
* Next we can choose how many diagnoses we want to calculate at most (default is 9). Please note that the higher the number the more time is required to calculate depending on the complexity of the ontology.
|
|
|
|
* If we have a consistent ontology we can reduce the incoherency to inconsistency and by option can extract star modules for that case.
|
|
|
|
|
|
|
|
### The search for diagnoses
|
|
|
|
Once we are happy with our preferences we can start the *Search Diagnoses* button and hopefully we will get some diagnoses in reasonable time.
|
|
|
|
In our example we will get these diagnoses:
|
|
|
|
![diagnoses](/uploads/216e58d304370983784d2b4d480777e1/diagnoses.PNG) |
|
|
|
\ No newline at end of file |