Debugging: Best Practices
- Dominant language
- Common Lisp
- Stars
- 59
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I wanted to know whether there are some hints on how to best debug a newly defined problem that doesn't work as expected (i.e., no plan was found).
I figured out that the pure task domain can be verified via ```tmsmt ops.pddl facts.pddl``` which is a first step.
But once this is done, I would like to get more insight into the full blown geometric problem. For example: Is it possible to output the initial and goal state conjunction? The initial state depends on the scene file, the optional task problem definition (:init) and the initial state (-q). I'm not sure I fully understand what happens when competing facts are defined in these different sources.
I'm also using the python interface and first thought that outputting the return value of ```tm.bind_scene_state``` and ```tm.bind_goal_state``` might give all necessary information but I realized that these lists are not the full state (at least the planner even fails when both are identical -- although there should be a trivial solution).
Any hints on how to debug (without going the LISP way)?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.