Differences between revisions 11 and 14 (spanning 3 versions)
Revision 11 as of 2018-02-09 11:04:06
Size: 1517
Comment:
Revision 14 as of 2018-09-20 23:43:46
Size: 738
Comment: lm_cost_type was removed in issue776
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
== Setting the "cost type" for landmark heuristics == == Using "preferred operators" with landmark heuristics ==
Line 9: Line 9:
For mostly historical reasons, specifying the cost type (see [[Doc/Heuristic]]) for landmark heuristics is currently complicated. Here's the complete set of rules: Unlike all other (current) heuristics, the landmark heuristic ({{{lmcount}}}, see [[Doc/Evaluator#Landmark-count_heuristic]]) requires a special setting {{{pref=true}}} to enable preferred operator support. Hence, to use preferred operators with that heuristic, '''two''' things must be done at the moment:
Line 11: Line 11:
There are two relevant options:

 1. {{{lm_cost_type}}} of the landmark generation method (currently only used by {{{lm_rhw}}})
 2. {{{transform}}} of the landmark heuristic declaration ({{{lmcount}}}). Pass e.g. {{{transform=adapt_costs(one)}}} for unit costs.

The cost type of the landmark heuristic is determined by option 1. when using {{{admissible=false}}} and by option 2. when using {{{admissible=true}}}.

'''Note:''' Setting the cost type for the LAMA-FF synergy's master follows the same rules as the landmark heuristic. The cost type of the synergy's FF heuristic is determined by option 2.

== Using preferred operators with the lmcount heuristic ==

Unlike all other (current) heuristics, the {{{lmcount}}} heuristic requires a special setting {{{pref=true}}} to enable preferred operator support. Hence, to use preferred operators with that heuristic, '''two''' things must be done at the moment:

 1. Set {{{pref=true}}} in the [[Doc/Heuristic| heuristic specification]].
 1. Set {{{pref=true}}} in the [[Doc/Evaluator| heuristic specification]].

Back to the HomePage.

Caveats for the options

Here, we document some aspects of the command-line syntax that may be unintuitive or complicated.

Using "preferred operators" with landmark heuristics

Unlike all other (current) heuristics, the landmark heuristic (lmcount, see Doc/Evaluator#Landmark-count_heuristic) requires a special setting pref=true to enable preferred operator support. Hence, to use preferred operators with that heuristic, two things must be done at the moment:

  1. Set pref=true in the heuristic specification.

  2. Include the heuristic in the list of heuristics in the preferred specification of the search engine.