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
I am testing using the ENHSP planner via the PDDL editor because it is more convenient. and I am using the option "Planning as a service". However, I get the following error:
Planning service: https://solver.planning.domains:5001/package/enhsp/solve
Domain: fit, Problem: fit
Error: set: invalid option: "domain"
FATAL: "-o": executable file not found in $PATH
Plan found:
Metric: 0
Makespan: 0
States evaluated: undefined
Planner found 1 plan(s) in 2.939secs.
I need to mention that the domain and problem file work when I am using the planner directly. So I doubt that they have a problem.
Also, in general, how do we usually set the configuration before calling a planner?
the name of my domain file is: domain.pddl
the name of my problem file is: problem.pddl
Thank you !
best,
Sher
The text was updated successfully, but these errors were encountered:
I can speak to the direct error -- this is a known issue that @hstairs is currently working on. The enhsp-2020 works best if you have planutils installed locally, but we're waiting on a bug fix to be pushed for the generic enhsp hosted on the solver.
As for the configuration -- typically the problem file would refer to the domain name in another open tab, and that is what the plugin would use to send to the service.
Dear all,
I am testing using the ENHSP planner via the PDDL editor because it is more convenient. and I am using the option "Planning as a service". However, I get the following error:
I need to mention that the domain and problem file work when I am using the planner directly. So I doubt that they have a problem.
Also, in general, how do we usually set the configuration before calling a planner?
the name of my domain file is: domain.pddl
the name of my problem file is: problem.pddl
Thank you !
best,
Sher
The text was updated successfully, but these errors were encountered: