Issue1194

Title Translate option --keep-no-ops triggers "Error reading task"
Priority bug Status chatting
Superseder Nosy List davidspeck, jendrik, malte, tanja
Assigned To Keywords
Optional summary
The new checks in the search component that run when reading a planning task 

assume that each action has at least one effect (issue1146). However, this
causes 
problems because we now allow no-op actions (issue1184).

Created on 2025-12-12.16:21:42 by davidspeck, last changed by malte.

Summary
The new checks in the search component that run when reading a planning task 

assume that each action has at least one effect (issue1146). However, this
causes 
problems because we now allow no-op actions (issue1184).
Files
File name Uploaded Type Edit Remove
domain.pddl davidspeck, 2025-12-12.16:23:08 application/octet-stream
prob01.pddl davidspeck, 2025-12-12.16:23:27 application/octet-stream
Messages
msg11920 (view) Author: malte Date: 2025-12-12.17:22:26
Thanks! So this means we should relax the checks.

This is closely related to
the latest discussion in issue1146, in particular msg11881.

Looking at
issue1146, I thought we merged it. Did we not? I see the issue is still open,
but it could also be that we just forgot to close it.

Perhaps it's still open
because we didn't yet open the follow-up issue mentioned in the discussion?
msg11918 (view) Author: davidspeck Date: 2025-12-12.16:25:37
I just realized that the files are not attached to the individual messages (nice 
:).
Here is the call that triggers the error:

./fast-downward.py --translate --search domain.pddl prob01.pddl --translate-
options --keep-no-ops --search-options --search "astar(blind())"
msg11917 (view) Author: davidspeck Date: 2025-12-12.16:23:08
I don't know how to upload two files at once. Here is a simple domain file:
History
Date User Action Args
2025-12-12 17:22:26maltesetmessages: + msg11920
summary: The new checks in the search component that run when reading a planning task assume that each action has at least one effect (issue1146). However, this causes problems because we now allow no-op actions (issue1184). -> The new checks in the search component that run when reading a planning task assume that each action has at least one effect (issue1146). However, this causes problems because we now allow no-op actions (issue1184).
2025-12-12 16:25:37davidspecksetmessages: + msg11918
2025-12-12 16:23:27davidspecksetfiles: + prob01.pddl
2025-12-12 16:23:08davidspecksetfiles: + domain.pddl
messages: + msg11917
2025-12-12 16:21:42davidspeckcreate