-
Notifications
You must be signed in to change notification settings - Fork 0
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
Consider shifting to pddl
#1
Comments
Since my next step is to implement existential preconditions (:exists) in Lifted PDDL, I have just taken a look at pddl. However, from the Readme, it seems that it does not support that PDDL requirement yet. |
Let's see... Anything else that would be required? |
Right now I am using Typed STRIPS + existential preconditions, so nothing else for now. |
From our previous conversation, I think it would be a good idea to also have support for universal effects (forall when) and, maybe, all the ADL requirements. In the future I would like to extend Lifted PDDL so that it supports ADL, so it is a matter of when ADL will be supported by pddl. If they have no intention to support it in the near future (since it is a lot of work), maybe I should stick to tarski, since they already support ADL (to the best of my knowledge). |
Aye, fair enough. Not sure how big of a task it'll be in the end, and something |
For now, I think I'll stick to tarski since I need support for existential preconditions ASAP. But in the future I'll consider shifting to pddl if they have implemented support for ADL by then. |
Not sure it needs to be closed out -- feel free to leave it on hold and assign me. I'll have a look into what's required on the |
Re-opening, as we're about to have full ADL support drop. |
If there's a desire to extend things to more general forms of PDDL expressivity, then a more flexible library might be useful. pddl is a decent candidate (already expressive, and easy-to-extend lark for the parsing context).
The text was updated successfully, but these errors were encountered: