- changed milestone to Later
Evaluate inference
Issue #149
open
Inference that evaluates a given formula/term/... in a given structure. (something like the query-inference, but for other input formats)
Comments (13)
-
-
- removed milestone
Removing milestone: Later (automated comment)
-
New usecase: after calculating the approximating definition, evaluate the top-level constraints in the calculated structure, to see whether they have been deduced to be false (so that an inconsistency warning may be printed)
-
- changed status to resolved
Fixes #149: implemented evaluate inference through query.
→ <<cset ccde6afc2628>>
-
Fixes #149: implemented evaluate inference through query.
→ <<cset edb6813ee266>>
-
Fixes #149: implemented evaluate inference through query.
→ <<cset 769b8a9684eb>>
-
Fixes #149: implemented evaluate inference through query.
→ <<cset 8a1ee2606f27>>
-
Fixes #149: implemented evaluate inference through query.
→ <<cset c747a27627b1>>
-
reporter
- changed status to open
This does not yet work in the context of partial interpretations. However, some test need this feature!
-
reporter
Disabled checking of two tests.
When lazy grounding, they yield partial interpretations. However, checking correctness of partial interpretations is not yet implemented. See #149
→ <<cset c66dc3710a8f>>
-
reporter
disabled verification of test. Evaluate inference too slow. Blame BDDs @PieterVH
See #149
As soon as issue is fixed. Should be reenabled
→ <<cset e0f4cbc21e66>>
-
reporter
This does not yet work in a partial structure
-
disabled verification of test. Evaluate inference too slow. Blame BDDs @PieterVH
See #149
As soon as issue is fixed. Should be reenabled
→ <<cset e0f4cbc21e66>>
- Log in to comment
