Oclingo do not increment grounding step by following example.
:- not p(2).
oclingo stop in inc step 1 with UNSAT ,even tough it has to increment grounding step.
The input you supply is invalid. You require an atom from step 2 but declare step 1. What happens when you give the following input?
CALL: controller.py input.lp
I see that the sketched example may be inappropriate. But there is also a problem when running:
:- p((t #mod 2)+1).
$ controller.py input.lp
Then, oclingo reports empty answer sets, but answer sets with "p(1)" or "p(2)", respectively, are requested from the controller side.
Could this be a problem with "#volatile."?
oclingo development is discontinued - please switch to clingo-4
Sign up for the SourceForge newsletter:
You seem to have CSS turned off.
Please don't fill out this field.