Issue448

Title add unit-cost/non-unit-cost dispatching to search component
Priority wish Status resolved
Superseder Nosy List malte
Assigned To malte Keywords
Optional summary

Created on 2014-08-03.19:07:48 by malte, last changed by malte.

Messages
msg3267 (view) Author: malte Date: 2014-08-04.21:41:59
Wrong doc link. Correct one:
http://www.fast-downward.org/OptionSyntax#Conditional_options
msg3265 (view) Author: malte Date: 2014-08-04.21:40:21
Merged and documented on http://www.fast-downward.org/PlannerUsage.
msg3263 (view) Author: malte Date: 2014-08-03.20:08:46
Code available on https://bitbucket.org/malte/downward/commits/issue448.
If this is merged, the feature needs to be documented on the wiki.
msg3261 (view) Author: malte Date: 2014-08-03.19:07:48
This is about adding options to the search component that allow specifying
different behaviour for unit-cost and and non-unit-cost problems. Currently, we
only support this for the LAMA 2011 configuration via some special-casing in the
src/search/downward shell script. By adding the functionality directly to the
search component, we can simplify and generalize other code.

See point 2. in msg3259.
History
Date User Action Args
2014-08-04 21:42:13maltesetstatus: chatting -> resolved
2014-08-04 21:42:00maltesetstatus: resolved -> chatting
messages: + msg3267
2014-08-04 21:40:21maltesetstatus: chatting -> resolved
messages: + msg3265
2014-08-03 20:08:46maltesetmessages: + msg3263
2014-08-03 19:07:48maltecreate