-
Notifications
You must be signed in to change notification settings - Fork 89
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
Transparent pddl #62
Transparent pddl #62
Conversation
Signed-off-by: Francisco Martin Rico <fmrico@gmail.com>
Signed-off-by: Francisco Martin Rico <fmrico@gmail.com>
Codecov Report
@@ Coverage Diff @@
## master #62 +/- ##
==========================================
+ Coverage 23.07% 23.08% +0.01%
==========================================
Files 116 119 +3
Lines 6137 6454 +317
Branches 3562 3811 +249
==========================================
+ Hits 1416 1490 +74
- Misses 2231 2279 +48
- Partials 2490 2685 +195
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
This looks very interesting. We will be taking a closer look. Thanks! |
We've worked through the build changes (which turned out to be pretty minor) but are still seeing the 'assign' token not known error. Are there any changes in terms of usage we need to change in order to ensure our test application is using the new functionality? Thanks |
@mark-sentaca, in the first tutorial, I describe how to run directly
Could you please try if this token is accepted? If not, try the same with TFD? |
Thank you - that has exposed a few errors in our pddl definition that I will have to debug. Interestingly, the token appears to be accepted because the errors are not related to the 'assign' keyword. Will keep you in the loop as we debug this. We are relatively new to pddl so that's been a learning curve with the team here. |
The error we were seeing from PlanSys2 was: |
Signed-off-by: Francisco Martin Rico <fmrico@gmail.com>
Signed-off-by: Francisco Martin Rico <fmrico@gmail.com>
Dear all,
This is a big change, and I would like to have feedback from you @teyssieuman @mark-sentaca @jjzapf @rossj13
Issues #61 #35 #21, at least, are motivated by the limitation of how plansys2_domain_expert stores the pddl domain. That's because I wanted to manage (merge) several domains. This can be useful in an application like this .
This PR contains an alternative way to solve this. With these changes, the model is not deep parsed, with the limitation that you found. Now, the domains are merged, respecting the original pddl content.
I hope you find it interesting. Please, try this branch to see if it solves the limitation that you found.
Best