Title Remove hack for initial state in lazy search
Priority wish Status resolved
Superseder Nosy List florian, jendrik, malte
Assigned To florian Keywords
Optional summary

Created on 2017-11-27.21:21:50 by florian, last changed by florian.

msg6625 (view) Author: florian Date: 2017-11-28.15:01:10
Merged, thanks.
msg6624 (view) Author: malte Date: 2017-11-28.11:44:06
Looks good to merge.
msg6623 (view) Author: florian Date: 2017-11-28.10:04:39
I ran a lazy greedy blind search, lama-first, and a lazy weighted A*
search with a weight of 5 and h^FF as a heuristic and for preferred

There were some issues on the grid with a couple of tasks (I suspect
most of this is caused by VAL crashing on some PSR plans). Across the
~15000 runs, 5 changed between running out of memory and running out of
time (in both directions). I think this could reasonably be tasks that
are close to both limits. Other than that, I don't see a large
difference in time or memory, and no difference in the
expanded/evaluated states or coverage.

I think we can merge this.
msg6621 (view) Author: malte Date: 2017-11-28.00:11:24
Looks plausible, I'll leave it to the experiments to show the details. :-)
The suggested experiment looks good, but please also include a configuration
with reopening, e.g. using lazy weighted A*.
msg6616 (view) Author: florian Date: 2017-11-27.23:04:53
I prepared a pull request on Bitbucket for this:

Its a nice local change and actually makes the code shorter by 4 lines. The new
code should be equivalent but lookup_state is now called twice. I don't think
this matters, as it is basically an array access.

I also switched
  "if (reopen) {...} else if (initial state) {...}"
  "if (initial state) {...} else if (reopen) {...}"
The two cases are mutually exclusive but even if they were not, the new version
would be the way to go anyway.

What kind of experiments should I run for this? Would lama-first and blind on
the satisficing suite be OK?
msg6615 (view) Author: florian Date: 2017-11-27.21:21:50
The lazy search creates a dummy parent for the initial state which causes issues
with the switch to the task interface. Rather than working around the hack, I
would like to try and remove it by handling the initial state separately from
other states.
Date User Action Args
2017-11-28 15:01:10floriansetstatus: chatting -> resolved
messages: + msg6625
2017-11-28 11:44:06maltesetmessages: + msg6624
2017-11-28 10:04:39floriansetmessages: + msg6623
2017-11-28 00:11:24maltesetmessages: + msg6621
2017-11-27 23:04:53floriansetstatus: unread -> chatting
messages: + msg6616
2017-11-27 21:21:50floriancreate