add option to automatically stop computing explanations after first is found

[balhoff]

In Protege 5.5, when I compute explanations for unsatisfiable classes, the "Stop searching" button is frequently unresponsive. So Protege continues to compute explanations while I keep trying to click the button (after it states that is has found 1), and sometimes I must force quit. In every case I can remember, I only need to see one explanation in order to diagnose the ontology problem. It would be very convenient if I could specify that I only need one explanation, before it starts searching.

For reference, I am usually working with Gene Ontology or Uberon, using the ELK reasoner, looking at classes equivalent to owl:Nothing in the DL query panel.

[matthewhorridge]

I need to investigate more, but some of this could be due to an entailment check that requires reasoning and is taking a long time to finish. Thanks for mentioning the materials to reproduce it. Much appreciated.

[balhoff]

Thanks for taking a look! Here is an ontology you can use directly (an unsatisfiable class is Malpighian tubule morphogenesis):

Prefix(:=<http://example.org/go-cl.ofn#>)
Prefix(owl:=<http://www.w3.org/2002/07/owl#>)
Prefix(rdf:=<http://www.w3.org/1999/02/22-rdf-syntax-ns#>)
Prefix(xml:=<http://www.w3.org/XML/1998/namespace>)
Prefix(xsd:=<http://www.w3.org/2001/XMLSchema#>)
Prefix(rdfs:=<http://www.w3.org/2000/01/rdf-schema#>)


Ontology(<http://example.org/go-cl.ofn>
Import(<http://purl.obolibrary.org/obo/cl/releases/2020-05-21/cl-base.owl>)
Import(<http://purl.obolibrary.org/obo/go/releases/2020-08-10/extensions/go-plus.owl>)
)

[smrgeoinfo]

I'm having a similar problem, the 'stop searching' button is un responsive. Running ELK, Protege 5.5., Windows 10. I end up having to kill Protege and never get to see the explanations that were found. Would be nice to limit number of explanations before starting the search.