Title Wrong behaviour with undefined numeric expressions
Priority bug Status chatting
Superseder Nosy List gabi, malte
Assigned To Keywords translator
Optional summary

Created on 2019-05-03.09:15:48 by gabi, last changed by gabi.

File name Uploaded Type Edit Remove
domain.pddl gabi, 2019-05-03.09:15:48 application/octet-stream
p01.pddl gabi, 2019-05-03.09:16:01 application/octet-stream
msg8769 (view) Author: gabi Date: 2019-05-04.08:40:09
Making this part of the grounding algorithm would have the advantage that we
could also eliminate other, then unreachable action.
msg8768 (view) Author: malte Date: 2019-05-03.12:46:24
My first impulse was to integrate the testing of well-definedness in the
grounding algorithm (for efficiency), but then we cannot easily get such
warnings because the failing actions are never generated.
msg8767 (view) Author: gabi Date: 2019-05-03.09:15:48
This was mentioned by Emil Keyder on the mailing list.

If some action refers to an uninitialized numeric expression, the translator
stops with "AssertionError: Could not find instantiation for PNE!". The correct
behaviour would be to simply not instantiate this action.

Maybe we should in this case include an output that the action was removed,
because otherwise this behaviour could easily hide modelling mistakes.
Date User Action Args
2019-05-04 08:40:09gabisetmessages: + msg8769
2019-05-03 12:46:24maltesetstatus: unread -> chatting
nosy: + malte
messages: + msg8768
2019-05-03 09:16:01gabisetfiles: + p01.pddl
2019-05-03 09:15:48gabicreate