Grounder fatal error: terminate called after throwing an instance of 'BadInputException' ...

[rpgoldman]

Trying to ground a rovers domain problem translated from PDDL (i.e., not from IPC2023), I get that error:

terminate called after throwing an instance of 'BadInputException'
  what():  Constraint type must be "=" (equal) or "!=" (not equal); "0" given

This is quite likely an error in the input I have provided, but I have no idea how to track this down. The input resulting in this error is on Dropbox.

If it's not too hard, it would be great if you could track the input lines and give a line number for bad input errors. It does seem like there are cases where pandaPIparser can give output that the grounder cannot read.

(added: could you use tellg to get position in the input stream for this purpose?)

[rpgoldman]

It looks to me like all of the constraints in the file are of this form:

#variable_constraints_first_number_then_individual_constraints
0
#end_of_task

or this form:

#variable_constraints
0
#end_of_method

I don't know if that's helpful.

[rpgoldman]

I have just repaired a number of errors in the input domain file, but am still getting this error:

terminate called after throwing an instance of 'BadInputException'
  what():  Constraint type must be "=" (equal) or "!=" (not equal); "0" given

Here are the relevant files:

• domain.hddl
• p01.hddl
• pandaPIparser output file
• pandaPIgrounder output file -- piped stdout and stderr together to this file.

[galvusdamor]

Hi @rpgoldman,

I've just had a look at this case. The problem was/is that the domain defines the predicates (empty) twice. This caused a hick-up in the parser and consequently that the numbering of predicates in the parser output file was off. This then caused the parsing error in the grounder (by not knowing how many arguments predicates actually have and then interpreting a variable index wrongly as the number of constraints -- of which there were not any, ...).

The simple fix is: remove one of the declarations. I have also added a safety feature to the parser that checks for double declarations, prints a warning to stderr, and only uses the first of the declarations (if there are multiple ones). This also fixes the issue with the current version of the domain.

Gregor