Tight Bounds for HTN Planning with Task Insertion Pascal Bercher Ulm University Ulm, Germany

Ron Alford ASEE-NRL Postdoctoral Fellow Washington DC, USA Abstract

Totally-Ordered Propositional HTN Complexity

HTN planning is the problem of decomposing an initial task to accomplish into a sequence of executable steps. HTN planning with Task Insertion (TIHTN planning) allows the insertion of operators from outside the method hierarchy, which: I Hybridizes classical planning with HTN planning I Allows partial task hierarchies with “missing required tasks” inserted by planner We provide tight complexity bounds for TIHTN planning along two axis: whether variables are allowed and whether methods must be totally ordered.

Standard Semantics EXPTIME

Arbitrary Arbitrary

Totally-Ordered Problems

The purpose of HTN planning is to complete a task. Tasks are either: I Primitive, which corresponds to some concrete action we know how to perform e.g: walk(room, hall), or drink(cof f ee)

Tail-Recursive

travel(h, stop1)

f ly(a1, a2)

bus(stop1, a1)

Acyclic NP

travel(a2, L.A.) taxi(a2, L.A.)

EXPSPACE

Partially-Ordered Problems

drink work

work write

We decompose a task network by replacing a node in the network with a corresponding method’s network. work

I

write

work

walk

work

write I

drink

drink

write

write

drink

work

write

drink

work

drink write

Method structures: Regular Method (totally-ordered): work

drink

write

Method (partially-ordered): work

drink work

work write

Method structures: Tail Recursive Method (partially-ordered):

Method (totally-ordered): live

work

sleep

Acyclic

Acyclic

EXPTIME PSPACE

Regular

Regular

NP

Regular-Acyclic

f loss

Method (partially-ordered):

write

Tail-Recursive

Complete Results

Method structures: Acyclic

work

Arbitrary

Regular-Acyclic

To a great extent, we can characterize the complexity of HTN and TIHTN planning by the structure of a problem’s methods: whether the methods are fully grounded, whether the methods are totally ordered, and where in the method recursion occurs.

Method (totally-ordered):

Tail-Recursive

work

An alternate set of semantics, HTN Planning with Task Insertion (TIHTN Planning) allows the insertion of tasks without a method. drink

Task-Insertion Semantics

NEXPTIME

A method (t, tn) is a non-primitive task t paired with a network tn

drink

Regular-Acyclic

Standard Semantics semidecidable Arbitrary

Method:

I

Regular-Acyclic

Partially-Ordered Propositional HTN Complexity

Methods and Decomposition I

Regular

Regular

Non-primitive, which is an abstract task. E.g. travel(home, L.A.) I Must recursively decompose non-primitive tasks until we get primitive tasks we know how to execute directly I We are given a set of methods, which are recipes on how to accomplish abstract tasks. E.g., to travel from home to L.A., we might decompose as follows: travel(h, L.A.) travel(h, a1)

Acyclic

Tail-Recursive

I

buy ticket

Task-Insertion Semantics

PSPACE

HTN Planning (Overview)

I

David W. Aha U.S. Naval Research Laboratory Washington DC, USA

Comparison of the complexity classes for HTN planning (completeness results) for HTN planning, with and without variables and task insertion (TI). Vars. Ordering TI Recursion Complexity no total no acyclic PSPACE no total no regular PSPACE no total no tail PSPACE no total no arbitrary EXPTIME no total yes – PSPACE no partial no acyclic NEXPTIME no partial no regular PSPACE no partial no tail EXPSPACE no partial no arbitrary undecidable no partial yes regular PSPACE no partial yes – NEXPTIME yes total no acyclic EXPSPACE yes total no regular EXPSPACE yes total no tail EXPSPACE yes total no arbitrary 2-EXPTIME yes total yes – EXPSPACE yes partial no acyclic 2-NEXPTIME yes partial no regular EXPSPACE yes partial no tail 2-EXPSPACE yes partial no arbitrary undecidable yes partial yes regular EXPSPACE yes partial yes – 2-NEXPTIME

work

live live

live

Conclusions

sleep

Totally-ordered TIHTN planning has the same worst-case complexity as classical planning. I Partially-ordered TIHTN planning has the same worst-case complexity as partially-ordered acyclic HTN planning (NEXPTIME), and is sometimes simpler Future Work: In the paper, we provide a new planning technique for TIHTN planning, called acyclic progression, that let us define worst-case efficient TIHTN planning algorithms. Theoretical efficiency is not implementation efficiency, and so we hope to implement and evaluate acyclic progression. I

Method structures: Arbitrary Method (totally-ordered): work

brew

work

Method (partially-ordered): drink

[email protected]

live

sleep work live

[email protected]

[email protected]

Tight Bounds for HTN Planning with Task Insertion - Ron Alford

E.g. travel(home, L.A.). ▷ Must recursively decompose non-primitive tasks until we get primitive tasks we know how to execute directly. ▷ We are given a set of ...

91KB Sizes 3 Downloads 327 Views

Recommend Documents

No documents