Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
tutorials:intermediate:performing_plans [2016/07/21 15:37] – gkazhoya | tutorials:intermediate:performing_plans [2019/02/04 17:46] – Updated syntax errors due to renamed packages in v0.70 (action-desig -> action-grounding + cram_plan_library -> cram_executive) amar | ||
---|---|---|---|
Line 8: | Line 8: | ||
<code lisp> | <code lisp> | ||
- | CL-USER> (ros-load: | + | CL-USER> (ros-load: |
- | ;; or ,r-l-s RET cram_plan_library | + | ;; or ,r-l-s RET cram_executive |
</ | </ | ||
Line 22: | Line 22: | ||
<code lisp> | <code lisp> | ||
- | CL-USER> (prolog: | + | CL-USER> (prolog: |
- | | + | |
| | ||
| | ||
Line 34: | Line 34: | ||
<code lisp> | <code lisp> | ||
CL-USER> (cpl: | CL-USER> (cpl: | ||
- | (plan-lib:perform (desig:an action (to eat) (yummy pizza)))) | + | (exe:perform (desig:an action (to eat) (yummy pizza)))) |
hmmm... nomnomnom... PIZZA | hmmm... nomnomnom... PIZZA | ||
</ | </ | ||
Line 44: | Line 44: | ||
<code lisp> | <code lisp> | ||
CL-USER> (cpl: | CL-USER> (cpl: | ||
- | (plan-lib:perform (desig:an action (to eat) (yummy pizza) (goal (object-eaten pizza))))) | + | (exe:perform (desig:an action (to eat) (yummy pizza) (goal (object-eaten pizza))))) |
WARNING: | WARNING: | ||
| | ||
Line 79: | Line 79: | ||
<code lisp> | <code lisp> | ||
PLAN-LIB> | PLAN-LIB> | ||
- | (plan-lib:perform (desig:an action (to eat) (yummy pizza) (goal (object-eaten pizza))))) | + | (exe:perform (desig:an action (to eat) (yummy pizza) (goal (object-eaten pizza))))) |
hmmm... nomnomnom... PIZZA | hmmm... nomnomnom... PIZZA | ||
NIL | NIL | ||
Line 87: | Line 87: | ||
Please keep in mind that if there are multiple solutions to a particular action designator, i.e. it resolves to different plans, the first one that is defined will be executed. Ordering is not yet implemented and should probably be taken care of explicitly in the plans anyway. | Please keep in mind that if there are multiple solutions to a particular action designator, i.e. it resolves to different plans, the first one that is defined will be executed. Ordering is not yet implemented and should probably be taken care of explicitly in the plans anyway. | ||
- | + | Summary: **make sure an action designator you use for plans can only be resolved to one unique CRAM plan.** | |
- | Also, if the same action designator can be executed by both a process module or a high-level plan, the precedence will always be given to the process module as it should get the most specific designators. | + | |
- | + | ||
- | Summary: **make sure an action designator you use for plans can only be resolved to one unique CRAM plan and that the process modules always get as input one level more detailed action designator than the plan. Even better is to not have similar action designators for PMs and those for plans.** | + |