|
Size: 837
Comment:
|
Size: 839
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 9: | Line 9: |
| Unlike all other (current) heuristics, the landmark heuristics ({{{landmark_sum}}} and {{{landmark_cost_partitioning}}}, see [[Doc/Evaluator#Landmark_sum_heuristic]] and [[Doc/Evaluator#Landmark_cost_partitioning_heuristic) require a special setting {{{pref=true}}} to enable preferred operator support. Hence, to use preferred operators with these heuristics, '''two''' things must be done at the moment: | Unlike all other (current) heuristics, the landmark heuristics ({{{landmark_sum}}} and {{{landmark_cost_partitioning}}}, see [[Doc/Evaluator#Landmark_sum_heuristic]] and [[Doc/Evaluator#Landmark_cost_partitioning_heuristic]]) require a special setting {{{pref=true}}} to enable preferred operator support. Hence, to use preferred operators with these heuristics, '''two''' things must be done at the moment: |
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 heuristics (landmark_sum and landmark_cost_partitioning, see Doc/Evaluator#Landmark_sum_heuristic and Doc/Evaluator#Landmark_cost_partitioning_heuristic) require a special setting pref=true to enable preferred operator support. Hence, to use preferred operators with these heuristics, two things must be done at the moment:
Set pref=true in the heuristic specification.
Include the heuristic in the list of heuristics in the preferred specification of the search engine.