Skip to main navigation Skip to search Skip to main content

Tight bounds for HTN planning

    Research output: Chapter in Book/Report/Conference proceedingConference Paperpeer-review

    58 Citations (Scopus)

    Abstract

    Although HTN planning is in general undecidable, there are many syntactically identifiable sub-classes of HTN problems that can be decided. For these sub-classes, the decision procedures provide upper complexity bounds. Lower bounds were often not investigated in more detail, however. We generalize a prepositional HTN formalization to one that is based upon a function-free first-order logic and provide tight upper and lower complexity results along three axes: whether variables are allowed in operator and method schemas, whether the initial task and methods must be totally ordered, and where recursion is allowed (arbitrary recursion, tail-recursion, and acyclic problems). Our findings have practical implications, both for the reuse of classical planning techniques for HTN planning, and for the design of efficient HTN algorithms.

    Original languageEnglish
    Title of host publicationICAPS 2015 - Proceedings of the 25th International Conference on Automated Planning and Scheduling
    EditorsPatrik Haslum, Carmel Domshlak, Ronen Brafman, Shlomo Zilberstein
    PublisherAAAI Press
    Pages7-15
    Number of pages9
    ISBN (Electronic)9781577357315
    DOIs
    Publication statusPublished - 4 Aug 2015
    Event25th International Conference on Automated Planning and Scheduling, ICAPS 2015 - Jerusalem, Israel
    Duration: 7 Jun 201511 Jun 2015

    Publication series

    NameProceedings International Conference on Automated Planning and Scheduling, ICAPS
    Volume2015-January
    ISSN (Print)2334-0835
    ISSN (Electronic)2334-0843

    Conference

    Conference25th International Conference on Automated Planning and Scheduling, ICAPS 2015
    Country/TerritoryIsrael
    CityJerusalem
    Period7/06/1511/06/15

    Fingerprint

    Dive into the research topics of 'Tight bounds for HTN planning'. Together they form a unique fingerprint.

    Cite this