Issue76

Title admissible landmarks: optimal cost partitioning gives worse heuristic values than uniform
Priority bug Status resolved
Superseder Nosy List erez, malte, silvia
Assigned To erez Keywords 1.0
Optional summary

Created on 2010-02-16.17:26:01 by malte, last changed by erez.

Messages
msg251 (view) Author: malte Date: 2010-02-16.21:44:02
I've implemented the optimal cost partitioning in a way that hopefully takes the
first achievers into account in r3932 of the emil-new branch. Note that there
are many other differences between this branch and the trunk, e.g. to do with
action landmarks, and the cost assignment method cannot be used directly in the
trunk since the way in which it is called is different in that branch.
msg249 (view) Author: erez Date: 2010-02-16.17:51:49
Sounds good
msg248 (view) Author: malte Date: 2010-02-16.17:50:47
OK, we'll have to rewrite that code in the "emil-new" branch anyway for
conjunctive LM support, so I'll leave the trunk alone for you to decide what to
do about it.

Generally speaking, we made a bunch of changes to the landmarks code in that
branch, some of which are worth considering for the trunk (e.g. see issue74). We
cannot merge them easily since we also threw away several features, though.

How about discussing the landmark-related things after the ECAI deadline?
msg246 (view) Author: erez Date: 2010-02-16.17:45:35
I can reproduce this, and the assumption about first achievers seems correct.
Using the old LP formulation yields a better estimate the uniform cost sharing.
msg244 (view) Author: malte Date: 2010-02-16.17:31:50
PS: If there indeed is a problem in trunk, it's probably hidden by default
because action landmarks take care of this for the given Blocks instance. But it
should show up if you can disable action landmarks in some way.
msg243 (view) Author: malte Date: 2010-02-16.17:26:01
In the emil-new branch, "olsp" gives a worse init h value (4) than "ols" (6) on
blocks problem 4-1. I cannot test this on trunk at the moment as I'd have to
mess with the Makefile to set up the LP solver there; Erez, can you reproduce this?

A possible explanation is that the new LP formulation doesn't distinguish
between first achievers and achievers, and hence it thinks that it can achieve
"clear(c)" and "on(c, a)" together even though it can't, and similarly for
"clear(d)" and "on(d, c)". (There exist operators that are *achievers* of both
clear(c) and on(c, a), but not *first* achievers.)
History
Date User Action Args
2010-03-22 14:46:59erezsetstatus: chatting -> resolved
2010-03-22 14:34:13maltesetkeyword: + 1.0
2010-03-22 12:09:00maltesetassignedto: erez
2010-02-16 21:44:02maltesetmessages: + msg251
2010-02-16 17:51:49erezsetmessages: + msg249
2010-02-16 17:50:47maltesetnosy: + silvia
messages: + msg248
2010-02-16 17:45:35erezsetmessages: + msg246
2010-02-16 17:31:50maltesetstatus: unread -> chatting
messages: + msg244
2010-02-16 17:26:01maltecreate