-
Notifications
You must be signed in to change notification settings - Fork 158
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
forall and when statements in domain file #178
Comments
It's on our todo list (and in the project boards). I hope that it is something that get added in the next cleanup of the codebase which we are starting now. The "when" effects can also be handled with some creative PDDL editing. For example, but introducing new operators that model the different conditions under which the original conditional operator can be applied. Michael |
…t conditional effects This is due to the fact that ROSPlan doesn't seem to support conditional effects and forall goals: KCL-Planning/ROSPlan#178
To my understanding, all depends on what the user planner supports, right? |
…t conditional effects This is due to the fact that ROSPlan doesn't seem to support conditional effects and forall goals: KCL-Planning/ROSPlan#178
Hello Corot, Almost all will depend upon the underlying planner, but there are a couple of places it needs support in ROSPlan (and is not implemented yet). I think the major two are:
Michael |
@m312z, thanks for the comment. |
I have seen a previous issue asking about the forall keyword, and would like to see if there is any update on a possible implementation for this. Also interested in conditional effects (when). I realize that the forall can be handled with some creative PDDL editing, but not sure about the when. Thanks.
The text was updated successfully, but these errors were encountered: