Error: PDDL Planning Service returned code 400 BAD REQUEST
Its my first time trying to use PDDL in Visual Studio Core. I was just following the tutorial with a demo project, trying to solve it. This is the answer I get when I do alt + P: Error: PDDL Planning Service returned code 400 BAD REQUEST Im trying to use the default settings, https://solver.planning.domains/solve Why do I get this error?
I was trying to solve the problem (it gets a solution in pddl.editor) but it doesnt compile in visual studio core
Solution
The online solver has been updated, and it looks like you're using an old endpoint. You should use the "Planning-as-a-Service" planner (add a new one in the plugin settings), and configure it like this:
- How to specify empty preconditions in PDDL?
- PDDL: Forall and when in action effect
- Error: PDDL Planning Service returned code 400 BAD REQUEST
- PDDL forall to initialize objects
- How to model a PDDL case in Java
- PDDL - Planning the moving of a vehicle
- PDDL Segmentation fault
- In PDDL, how can I access time since *start* as a variable?
- Unexpected PDDL behavior with fluents and durative actions
- Cannot compile PDDL 2.1 Temporal Planner POPF on Ubuntu 20.04.1 LTS
- Difference between PDDL Online Planner vs POPF Planner
- Some criteria when it comes to defining a PDDL domain
- how to build an action with unfixed length?
- PDDL forall effect with durative actions
- Why isn't PDDL compiling correctly and resulting in parse error?
- object composition in PDDL
- PDDL syntax for effect with semantic meaning of "one of type"
- PDDL - invalid predicates and correct usage of forall
- PDDL syntax error, ':DURATIVE-ACTIONS' : domain definition expected
- PDDL planner does not recognize types
- how to put conditions in PDDL?
- Issue while developing a planning algorithm
- PDDL How to assign number for many predicates
- I can't seem to understand actions and goal in pddl
- PDDL2.1: Purpose of `over all`
- PDDL Durative-Action: Flexible duration
- Why isn't my PDDL compiling? Parsing error
- How to debug a PDDL domain/problem if the planner is timing out?
- pddl precondtion not working correctly in the plan
- How to write PDDL Domain and Problem file?