Differences between revisions 1 and 10 (spanning 9 versions)
Revision 1 as of 2016-04-11 16:44:31
Size: 2348
Editor: XmlRpcBot
Comment:
Revision 10 as of 2020-05-12 17:01:09
Size: 8513
Editor: XmlRpcBot
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
== Atom-centric stubborn sets ==

Stubborn sets are a state pruning method which computes a subset of applicable actions in each state such that completeness and optimality of the overall search is preserved. Previous stubborn set implementations mainly track information about actions. In contrast, this implementation focuses on atomic propositions (atoms), which often speeds up the computation on IPC benchmarks. For details, see

 * Gabriele Roeger, Malte Helmert, Jendrik Seipp and Silvan Sievers.<<BR>>
 [[https://ai.dmi.unibas.ch/papers/roeger-et-al-socs2020.pdf|An Atom-Centric Perspective on Stubborn Sets]].<<BR>>
 In ''Proceedings of the 13th Annual Symposium on Combinatorial Search (SoCS 2020)''. AAAI Press, 2020.

{{{
atom_centric_stubborn_sets(use_sibling_shortcut=true, atom_selection_strategy=quick_skip, min_required_pruning_ratio=0.0, expansions_before_checking_pruning_ratio=1000)
}}}

 * ''use_sibling_shortcut'' (bool): use variable-based marking in addition to atom-based marking
 * ''atom_selection_strategy'' ({fast_downward, quick_skip, static_small, dynamic_small}): Strategy for selecting unsatisfied atoms from action preconditions or the goal atoms. All strategies use the fast_downward strategy for breaking ties.
  * {{{fast_downward}}}: select the atom (v, d) with the variable v that comes first in the Fast Downward variable ordering (which is based on the causal graph)
  * {{{quick_skip}}}: if possible, select an unsatisfied atom whose producers are already marked
  * {{{static_small}}}: select the atom achieved by the fewest number of actions
  * {{{dynamic_small}}}: select the atom achieved by the fewest number of actions that are not yet part of the stubborn set
 * ''min_required_pruning_ratio'' (double [0.0, 1.0]): disable pruning if the pruning ratio is lower than this value after 'expansions_before_checking_pruning_ratio' expansions
 * ''expansions_before_checking_pruning_ratio'' (int [0, infinity]): number of expansions before deciding whether to disable pruning
'''Automatically disable pruning:''' Using stubborn sets to prune operators often reduces the required number of expansions but computing the prunable operators has a non-negligible runtime overhead. Whether the decrease in expansions outweighs the increased computational costs depends on the task at hand. Using the options 'min_required_pruning_ratio' (M) and 'expansions_before_checking_pruning_ratio' (E) it is possible to automatically disable pruning after E expansions if the ratio of pruned vs. non-pruned operators is lower than M. In detail, let B and A be the total number of operators before and after pruning summed over all previous expansions. We call 1-(A/B) the pruning ratio R. If R is lower than M after E expansions, we disable pruning for all subsequent expansions, i.e., consider all applicable operators when generating successor states. By default, pruning is never disabled (min_required_pruning_ratio = 0.0). In experiments on IPC benchmarks, stronger results have been observed with automatic disabling (min_required_pruning_ratio = 0.2, expansions_before_checking_pruning_ratio=1000).
Line 6: Line 28:
Line 8: Line 29:
Line 12: Line 32:
Line 17: Line 38:
 * Martin Wehrle, Malte Helmert, Yusra Alkhazraji and Robert Mattmüller.<<BR>>
 [[The Relative Pruning Power of Strong Stubborn Sets and Expansion Core|http://www.aaai.org/ocs/index.php/ICAPS/ICAPS13/paper/view/6053/6185]].<<BR>>
 In ''Proceedings of the 23rd International Conference on Automated Planning and Scheduling (ICAPS 2013)'', pp. 251-259. AAAI Press 2013.
 * Martin Wehrle, Malte Helmert, Yusra Alkhazraji and Robert Mattmueller.<<BR>>
 [[http://www.aaai.org/ocs/index.php/ICAPS/ICAPS13/paper/view/6053/6185|The Relative Pruning Power of Strong Stubborn Sets and Expansion Core]].<<BR>>
 In ''Proceedings of the 23rd International Conference on Automated Planning and Scheduling (ICAPS 2013)'', pp. 251-259. AAAI Press, 2013.
Line 22: Line 43:
stubborn_sets_ec() stubborn_sets_ec(min_required_pruning_ratio=0.0, expansions_before_checking_pruning_ratio=1000)
Line 25: Line 46:
 * ''min_required_pruning_ratio'' (double [0.0, 1.0]): disable pruning if the pruning ratio is lower than this value after 'expansions_before_checking_pruning_ratio' expansions
 * ''expansions_before_checking_pruning_ratio'' (int [0, infinity]): number of expansions before deciding whether to disable pruning
'''Automatically disable pruning:''' Using stubborn sets to prune operators often reduces the required number of expansions but computing the prunable operators has a non-negligible runtime overhead. Whether the decrease in expansions outweighs the increased computational costs depends on the task at hand. Using the options 'min_required_pruning_ratio' (M) and 'expansions_before_checking_pruning_ratio' (E) it is possible to automatically disable pruning after E expansions if the ratio of pruned vs. non-pruned operators is lower than M. In detail, let B and A be the total number of operators before and after pruning summed over all previous expansions. We call 1-(A/B) the pruning ratio R. If R is lower than M after E expansions, we disable pruning for all subsequent expansions, i.e., consider all applicable operators when generating successor states. By default, pruning is never disabled (min_required_pruning_ratio = 0.0). In experiments on IPC benchmarks, stronger results have been observed with automatic disabling (min_required_pruning_ratio = 0.2, expansions_before_checking_pruning_ratio=1000).
Line 26: Line 51:
Line 29: Line 53:
 * Yusra Alkhazraji, Martin Wehrle, Robert Mattmüller and Malte Helmert.<<BR>>
 [[A Stubborn Set Algorithm for Optimal Planning|http://ai.cs.unibas.ch/papers/alkhazraji-et-al-ecai2012.pdf]].<<BR>>
 In ''Proceedings of the 20th European Conference on Artificial Intelligence (ECAI 2012)'', pp. 891-892. IOS Press 2012.
 * Yusra Alkhazraji, Martin Wehrle, Robert Mattmueller and Malte Helmert.<<BR>>
 [[https://ai.dmi.unibas.ch/papers/alkhazraji-et-al-ecai2012.pdf|A Stubborn Set Algorithm for Optimal Planning]].<<BR>>
 In ''Proceedings of the 20th European Conference on Artificial Intelligence (ECAI 2012)'', pp. 891-892. IOS Press, 2012.
Line 34: Line 58:
 [[Efficient Stubborn Sets: Generalized Algorithms and Selection Strategies|http://www.aaai.org/ocs/index.php/ICAPS/ICAPS14/paper/view/7922/8042]].<<BR>>  [[http://www.aaai.org/ocs/index.php/ICAPS/ICAPS14/paper/view/7922/8042|Efficient Stubborn Sets: Generalized Algorithms and Selection Strategies]].<<BR>>
Line 38: Line 62:
stubborn_sets_simple() stubborn_sets_simple(min_required_pruning_ratio=0.0, expansions_before_checking_pruning_ratio=1000)
Line 41: Line 65:
/* moin code generated by txt2tags 2.6b (http://txt2tags.sf.net) */  * ''min_required_pruning_ratio'' (double [0.0, 1.0]): disable pruning if the pruning ratio is lower than this value after 'expansions_before_checking_pruning_ratio' expansions
 * ''expansions_before_checking_pruning_ratio'' (int [0, infinity]): number of expansions before deciding whether to disable pruning
'''Automatically disable pruning:''' Using stubborn sets to prune operators often reduces the required number of expansions but computing the prunable operators has a non-negligible runtime overhead. Whether the decrease in expansions outweighs the increased computational costs depends on the task at hand. Using the options 'min_required_pruning_ratio' (M) and 'expansions_before_checking_pruning_ratio' (E) it is possible to automatically disable pruning after E expansions if the ratio of pruned vs. non-pruned operators is lower than M. In detail, let B and A be the total number of operators before and after pruning summed over all previous expansions. We call 1-(A/B) the pruning ratio R. If R is lower than M after E expansions, we disable pruning for all subsequent expansions, i.e., consider all applicable operators when generating successor states. By default, pruning is never disabled (min_required_pruning_ratio = 0.0). In experiments on IPC benchmarks, stronger results have been observed with automatic disabling (min_required_pruning_ratio = 0.2, expansions_before_checking_pruning_ratio=1000).

/* moin code generated by txt2tags 2.6 (http://txt2tags.org) */

Prune or reorder applicable operators.

Atom-centric stubborn sets

Stubborn sets are a state pruning method which computes a subset of applicable actions in each state such that completeness and optimality of the overall search is preserved. Previous stubborn set implementations mainly track information about actions. In contrast, this implementation focuses on atomic propositions (atoms), which often speeds up the computation on IPC benchmarks. For details, see

atom_centric_stubborn_sets(use_sibling_shortcut=true, atom_selection_strategy=quick_skip, min_required_pruning_ratio=0.0, expansions_before_checking_pruning_ratio=1000)
  • use_sibling_shortcut (bool): use variable-based marking in addition to atom-based marking

  • atom_selection_strategy ({fast_downward, quick_skip, static_small, dynamic_small}): Strategy for selecting unsatisfied atoms from action preconditions or the goal atoms. All strategies use the fast_downward strategy for breaking ties.

    • fast_downward: select the atom (v, d) with the variable v that comes first in the Fast Downward variable ordering (which is based on the causal graph)

    • quick_skip: if possible, select an unsatisfied atom whose producers are already marked

    • static_small: select the atom achieved by the fewest number of actions

    • dynamic_small: select the atom achieved by the fewest number of actions that are not yet part of the stubborn set

  • min_required_pruning_ratio (double [0.0, 1.0]): disable pruning if the pruning ratio is lower than this value after 'expansions_before_checking_pruning_ratio' expansions

  • expansions_before_checking_pruning_ratio (int [0, infinity]): number of expansions before deciding whether to disable pruning

Automatically disable pruning: Using stubborn sets to prune operators often reduces the required number of expansions but computing the prunable operators has a non-negligible runtime overhead. Whether the decrease in expansions outweighs the increased computational costs depends on the task at hand. Using the options 'min_required_pruning_ratio' (M) and 'expansions_before_checking_pruning_ratio' (E) it is possible to automatically disable pruning after E expansions if the ratio of pruned vs. non-pruned operators is lower than M. In detail, let B and A be the total number of operators before and after pruning summed over all previous expansions. We call 1-(A/B) the pruning ratio R. If R is lower than M after E expansions, we disable pruning for all subsequent expansions, i.e., consider all applicable operators when generating successor states. By default, pruning is never disabled (min_required_pruning_ratio = 0.0). In experiments on IPC benchmarks, stronger results have been observed with automatic disabling (min_required_pruning_ratio = 0.2, expansions_before_checking_pruning_ratio=1000).

No pruning

This is a skeleton method that does not perform any pruning, i.e., all applicable operators are applied in all expanded states.

null()

StubbornSetsEC

Stubborn sets represent a state pruning method which computes a subset of applicable operators in each state such that completeness and optimality of the overall search is preserved. As stubborn sets rely on several design choices, there are different variants thereof. The variant 'StubbornSetsEC' resolves the design choices such that the resulting pruning method is guaranteed to strictly dominate the Expansion Core pruning method. For details, see

stubborn_sets_ec(min_required_pruning_ratio=0.0, expansions_before_checking_pruning_ratio=1000)
  • min_required_pruning_ratio (double [0.0, 1.0]): disable pruning if the pruning ratio is lower than this value after 'expansions_before_checking_pruning_ratio' expansions

  • expansions_before_checking_pruning_ratio (int [0, infinity]): number of expansions before deciding whether to disable pruning

Automatically disable pruning: Using stubborn sets to prune operators often reduces the required number of expansions but computing the prunable operators has a non-negligible runtime overhead. Whether the decrease in expansions outweighs the increased computational costs depends on the task at hand. Using the options 'min_required_pruning_ratio' (M) and 'expansions_before_checking_pruning_ratio' (E) it is possible to automatically disable pruning after E expansions if the ratio of pruned vs. non-pruned operators is lower than M. In detail, let B and A be the total number of operators before and after pruning summed over all previous expansions. We call 1-(A/B) the pruning ratio R. If R is lower than M after E expansions, we disable pruning for all subsequent expansions, i.e., consider all applicable operators when generating successor states. By default, pruning is never disabled (min_required_pruning_ratio = 0.0). In experiments on IPC benchmarks, stronger results have been observed with automatic disabling (min_required_pruning_ratio = 0.2, expansions_before_checking_pruning_ratio=1000).

Stubborn sets simple

Stubborn sets represent a state pruning method which computes a subset of applicable operators in each state such that completeness and optimality of the overall search is preserved. As stubborn sets rely on several design choices, there are different variants thereof. The variant 'StubbornSetsSimple' resolves the design choices in a straight-forward way. For details, see the following papers:

stubborn_sets_simple(min_required_pruning_ratio=0.0, expansions_before_checking_pruning_ratio=1000)
  • min_required_pruning_ratio (double [0.0, 1.0]): disable pruning if the pruning ratio is lower than this value after 'expansions_before_checking_pruning_ratio' expansions

  • expansions_before_checking_pruning_ratio (int [0, infinity]): number of expansions before deciding whether to disable pruning

Automatically disable pruning: Using stubborn sets to prune operators often reduces the required number of expansions but computing the prunable operators has a non-negligible runtime overhead. Whether the decrease in expansions outweighs the increased computational costs depends on the task at hand. Using the options 'min_required_pruning_ratio' (M) and 'expansions_before_checking_pruning_ratio' (E) it is possible to automatically disable pruning after E expansions if the ratio of pruned vs. non-pruned operators is lower than M. In detail, let B and A be the total number of operators before and after pruning summed over all previous expansions. We call 1-(A/B) the pruning ratio R. If R is lower than M after E expansions, we disable pruning for all subsequent expansions, i.e., consider all applicable operators when generating successor states. By default, pruning is never disabled (min_required_pruning_ratio = 0.0). In experiments on IPC benchmarks, stronger results have been observed with automatic disabling (min_required_pruning_ratio = 0.2, expansions_before_checking_pruning_ratio=1000).

FastDownward: Doc/PruningMethod (last edited 2024-01-11 22:26:38 by XmlRpcBot)