Issue318

Title Problem parsing ADL domain
Priority bug Status resolved
Superseder Nosy List malte, rpgoldman
Assigned To malte Keywords
Optional summary

Created on 2012-02-03.02:12:13 by rpgoldman, last changed by malte.

Files
File name Uploaded Type Edit Remove
problem.pddl rpgoldman, 2012-02-03.02:12:48 application/octet-stream
trap.pddl rpgoldman, 2012-02-03.02:12:29 application/octet-stream
Messages
msg2038 (view) Author: malte Date: 2012-02-03.22:50:16
Hi Robert, thanks for the analysis! I'm closing this since we already have this
issue open elsewhere: issue164. I'll add you to the nosy list there. If it takes
us more than a few weeks to act on this, feel free to nudge me.
msg2037 (view) Author: rpgoldman Date: 2012-02-03.18:17:28
AFAICT, the problem parser does not expect a :requirements component in the 
problem statement, but the PDDL grammar seems to permit this.
msg2036 (view) Author: rpgoldman Date: 2012-02-03.02:12:12
When I try to parse the attached domain and problem (modified versions of the 
BAMS domain from the IPC), I get an assertion failure where init[0] is not equal 
to ":init" in translate/tasks/pddl.py

Indeed, when I check, init[0] is actually bound to ":requirements" instead.
History
Date User Action Args
2012-02-03 22:50:16maltesetstatus: chatting -> resolved
assignedto: malte
messages: + msg2038
2012-02-03 18:17:29rpgoldmansetstatus: unread -> chatting
messages: + msg2037
2012-02-03 02:12:48rpgoldmansetfiles: + problem.pddl
2012-02-03 02:12:29rpgoldmansetfiles: + trap.pddl
2012-02-03 02:12:13rpgoldmancreate