Issue697

Title Clarify use of cost type option for landmark ff synergy heuristic
Priority wish Status chatting
Superseder Nosy List cedric, jendrik, malte, manuel, silvan
Assigned To Keywords
Optional summary

Created on 2016-12-19.12:40:33 by manuel, last changed by cedric.

Messages
msg6797 (view) Author: cedric Date: 2018-02-09.12:33:48
The OptionCaveats have changed slightly. To two subsubsections of the subsection
"setting the "cost type" for landmark heuristics" are merged.

The LAMA-FF synergy master follows the same rules for setting the cost type as
the landmark heuristic, so the behavior is the same as reported in msg5903.
The LAMA-FF synergy slave inherits the cost type set by the masters transform
option.
msg6142 (view) Author: malte Date: 2017-02-19.11:18:29
Roundup's URL regexp caught too much. This is the link:

http://www.fast-downward.org/OptionCaveats
msg6141 (view) Author: malte Date: 2017-02-19.11:17:41
When working on this, please also update
http://www.fast-downward.org/OptionCaveats, which is (mostly) about this issue.
msg6140 (view) Author: jendrik Date: 2017-02-19.10:50:08
Done. issue190 is closed.
msg6138 (view) Author: silvan Date: 2017-02-19.10:32:31
Sounds good.
msg6137 (view) Author: jendrik Date: 2017-02-18.23:34:29
I think issue190 and this issue talk about the same problem. Therefore, I suggest 
referencing the content of issue190 here, which is just two links to msg1060 and 
msg1063 and closing issue190 in favor of this newer issue.
msg5903 (view) Author: manuel Date: 2016-12-19.12:41:59
The cost type used by landmark ff synergy heuristic can be set with lm_cost_type
option of landmark heuristic or transform option of synergy declaration:

lm_ff_syn(lm_rhw(lm_cost_type=normal), admissible=false,
transform=adapt_costs(normal))

While for admissible=true Fast Downward uses the transform option and ignores
the lm_cost_type option, for admissible=false both options are considered.
Following example shows the different results of for different options:

openstacks-opt08-strips/p01.pddl
--heuristic "hlm,hff=lm_ff_syn(lm_rhw(lm_cost_type=cost_type), admissible=false,
transform=adapt_costs(cost_type))" 
--search "lazy_greedy([hff,hlm],preferred=[hff,hlm])"

lm_cost_type=cost_type transform=adapt(cost_type) Expansions
normal                 normal                            536
normal                 one                                41
one                    normal                             28
one                    one                                18

We wish to clarify the use of cost type with landmark ff synergy heuristic. If
the heuristic intends to use an unique cost type, we should provide a single
option for cost type in the long term. Otherwise, we should document how the
existing options interleave within the landmark ff synergy heuristic.
History
Date User Action Args
2018-02-09 12:33:48cedricsetnosy: + cedric
messages: + msg6797
2017-02-19 11:18:29maltesetmessages: + msg6142
2017-02-19 11:17:41maltesetmessages: + msg6141
2017-02-19 10:50:08jendriksetmessages: + msg6140
2017-02-19 10:32:31silvansetmessages: + msg6138
2017-02-18 23:34:29jendriksetmessages: + msg6137
2016-12-19 12:51:03silvansetnosy: + silvan
2016-12-19 12:41:59manuelsetstatus: unread -> chatting
messages: + msg5903
summary: The cost type used by landmark ff synergy heuristic can be set with lm_cost_type option of landmark heuristic or transform option of synergy declaration: lm_ff_syn(lm_rhw(lm_cost_type=normal), admissible=false, transform=adapt_costs(normal)) While for admissible=true Fast Downward uses the transform option and ignores the lm_cost_type option, for admissible=false both options are considered. Following example shows the different results of for different options: openstacks-opt08-strips/p01.pddl --heuristic "hlm,hff=lm_ff_syn(lm_rhw(lm_cost_type=cost_type), admissible=false, transform=adapt_costs(cost_type))" --search "lazy_greedy([hff,hlm],preferred=[hff,hlm])" lm_cost_type=cost_type transform=adapt(cost_type) Expansions normal normal 536 normal one 41 one normal 28 one one 18 We wish to clarify the use of cost type with landmark ff synergy heuristic. If the heuristic intends to use an unique cost type, we should provide a single option for cost type in the long term. Otherwise, we should document how the existing options interleave within the landmark ff synergy heuristic. ->
2016-12-19 12:40:33manuelcreate