You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I ran into a problem with what seems to be a bug with the minQualifiedCardinality axiom. It exists in Pellet as well, but when using HermiT there is no problem. There are workarounds of course but I would like to be able to use this axiom as it was meant to work.
The error it throws is as follows:
java.lang.ArrayIndexOutOfBoundsException: Index 2 out of bounds for length 2
at openllet.core.tableau.branch.DisjunctionBranch.tryBranch(DisjunctionBranch.java:164) ~[openllet-core-2.6.5.jar:2.6.5]
at openllet.core.tableau.branch.Branch.tryNext(Branch.java:130) ~[openllet-core-2.6.5.jar:2.6.5]
at openllet.core.tableau.completion.SROIQStrategy.backtrack(SROIQStrategy.java:112) ~[openllet-core-2.6.5.jar:2.6.5]
at openllet.core.tableau.completion.SROIQStrategy.complete(SROIQStrategy.java:170) ~[openllet-core-2.6.5.jar:2.6.5]
at openllet.core.boxes.abox.ABoxImpl.lambda$isConsistent$12(ABoxImpl.java:1417) ~[openllet-core-2.6.5.jar:2.6.5] at openllet.core.utils.Timers.execute(Timers.java:118) ~[openllet-core-2.6.5.jar:2.6.5]
It goes on for a while but this probably the most relevant part.
I've had the problem with several ontologies but below is the simplest ontology that I could make that triggers the exception:
The text was updated successfully, but these errors were encountered:
broektjvd
changed the title
Apparent bug when using minQualifiedCardinality
ArrayIndexOutOfBoundsException when using minQualifiedCardinality
Mar 23, 2021
I ran into a problem with what seems to be a bug with the
minQualifiedCardinality
axiom. It exists in Pellet as well, but when using HermiT there is no problem. There are workarounds of course but I would like to be able to use this axiom as it was meant to work.The error it throws is as follows:
It goes on for a while but this probably the most relevant part.
I've had the problem with several ontologies but below is the simplest ontology that I could make that triggers the exception:
The text was updated successfully, but these errors were encountered: