Issue86

Title translator bug with conditional effects
Priority bug Status resolved
Superseder Nosy List gabi, haz, malte
Assigned To gabi Keywords 1.0
Optional summary

Created on 2010-03-25.14:51:03 by malte, last changed by gabi.

Files
File name Uploaded Type Edit Remove
light.ba.domain.pddl malte, 2010-03-25.14:51:21 application/octet-stream
light.ba.problem.1.pddl malte, 2010-03-25.14:51:27 application/octet-stream
Messages
msg2692 (view) Author: gabi Date: 2013-11-19.14:12:38
This is the same issue as issue 146, which is now resolved. So I close this one
as well.
msg2683 (view) Author: malte Date: 2013-11-16.21:58:28
> The question is what we should do in these cases. Of course, we can multiply
> out all possible combinations of values.

I would suggest that we don't do this and instead support multiple effects
affecting the same variable properly everywhere we currently support conditional
effects.

> Malte, do you have an idea which parts of the search component rely on the above
> assumption?

No, but most of them don't support conditional effects in any case.
msg2681 (view) Author: gabi Date: 2013-11-15.13:37:53
I reimplemented the translation of operators to fix this bug. One problem is
that now the translator can create operators with several conditional effects on
one variable that set the variable to different values (in this case the
conditions are mutually exclusive). Previously the translator simply bailed out
in these cases. The issue is that parts of the search component could rely on
the fact that an operator can set a variable only to one possible new value.

The question is what we should do in these cases. Of course, we can multiply out
all possible combinations of values. However, this could lead to many operators
with lots of preconditions: first, there are exponentially many such
combinations, second, we would need to include negated effect conditions for the
other values as operator precondition and negating a finite domain "atom" V=v
means replacing it with a disjunction over all other values of V.

So I wonder whether this is really the right way to go. Maybe we should rather
use a similar procedure as for axioms and conditional effects, where search
components that do not support them simply raise an exception. 

Malte, do you have an idea which parts of the search component rely on the above
assumption?
msg840 (view) Author: gabi Date: 2010-12-13.13:36:38
Update: This is not connected to the invariant synthesis but to issue 146
(operators that conditionally delete/add the same fact).
msg574 (view) Author: gabi Date: 2010-10-18.18:30:29
This is probably connected to the bug in the invariant synthesis (issue 132).

Waiting for issue 132 to be resolved...
msg313 (view) Author: malte Date: 2010-03-25.14:51:03
Message from Héctor Geffner:

Hi Malte,

I'm doing some work with Fabio (in the cc) where
we translate some problems into classical ones,
and solve them with lama, ff, etc. As usual.

In the translation, Fabio now generates pddl's
that ff parses well, but lama (and I guess, fd)
doesn't, reporting: 
 
 "Add effect with uncertain del effect partner?"
 AssertionError: Add effect with uncertain del effect partner?

Any idea of what this is?

I'm here from my students that Lama/FD/IPC base planner don't handle
negative preconds all that well, but this doesn't seem to be the problem
(I think I commented them out).

Example pddl files that report the error above
are attached.

Thanks a lot. Best
-hector
History
Date User Action Args
2013-11-19 14:12:38gabisetstatus: deferred -> resolved
messages: + msg2692
2013-11-16 21:58:28maltesetmessages: + msg2683
2013-11-15 13:37:54gabisetmessages: + msg2681
2010-12-22 19:16:41hazsetnosy: + haz
2010-12-13 13:36:38gabisetmessages: + msg840
2010-10-18 18:30:29gabisetstatus: unread -> deferred
messages: + msg574
2010-10-15 19:04:16maltesetassignedto: malte -> gabi
nosy: + gabi
2010-03-25 14:51:27maltesetfiles: + light.ba.problem.1.pddl
2010-03-25 14:51:21maltesetfiles: + light.ba.domain.pddl
2010-03-25 14:51:03maltecreate