1431
Comment:
|
1915
|
Deletions are marked like this. | Additions are marked like this. |
Line 9: | Line 9: |
For mostly historical reasons, specifying the cost type (see HeuristicSpecification) for landmark heuristics is currently complicated. Here's the complete set of rules: | For mostly historical reasons, specifying the cost type (see [[Doc/Heuristic]]) for landmark heuristics is currently complicated. Here's the complete set of rules: |
Line 13: | Line 13: |
There are three relevant options: | There are two relevant options: |
Line 15: | Line 15: |
1. {{{lm_cost_type}}} of the landmark generation method (e.g. {{{lm_rhw}}}) 2. {{{cost_type}}} of the landmark generation method (e.g. {{{lm_rhw}}}) 3. {{{cost_type}}} of the synergy declation ({{{lm_ff_syn}}}) |
1. {{{lm_cost_type}}} of the landmark generation method (currently only used by {{{lm_rhw}}}) 2. {{{transform}}} of the synergy declaration ({{{lm_ff_syn}}}). Pass e.g. {{{transform=adapt_costs(one)}}} for unit costs. |
Line 19: | Line 18: |
The cost type of the synergy's landmark heuristic is determined by option 1. when using {{{admissible=false}}} and by option 3. when using {{{admissible=true}}}. | The cost type of the synergy's landmark heuristic is determined by option 1. when using {{{admissible=false}}} and by option 2. when using {{{admissible=true}}}. |
Line 21: | Line 20: |
The cost type of the synergy's FF heuristic is determined by option 2. /!\ | The cost type of the synergy's FF heuristic is determined by option 2. |
Line 25: | Line 24: |
There are three relevant options: | There are two relevant options: |
Line 27: | Line 26: |
1. {{{lm_cost_type}}} of the landmark generation method (e.g. {{{lm_rhw}}}) 2. {{{cost_type}}} of the landmark generation method (e.g. {{{lm_rhw}}}) 3. {{{cost_type}}} of the landmark heuristic declation ({{{lmcount}}}) |
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. |
Line 31: | Line 29: |
The cost type of the landmark heuristic is determined by option 1. when using {{{admissible=false}}} and by option 3. when using {{{admissible=true}}}. | The cost type of the landmark heuristic is determined by option 1. when using {{{admissible=false}}} and by option 2. when using {{{admissible=true}}}. |
Line 33: | Line 31: |
Option 2 is ignored in this case. | == 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]]. 2. Include the heuristic in the list of heuristics in the {{{preferred}}} specification of the [[Doc/SearchEngine|search engine]]. |
Back to the HomePage.
Caveats for the options
Here, we document some aspects of the command-line syntax that may be unintuitive or complicated.
Setting the "cost type" for landmark heuristics
For mostly historical reasons, specifying the cost type (see Doc/Heuristic) for landmark heuristics is currently complicated. Here's the complete set of rules:
If you use the LAMA-FF synergy
There are two relevant options:
lm_cost_type of the landmark generation method (currently only used by lm_rhw)
transform of the synergy declaration (lm_ff_syn). Pass e.g. transform=adapt_costs(one) for unit costs.
The cost type of the synergy's landmark heuristic is determined by option 1. when using admissible=false and by option 2. when using admissible=true.
The cost type of the synergy's FF heuristic is determined by option 2.
If you do not use the LAMA-FF synergy
There are two relevant options:
lm_cost_type of the landmark generation method (currently only used by lm_rhw)
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.
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:
Set pref=true in the heuristic specification.
Include the heuristic in the list of heuristics in the preferred specification of the search engine.