hierarchical task network htn planning jos luis ambite
play

Hierarchical Task Network (HTN) Planning Jos Luis Ambite* [* Based - PowerPoint PPT Presentation

Hierarchical Task Network (HTN) Planning Jos Luis Ambite* [* Based in part on presentations by Dana Nau and Rao Kambhampati] 1 Hierarchical Decomposition 2 Task Reduction 3 Hierarchical Planning Brief History Originally developed about


  1. Hierarchical Task Network (HTN) Planning José Luis Ambite* [* Based in part on presentations by Dana Nau and Rao Kambhampati] 1

  2. Hierarchical Decomposition 2

  3. Task Reduction 3

  4. Hierarchical Planning Brief History � Originally developed about 25 years ago � NOAH [Sacerdoti, IJCAI 1977] � NONLIN [Tate, IJCAI 1977] � Knowledge-based � Scalable � Task Hierarchy is a form of domain-specific knowledge � Practical, applied to real world problems � Lack of theoretical understanding until early 1990’s [Erol et al, 1994] [Yang 1990] [Kambhampati 1992] � Formal semantics, sound/complete algorithm, complexity analysis [Erol et al, 1994] 4

  5. Deployed, Practical Planners � SIPE, SIPE-2 [Wilkins, 85-] � http://www.ai.sri.com/~sipe/ � NONLIN/O-Plan/I-X [Tate et. al., 77-] � http://www.aiai.ed.ac.uk/~oplan/ � http://www.aiai.ed.ac.uk/project/ix/ � Applications: � Logistics � Military operations planning: Air campaign planning, Non- Combatant Evacuation Operations � Crisis Response: Oil Spill Response � Production line scheduling � Construction planning: Space platform building, house construction � Space applications: mission sequencing, satellite control � Software Development: Unix administrator's script writing 5

  6. Deployed, Practical Planners Many features: � Hierarchical decomposition � Resources � Time � Complex conditions � Axioms � Procedural attachments � Scheduling � Planning and Execution � Knowledge acquisition tools � Mixed-initiative 6

  7. 7

  8. O-Plan 8

  9. HTN Planning � Capture hierarchical structure of the planning domain � Planning domain contains non-primitive actions and schemas for reducing them � Reduction schemas: � given by the designer � express preferred ways to accomplish a task 9

  10. HTN Formalization (1) � State: list of ground atoms � Tasks: � Primitive tasks: do[f(x 1 , …, x n )] � Non-primitive tasks: � Goal task: achieve(l) (l is a literal) � Compound task: perform[t(x 1 , …, x n )] � Operator: � [operator f(x 1 , …, x n ) (pre: l 1 , …, l n ) (post: l’ 1 , …, l’ n )] � Method: ( α , d) � α is a non-primitive task and d is a task network � Plan: sequence of ground primitive tasks (operators) 10

  11. HTN Formalization (2) � Task network: [(n 1 : α 1 ) … (n m : α m ), φ ] � n i = node label � α i = task � φ = formula that includes � Binding constraints: (v = v’) or (v ≠ v’) � Ordering constraints: (n < n’) � State constraints: � (n, l, n’): interval preservation constraint (causal link) � (l, n): l must be true in state immediately before n � (n, l): l must be true in state immediately after n 11

  12. Task Network Example 12

  13. HTN Planning Algorithm (intuition) Problem reduction: � Decompose tasks into subtasks � Handle constraints � Resolve interactions � If necessary, backtrack and try other decompositions 13

  14. Basic HTN Procedure 1. Input a planning problem P 2. If P contains only primitive tasks, then resolve the conflicts and return the result. If the conflicts cannot be resolved, return failure 3. Choose a non-primitive task t in P 4. Choose an expansion for t 5. Replace t with the expansion 6. Find interactions among tasks in P and suggest ways to handle them. Choose one. 7. Go to 2 14

  15. ground total ordering satisfying constraints m = ( α ’, d’) s.t. mgu( α , α ’) = θ τ = “critics” to Reduce(d, n, m) = task network obtained resolve conflicts from d by replacing (n : α ) θ with d’ θ (and modifying the constraint formula) 15

  16. Similarity between reduction schemas GobyBus(S,D) and plan-space planning In(B) t1: Getin(B,S) Hv-Tkt t2: BuyTickt(B) t3: Getout(B,D) Hv-Money At(D) At(Msn) Get(Money) GobyBus(Phx,Msn) Buy(WiscCheese) Hv-Money In(B) t1: Getin(B,Phx) Hv-Tkt t2: BuyTickt(B) Get(Money) t3: Getout(B,Msn) Hv-Money At(D) Buy(WiscCheese) 16

  17. 17

  18. 18

  19. 19

  20. Refinement Planning [Kambhampati 96] Task reduction 20

  21. Refinement Planning � Unified framework for state-space, plan-space, and HTN planning [Kambhampati et al, 96] 21

  22. Expressiveness of STRIPS vs HTN planning � Solutions to STRIPS problems are regular sets: (a 1 | a 2 |… a n ) * � Solutions to HTN problems can be n a 2 arbitrary context-free sets: a 1 n … a n n HTN’s are more expressive than STRIPS 22

  23. Task Decomposition via Plan Parsing � Task decomposition hierarchy can be seen as a context-free grammar � Prune plans that do not conform to the grammar in a Partial-Order planner [Barret & Weld, AAAI94] 23

  24. Task Decomposition via Plan Parsing 24

  25. Ordered Task Decomposition � Adaptation of HTN planning � Subtasks of each method to be totally ordered � Decompose these tasks left-to-right � The same order that they’ll later be executed Make the artwork for a PC board Preclean for artwork Apply photoresist Photolithography Etching Spindling Spraying Spreading Painting 25

  26. 26

  27. SHOP (Simple Hierarchical Ordered Planner) � Domain-independent algorithm for Ordered Task Decomposition � Sound/complete � Input: � State: a set of ground atoms � Task List: a linear list of tasks � Domain: methods, operators, axioms � Output: one or more plans, it can return: � the first plan it finds � all possible plans � a least-cost plan � all least-cost plans 27

  28. Simple Example Initial task list: � ((travel home park)) Initial state: � ((at home) (cash 20) (distance home park 8)) Methods (task, preconditions, subtasks): � � (:method (travel ?x ?y) ((at x) (walking-distance ?x ?y)) ' ((!walk ?x ?y)) 1) � (:method (travel ?x ?y) Optional cost; default is 1 ((at ?x) (have-taxi-fare ?x ?y)) ' ((!call-taxi ?x) (!ride ?x ?y) (!pay-driver ?x ?y)) 1) Axioms: � � (:- (walking-dist ?x ?y) ((distance ?x ?y ?d) (eval (<= ?d 5)))) � (:- (have-taxi-fare ?x ?y) ((have-cash ?c) (distance ?x ?y ?d) (eval (>= ?c (+ 1.50 ?d)))) Primitive operators (task, delete list, add list) � � (:operator (!walk ?x ?y) ((at ?x)) ((at ?y))) � … 28

  29. Simple Example Initial state: (Continued) (at home) (cash 20) (travel home park) (distance home park 8) Precond: Precond: (at home) (walking-distance (at home) (have-taxi-fare home park) Home park) Succeed Succeed (we have $20, and the fare is only $9.50) Succeed Fail (distance > 5) (!call-taxi home) (!ride home park) (!pay-driver home park) (!walk home park) (at park) Final state: (cash 10.50) (distance home park 8) 29

  30. The SHOP Algorithm state S; task list T=( t 1 ,t 2 ,…) procedure SHOP (state S, task-list T, domain D ) operator instance o 1. if T = nil then return nil 2. t 1 = the first task in T state o(S) ; task list T=(t 2 , …) 3. U = the remaining tasks in T 4. if t is primitive & an operator instance o matches t 1 then 5. P = SHOP ( o ( S ), U , D ) nondeterministic choice 6. if P = FAIL then return FAIL among all methods m 7. return cons( o , P ) whose preconditions 8. else if t is non-primitive can be inferred from S & a method instance m matches t 1 in S & m ’s preconditions can be inferred from S then 9. return SHOP ( S , append ( m ( t 1 ) , U ), D ) 10. else task list T=( t 1 ,t 2 ,…) 11. return FAIL method instance m 12. end if end SHOP task list T=( u 1 ,…,u k ,t 2 ,…) 30

  31. Time Blocks World 1000 100 100 randomly � 10 SHOP generated problems TLPlan 1 167-MHz Sun Ultra � with 64 MB of RAM 0.1 Blackbox and IPP � 0.01 could not solve any of these problems TLplan’s running time � Number of actions in plan 400 was only slightly worse 350 than SHOP’s 300 � TLplan’s pruning rules 250 SHOP [Bacchus et al. , 2000] 200 TLPlan have expressive power 150 similar to SHOP’s 100 � Using its pruning rules, 50 they encoded a block- 0 stacking algorithm similar to ours 31

  32. Logistics 10000 1000 Time 110 randomly � 100 SHOP generated problems 10 TLPlan Same machine � 1 as before 0.1 As before, Blackbox � and IPP could not solve any of these problems 500 TLplan ran Number of actions in plan � 400 somewhat slower 300 SHOP than SHOP 200 TLPlan (about an order of 100 magnitude on large 0 problems) 32

  33. Logistics 10000 1000 Time Blackbox 30 problems from � 100 TLPlan the Blackbox 10 SHOP distribution 1 SHOP and TLplan � 0.1 on the same machine as before Blackbox on a faster � machine, with 8GB 100 of RAM 80 Number of actions in plan SHOP was about an � Blackbox 60 order of magnitude TLPlan faster than TLplan 40 SHOP TLplan was about � 20 two orders of 0 magnitude faster than Blackbox 33

  34. SHOP demo 34

  35. 35

Recommend


More recommend