You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let's consider the complete example in attach.
The file plansys2_problem5/launch/commands contains for instance the predicate: set predicate (notFilling r)
And internally in the problem expert it is stored with the capitalized letter. However, when the domain file is read to then create the BT and check for the preconditions before starting an action, since the string is different it is not able to correctly verify the condition, and the execution aborts with the message precondition not met.
Similar problem, the actions have been implemented with name capitalized. However, when searching for the action performer the search uses the lowercase name, and it does not find a possible executor.
Let me remind that, PDDL is case insensitive, so in PlanSYS2 we need to be uniform if the language used for generating/writing plans is such.
Let's consider the complete example in attach.
The file
plansys2_problem5/launch/commands
contains for instance the predicate:set predicate (notFilling r)
And internally in the problem expert it is stored with the capitalized letter. However, when the domain file is read to then create the BT and check for the preconditions before starting an action, since the string is different it is not able to correctly verify the condition, and the execution aborts with the message precondition not met.
Similar problem, the actions have been implemented with name capitalized. However, when searching for the action performer the search uses the lowercase name, and it does not find a possible executor.
Let me remind that, PDDL is case insensitive, so in PlanSYS2 we need to be uniform if the language used for generating/writing plans is such.
plansys2_problem5.zip
@fmrico
The text was updated successfully, but these errors were encountered: