You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This formulation doesn't work, and I am not sure why.
In addition, PlanSys doesn't support forall and imply so the final solution shouldn't contain both.
Perhaps it is easier to define a SWRL rule for this instead of defining it in PDDL
The text was updated successfully, but these errors were encountered:
one should be able to model imply( X Y ) as (or (not X) Y)
but I think a SWRL rule and some modifications to the PDDL might be better suited. I don't think, we can encode everything in SWRL because of how negations work in OWL. But we can have a SWRL rule for better_performance such as:
(I dropped the function from the relation as solvesF is functional anyway and it is therefore redundant)
this can than be used in PDDL, where one checks that there is no better functional design that is realisable (syntax might be slightly off...):
I am having a hard time trying to modify the SUAVE PDDL formulation to select the best function design available.
So far, I have something like the following:
This formulation doesn't work, and I am not sure why.
In addition, PlanSys doesn't support
forall
andimply
so the final solution shouldn't contain both.Perhaps it is easier to define a SWRL rule for this instead of defining it in PDDL
The text was updated successfully, but these errors were encountered: