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
Currently, we are not using the concepts of "Objective" and "FunctionGrounding".
Should we add a (Objective ?f) effect to the actions effects to represent which function is currently in use? And a (FunctionGrounding ?fd) effect to represent which function designs are selected? Is this useful?
Or can we just remove these two concepts?
In our PDDL formulation, this information is "kind of" captured by the action's preconditions when they are grounded. For example:
If the action search_pipeline is grounded with f1=f_maintain_motion and fd1=fd_all_thrusters, it indirectly implies the same as having an (Objective f_maintain_motion) and a (FunctionGrounding fd_all_thrusters). Whenever fd1 is not realizable the precondition will fail and retrigger replanning.
Currently, we are not using the concepts of "Objective" and "FunctionGrounding".
Should we add a
(Objective ?f)
effect to the actions effects to represent which function is currently in use? And a(FunctionGrounding ?fd)
effect to represent which function designs are selected? Is this useful?Or can we just remove these two concepts?
In our PDDL formulation, this information is "kind of" captured by the action's preconditions when they are grounded. For example:
If the action
search_pipeline
is grounded withf1=f_maintain_motion
andfd1=fd_all_thrusters
, it indirectly implies the same as having an(Objective f_maintain_motion)
and a(FunctionGrounding fd_all_thrusters)
. Wheneverfd1
is not realizable the precondition will fail and retrigger replanning.The text was updated successfully, but these errors were encountered: