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

Mechanism to load problem pddl files #1

Closed
paucarre opened this issue May 12, 2021 · 1 comment
Closed

Mechanism to load problem pddl files #1

paucarre opened this issue May 12, 2021 · 1 comment

Comments

@paucarre
Copy link

paucarre commented May 12, 2021

Thanks for the example and all the work in PlanSys2 !

I'd like to know if there is a way to load directly upon launch the problem pddl to the problem expert node. Namely, load to the problem expert node one of the files: cooking_problem_0.pddl, .., cooking_problem_3.pddl

As far as I see, the problem expert node launch requires the domain pddl, which seems to configure the domain expert.
Is there any way the problem expert node can directly load the problem pddl directly using a configuration parameter upon launch?

Side question: as the domain expert gets domain pddl in its launch configuration, shouldn't the problem expert node just get the problem pddl as configuration and rely on the domain expert configured domain pddl?

@paucarre paucarre changed the title Mechanism to load problem files Mechanism to load problem pddl files May 12, 2021
@fmrico
Copy link
Contributor

fmrico commented May 16, 2021

Hi @paucarre

Your question is really interesting. It would be very useful to init the knowledge from a problem pddl, or even from a YAML file. In my examples, I use the controllers (executables that use the problem_expert client to insert knowledge).

If you want to work on that and prepare a PR, I can guide and help you.

Thanks for using PlanSys2 :)

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