Differences between revisions 13 and 36 (spanning 23 versions)
Revision 13 as of 2016-05-13 13:59:41
Size: 2742
Editor: XmlRpcBot
Comment:
Revision 36 as of 2024-01-11 22:26:37
Size: 4380
Editor: XmlRpcBot
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
== Merge strategy DFP == == Precomputed merge strategy ==
Line 7: Line 7:
This merge strategy implements the algorithm originally described in the paper "Directed model checking with distance-preserving abstractions" by Draeger, Finkbeiner and Podelski (SPIN 2006), adapted to planning in the following paper: This merge strategy has a precomputed merge tree. Note that this merge strategy does not take into account the current state of the factored transition system. This also means that this merge strategy relies on the factored transition system being synchronized with this merge tree, i.e. all merges are performed exactly as given by the merge tree.

{{{
merge_precomputed(merge_tree, verbosity=normal)
}}}

 * ''merge_tree'' ([[Doc/MergeTree|MergeTree]]): The precomputed merge tree.
 * ''verbosity'' ({silent, normal, verbose, debug}): Option to specify the verbosity level.
     * {{{silent}}}: only the most basic output
     * {{{normal}}}: relevant information to monitor progress
     * {{{verbose}}}: full output
     * {{{debug}}}: like verbose with additional debug output

'''Note:''' An example of a precomputed merge startegy is a linear merge strategy, which can be obtained using:
{{{
merge_strategy=merge_precomputed(merge_tree=linear(<variable_order>))
}}}

== Merge strategy SSCs ==

This merge strategy implements the algorithm described in the paper
Line 10: Line 30:
 [[http://ai.cs.unibas.ch/papers/sievers-et-al-aaai2014.pdf|Generalized Label Reduction for Merge-and-Shrink Heuristics]].<<BR>>
 In ''Proceedings of the 28th AAAI Conference on Artificial Intelligence (AAAI 2014)'', pp. 2358-2366. AAAI Press 2014.
 [[https://ai.dmi.unibas.ch/papers/sievers-et-al-icaps2016.pdf|An Analysis of Merge Strategies for Merge-and-Shrink Heuristics]].<<BR>>
 In ''Proceedings of the 26th International Conference on Planning and Scheduling (ICAPS 2016)'', pp. 2358-2366. AAAI Press, 2016.

In a nutshell, it computes the maximal SCCs of the causal graph, obtaining a partitioning of the task's variables. Every such partition is then merged individually, using the specified fallback merge strategy, considering the SCCs in a configurable order. Afterwards, all resulting composite abstractions are merged to form the final abstraction, again using the specified fallback merge strategy and the configurable order of the SCCs.
Line 14: Line 36:
merge_dfp(atomic_ts_order=regular, product_ts_order=new_to_old, atomic_before_product=false, randomized_order=false, random_seed=-1) merge_sccs(order_of_sccs=topological, merge_tree=<none>, merge_selector=<none>, verbosity=normal)
Line 17: Line 39:
 * ''atomic_ts_order'' ({regular, inverse, random}): The order in which atomic transition systems are considered when considering pairs of potential merges.
  * {{{regular}}}: the variable order of Fast Downward
  * {{{inverse}}}: opposite of regular
  * {{{random}}}: a randomized order
 * ''product_ts_order'' ({old_to_new, new_to_old, random}): The order in which product transition systems are considered when considering pairs of potential merges.
  * {{{old_to_new}}}: consider composite transition systems from most recent to oldest, that is in decreasing index order
  * {{{new_to_old}}}: opposite of old_to_new
  * {{{random}}}: a randomized order
 * ''atomic_before_product'' (bool): Consider atomic transition systems before composite ones iff true.
 * ''randomized_order'' (bool): If true, use a 'globally' randomized order, i.e. all transition systems are considered in an arbitrary order. This renders all other ordering options void.
 * ''random_seed'' (int [-1, infinity]): Set to -1 (default) to use the global random number generator. Set to any other value to use a local random number generator with the given seed.
== Linear merge strategies ==
This merge strategy implements several linear merge orders, which are described in the paper:
 * ''order_of_sccs'' ({topological, reverse_topological, decreasing, increasing}): how the SCCs should be ordered
     * {{{topological}}}: according to the topological ordering of the directed graph where each obtained SCC is a 'supervertex'
     * {{{reverse_topological}}}: according to the reverse topological ordering of the directed graph where each obtained SCC is a 'supervertex'
     * {{{decreasing}}}: biggest SCCs first, using 'topological' as tie-breaker
     * {{{increasing}}}: smallest SCCs first, using 'topological' as tie-breaker
 * ''merge_tree'' ([[Doc/MergeTree|MergeTree]]): the fallback merge strategy to use if a precomputed strategy should be used.
 * ''merge_selector'' ([[Doc/MergeSelector|MergeSelector]]): the fallback merge strategy to use if a stateless strategy should be used.
 * ''verbosity'' ({silent, normal, verbose, debug}): Option to specify the verbosity level.
     * {{{silent}}}: only the most basic output
     * {{{normal}}}: relevant information to monitor progress
     * {{{verbose}}}: full output
     * {{{debug}}}: like verbose with additional debug output
Line 31: Line 52:
 * Malte Helmert, Patrik Haslum and Joerg Hoffmann.<<BR>>
 [[http://ai.cs.unibas.ch/papers/helmert-et-al-icaps2007.pdf|Flexible Abstraction Heuristics for Optimal Sequential Planning]].<<BR>>
 In ''Proceedings of the Seventeenth International Conference on Automated Planning and Scheduling (ICAPS 2007)'', pp. 176-183. 2007.
== Stateless merge strategy ==

This merge strategy has a merge selector, which computes the next merge only depending on the current state of the factored transition system, not requiring any additional information.
Line 36: Line 57:
merge_linear(variable_order=CG_GOAL_LEVEL) merge_stateless(merge_selector, verbosity=normal)
Line 39: Line 60:
 * ''variable_order'' ({CG_GOAL_LEVEL, CG_GOAL_RANDOM, GOAL_CG_LEVEL, RANDOM, LEVEL, REVERSE_LEVEL}): the order in which atomic transition systems are merged  * ''merge_selector'' ([[Doc/MergeSelector|MergeSelector]]): The merge selector to be used.
 * ''verbosity'' ({silent, normal, verbose, debug}): Option to specify the verbosity level.
     * {{{silent}}}: only the most basic output
     * {{{normal}}}: relevant information to monitor progress
     * {{{verbose}}}: full output
     * {{{debug}}}: like verbose with additional debug output
Line 41: Line 67:
/* moin code generated by txt2tags 2.6b (http://txt2tags.sf.net) */
/* cmdline: txt2tags */
'''Note:''' Examples include the DFP merge strategy, which can be obtained using:
{{{
merge_strategy=merge_stateless(merge_selector=score_based_filtering(scoring_functions=[goal_relevance,dfp,total_order(<order_option>))]))
}}}
and the (dynamic/score-based) MIASM strategy, which can be obtained using:
{{{
merge_strategy=merge_stateless(merge_selector=score_based_filtering(scoring_functions=[sf_miasm(<shrinking_options>),total_order(<order_option>)]
}}}

This page describes the various merge strategies supported by the planner.

Precomputed merge strategy

This merge strategy has a precomputed merge tree. Note that this merge strategy does not take into account the current state of the factored transition system. This also means that this merge strategy relies on the factored transition system being synchronized with this merge tree, i.e. all merges are performed exactly as given by the merge tree.

merge_precomputed(merge_tree, verbosity=normal)
  • merge_tree (MergeTree): The precomputed merge tree.

  • verbosity ({silent, normal, verbose, debug}): Option to specify the verbosity level.

    • silent: only the most basic output

    • normal: relevant information to monitor progress

    • verbose: full output

    • debug: like verbose with additional debug output

Note: An example of a precomputed merge startegy is a linear merge strategy, which can be obtained using:

merge_strategy=merge_precomputed(merge_tree=linear(<variable_order>))

Merge strategy SSCs

This merge strategy implements the algorithm described in the paper

In a nutshell, it computes the maximal SCCs of the causal graph, obtaining a partitioning of the task's variables. Every such partition is then merged individually, using the specified fallback merge strategy, considering the SCCs in a configurable order. Afterwards, all resulting composite abstractions are merged to form the final abstraction, again using the specified fallback merge strategy and the configurable order of the SCCs.

merge_sccs(order_of_sccs=topological, merge_tree=<none>, merge_selector=<none>, verbosity=normal)
  • order_of_sccs ({topological, reverse_topological, decreasing, increasing}): how the SCCs should be ordered

    • topological: according to the topological ordering of the directed graph where each obtained SCC is a 'supervertex'

    • reverse_topological: according to the reverse topological ordering of the directed graph where each obtained SCC is a 'supervertex'

    • decreasing: biggest SCCs first, using 'topological' as tie-breaker

    • increasing: smallest SCCs first, using 'topological' as tie-breaker

  • merge_tree (MergeTree): the fallback merge strategy to use if a precomputed strategy should be used.

  • merge_selector (MergeSelector): the fallback merge strategy to use if a stateless strategy should be used.

  • verbosity ({silent, normal, verbose, debug}): Option to specify the verbosity level.

    • silent: only the most basic output

    • normal: relevant information to monitor progress

    • verbose: full output

    • debug: like verbose with additional debug output

Stateless merge strategy

This merge strategy has a merge selector, which computes the next merge only depending on the current state of the factored transition system, not requiring any additional information.

merge_stateless(merge_selector, verbosity=normal)
  • merge_selector (MergeSelector): The merge selector to be used.

  • verbosity ({silent, normal, verbose, debug}): Option to specify the verbosity level.

    • silent: only the most basic output

    • normal: relevant information to monitor progress

    • verbose: full output

    • debug: like verbose with additional debug output

Note: Examples include the DFP merge strategy, which can be obtained using:

merge_strategy=merge_stateless(merge_selector=score_based_filtering(scoring_functions=[goal_relevance,dfp,total_order(<order_option>))]))

and the (dynamic/score-based) MIASM strategy, which can be obtained using:

merge_strategy=merge_stateless(merge_selector=score_based_filtering(scoring_functions=[sf_miasm(<shrinking_options>),total_order(<order_option>)]

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