Identifying and exploiting features for effective plan retrieval in case-based planning

Mauro Vallati, Ivan Serina, Alessandro Saetti, Alfonso E. Gerevini

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

3 Citations (Scopus)

Abstract

Case-Based planning can fruitfully exploit knowledge gained by solving a large number of problems, storing the corresponding solutions in a plan library and reusing them for solving similar planning problems in the future. Case-based planning is extremely effective when similar reuse candidates can be efficiently chosen. In this paper, we study an innovative technique based on planning problem features for efficiently retrieving solved planning problems (and relative plans) from large plan libraries. Since existing planning features are not always able to effectively distinguish between problems within the same planning domain, we introduce a new class of features. Our experimental analysis shows that the proposed features-based retrieval approach can significantly improve the performance of a state-of-theart case-based planning system.

Original languageEnglish
Title of host publicationProceedings of the 25th International Conference on Automated Planning and Scheduling (ICAPS 2015)
EditorsRonen Brafman, Carmel Domshlak, Patrik Haslum, Shlomo Zilberstein
PublisherAAAI press
Pages239-243
Number of pages5
ISBN (Electronic)9781577357315
Publication statusPublished - Apr 2015
Event25th International Conference on Automated Planning and Scheduling - Jerusalem, Israel
Duration: 7 Jun 201511 Jun 2015
Conference number: 25
http://icaps15.icaps-conference.org (Link to Conference Website )

Conference

Conference25th International Conference on Automated Planning and Scheduling
Abbreviated titleICAPS 2015
Country/TerritoryIsrael
CityJerusalem
Period7/06/1511/06/15
Internet address

Fingerprint

Dive into the research topics of 'Identifying and exploiting features for effective plan retrieval in case-based planning'. Together they form a unique fingerprint.

Cite this