Issue753

Title ugly hacks
Priority meta Status chatting
Superseder Nosy List florian, guillem, jendrik, malte, silvan
Assigned To Keywords
Optional summary
1. The "pref=..." option of the lmcount heuristic (see
http://www.fast-downward.org/OptionCaveats).
2. The "cost_type" and "lm_cost_type" options in the landmark code (issue697 
and see
http://www.fast-downward.org/OptionCaveats).
3. The multi-path dependency code (issue198).
4. The global copy of the initial state data and the complex way of 
initializing
it (see msg5101 and issue509).

Created on 2017-11-30.17:37:10 by malte, last changed by silvan.

Summary
1. The "pref=..." option of the lmcount heuristic (see
http://www.fast-downward.org/OptionCaveats).
2. The "cost_type" and "lm_cost_type" options in the landmark code (issue697 
and see
http://www.fast-downward.org/OptionCaveats).
3. The multi-path dependency code (issue198).
4. The global copy of the initial state data and the complex way of 
initializing
it (see msg5101 and issue509).
Messages
msg6669 (view) Author: florian Date: 2017-12-01.08:27:21
The initial state data is stored globally without axioms evaluated and is
accessed when constructing state registries in a very intricate way where the
task constructs a StateRegistry that accesses the task itself but gets the state
data on a separate channel to avoid an endless loop (see msg5101 and issue509).
msg6664 (view) Author: jendrik Date: 2017-11-30.18:55:29
Reference issue697.
msg6661 (view) Author: malte Date: 2017-11-30.17:37:24
Fix typo in summary.
msg6660 (view) Author: malte Date: 2017-11-30.17:37:10
This meta issue collects ugly hacks that we would like to get rid of.

It is meant mainly for things where the usual concepts in the code are violated
in some way and hence work-arounds are required, especially when these are
visible on the user level.

For example, usually a heuristic object doesn't care whether it's going to be
used for preferred operators, but if it is the landmark heuristic, it does care,
and the user needs to specify a special option. Also, the way that action cost
modifications are specified usually makes some sense, but it doesn't in the case
of the landmark heuristic and/or landmark synergy.
History
Date User Action Args
2017-12-01 15:50:58silvansetnosy: + silvan
2017-12-01 11:47:08guillemsetnosy: + guillem
summary: 1. The "pref=..." option of the lmcount heuristic (see http://www.fast-downward.org/OptionCaveats). 2. The "cost_type" and "lm_cost_type" options in the landmark code (issue697 and see http://www.fast-downward.org/OptionCaveats). 3. The multi-path dependency code (issue198). 4. The global copy of the initial state data and the complex way of initializing it (see msg5101 and issue509). -> 1. The "pref=..." option of the lmcount heuristic (see http://www.fast-downward.org/OptionCaveats). 2. The "cost_type" and "lm_cost_type" options in the landmark code (issue697 and see http://www.fast-downward.org/OptionCaveats). 3. The multi-path dependency code (issue198). 4. The global copy of the initial state data and the complex way of initializing it (see msg5101 and issue509).
2017-12-01 08:27:21floriansetnosy: + florian
messages: + msg6669
summary: 1. The "pref=..." option of the lmcount heuristic (see http://www.fast-downward.org/OptionCaveats). 2. The "cost_type" and "lm_cost_type" options in the landmark code (issue697 and see http://www.fast-downward.org/OptionCaveats). 3. The multi-path dependency code (issue198). -> 1. The "pref=..." option of the lmcount heuristic (see http://www.fast-downward.org/OptionCaveats). 2. The "cost_type" and "lm_cost_type" options in the landmark code (issue697 and see http://www.fast-downward.org/OptionCaveats). 3. The multi-path dependency code (issue198). 4. The global copy of the initial state data and the complex way of initializing it (see msg5101 and issue509).
2017-11-30 18:55:29jendriksetmessages: + msg6664
summary: 1. The "pref=..." option of the lmcount heuristic (see http://www.fast-downward.org/OptionCaveats). 2. The "cost_type" and "lm_cost_type" options in the landmark code (see http://www.fast-downward.org/OptionCaveats). 3. The multi-path dependency code (issue198). -> 1. The "pref=..." option of the lmcount heuristic (see http://www.fast-downward.org/OptionCaveats). 2. The "cost_type" and "lm_cost_type" options in the landmark code (issue697 and see http://www.fast-downward.org/OptionCaveats). 3. The multi-path dependency code (issue198).
2017-11-30 17:41:14jendriksetnosy: + jendrik
2017-11-30 17:37:24maltesetmessages: + msg6661
summary: 1. The "pref=..." option of the lmcount heuristic (see http://www.fast-downward.org/OptionCaveats). 2. The "cost_type" and "lm_cost_type" options in the landmark code (eee http://www.fast-downward.org/OptionCaveats). 3. The multi-path dependency code (issue198). -> 1. The "pref=..." option of the lmcount heuristic (see http://www.fast-downward.org/OptionCaveats). 2. The "cost_type" and "lm_cost_type" options in the landmark code (see http://www.fast-downward.org/OptionCaveats). 3. The multi-path dependency code (issue198).
2017-11-30 17:37:10maltecreate