Issue52

Title change progress statistics in eager search
Priority feature Status resolved
Superseder Nosy List erez, malte
Assigned To erez Keywords 1.0
Optional summary

Created on 2009-11-27.17:05:33 by malte, last changed by malte.

Messages
msg304 (view) Author: erez Date: 2010-03-22.15:52:21
Done
msg303 (view) Author: malte Date: 2010-03-22.15:34:57
Ah, sorry, I should have read the old messages. I think I still find this a bit
confusing...

I think it would help to make the messages more verbose by mentioning the g and
h value for the "new best" expanded state in the "Best heuristic" line. Then it
would be clear to the reader that they belong to a different f layer. Can you
add that?
msg302 (view) Author: erez Date: 2010-03-22.15:28:38
The reported numbers are correct (and always have been as far as I know).
It's just that the check for best-heuristic-value is done when a state is
generated, and for f-value when a state is expanded.
msg301 (view) Author: malte Date: 2010-03-22.15:26:34
Are they messages clear about what they refer to? Down in the first comment, it says
    Best heuristic value: 6 [expanded 103753 state(s)]
which would be a terrible message if it referred to generated and not expanded
states!
msg300 (view) Author: erez Date: 2010-03-22.15:09:11
The f-message still refer to expanded states and the best-heuristic-value
message still refer to generated states, but this is just because these are the
places where these things matter.
The output looks the same now (also between different searches).
Malte - I guess it's up to you. If you want to do something else (maybe don't
output best-heuristic-value message in A*)?
msg296 (view) Author: malte Date: 2010-03-22.14:32:25
Erez, would you say this is done?
msg290 (view) Author: erez Date: 2010-03-22.12:49:15
Added a SearchProgress class which is used by all searches
msg142 (view) Author: malte Date: 2009-11-27.17:05:33
The progress statistics in the eager search algorithm are currently a bit
confusing because some of them refer to *expanded* states, others to *generated*
states. For example, consider this fragment of output in the Elevators domain
(option "ou"):

f = 47 [551962 evaluated, 52462 expanded, 64 reopened, t=159.9s]
f = 48 [768713 evaluated, 76110 expanded, 64 reopened, t=222.63s]
f = 49 [1018454 evaluated, 103685 expanded, 64 reopened, t=295.17s]
Best heuristic value: 6 [expanded 103753 state(s)]
f = 50 [1362992 evaluated, 138060 expanded, 80 reopened, t=393.26s]
f = 51 [1916551 evaluated, 192159 expanded, 84 reopened, t=553.87s]
Best heuristic value: 0 [expanded 192172 state(s)]
f = 52 [2571654 evaluated, 255295 expanded, 116 reopened, t=742.23s]

The "f = ..." output lines correspond to expanded states, but the "Best
heuristic value: ..." lines correspond to generated states. That's somewhat
confusing, as it would be natural to assume that the lines after something like
"f = 51" correspond to states that belong *to that f layer*, which is not the case.

Suggested change: Only create output for *expanded* states, not generated states.
History
Date User Action Args
2010-03-22 16:14:10maltesetstatus: in-progress -> resolved
2010-03-22 15:52:21erezsetmessages: + msg304
2010-03-22 15:34:57maltesetmessages: + msg303
2010-03-22 15:28:38erezsetmessages: + msg302
2010-03-22 15:26:34maltesetmessages: + msg301
2010-03-22 15:09:11erezsetmessages: + msg300
2010-03-22 14:32:25maltesetstatus: testing -> in-progress
priority: wish -> feature
messages: + msg296
2010-03-22 14:32:00maltesetassignedto: erez
2010-03-22 14:31:51maltesetkeyword: + 1.0
2010-03-22 12:49:15erezsetstatus: chatting -> testing
messages: + msg290
2010-01-09 21:08:37maltesetstatus: unread -> chatting
2009-11-27 17:05:33maltecreate