Issue80

Title Updating parent pointer without reopening in eager GBFS causes incompatibility between g-value and path from initial state
Priority wish Status resolved
Superseder Nosy List erez, malte
Assigned To erez Keywords 1.0
Optional summary

Created on 2010-03-10.10:14:30 by erez, last changed by erez.

Messages
msg289 (view) Author: malte Date: 2010-03-22.12:47:10
We should update the parent and update the g value for *that* node, and add a
comment that g values can be too large if we don't reopen closed nodes (because
they are the g values at the time the node was generated). Sounds better than
producing a longer plan than necessary.
msg272 (view) Author: erez Date: 2010-03-10.10:14:29
I noticed that for some states, the g-value and and path found using trace_path()
are not consistent, when using eager GBFS.
This does not happen when I remove the update_parent() call, so I commented it
out for now.
History
Date User Action Args
2010-03-22 15:02:47erezsetstatus: deferred -> resolved
2010-03-22 14:31:45maltesetkeyword: + 1.0
2010-03-22 12:47:13maltesetassignedto: erez
2010-03-22 12:47:10maltesetmessages: + msg289
2010-03-22 12:44:11maltesetnosy: + malte
2010-03-10 10:14:30erezcreate