Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#70 unsat bug

v3.x
wont-fix
oclingo (12)
5
2014-04-24
2012-09-27
Tobias Rabener
No

Oclingo do not increment grounding step by following example.

oclingo input:

cumulative t.

{p(t)}.

controller input:

step 1.

:- not p(2).

endstep.

oclingo stop in inc step 1 with UNSAT ,even tough it has to increment grounding step.

Discussion

  • Tovok7
    Tovok7
    2012-09-27

    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?

    step 2.

    :- not p(2).

    endstep.

     
  • Martin Gebser
    Martin Gebser
    2012-09-27

    CALL: controller.py input.lp

     
    Attachments
  • Martin Gebser
    Martin Gebser
    2012-09-27

    I see that the sketched example may be inappropriate. But there is also a problem when running:

    $ oclingo

    base.

    {p(1),p(2)}.

    volatile t.

    :- 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."?

    Cheers,
    Martin

     
    • assigned_to: Tovok7 --> Philipp Obermeier
    • Group: --> v1.x
     
  • oclingo development is discontinued - please switch to clingo-4

     
    • status: open --> wont-fix
    • Group: v1.x --> v3.x