I am currently working on generating execution rules automatically from a PDDL file and noticed that a condition like (and robot_close) creates a parsing error. Replacing it with (and robot_close dummy) is parsable. I assume the same is true for or?!
I know that in theory every and should have at least two arguments because it is mute otherwise but since the conditions have the same syntax as PDDL where an and with only one argument is allowed by most parsers it is a bit confusing.
Hi,
I am currently working on generating execution rules automatically from a PDDL file and noticed that a condition like
(and robot_close)creates a parsing error. Replacing it with(and robot_close dummy)is parsable. I assume the same is true for or?!I know that in theory every
andshould have at least two arguments because it is mute otherwise but since the conditions have the same syntax as PDDL where anandwith only one argument is allowed by most parsers it is a bit confusing.