Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ENHSP planner #189

Open
shshermin opened this issue Nov 12, 2024 · 1 comment
Open

ENHSP planner #189

shshermin opened this issue Nov 12, 2024 · 1 comment

Comments

@shshermin
Copy link

shshermin commented Nov 12, 2024

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:

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

@haz
Copy link

haz commented Nov 12, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants