Issue467

Title Assertion in LandmarkFactoryRpgSasp fails for unsolvable tasks
Priority bug Status chatting
Superseder Nosy List erez, florian, malte
Assigned To Keywords
Optional summary

Created on 2014-09-17.12:36:33 by florian, last changed by malte.

Messages
msg3516 (view) Author: malte Date: 2014-09-23.19:36:19
I think it should remain open. I'm not sure how soon we'll be able to work on
the landmark code, but I think it should be one of our main priorities.
msg3514 (view) Author: florian Date: 2014-09-23.19:32:38
I added the comment in the master branch. Should we set this issue to deferred,
resolved or leave it open?
msg3428 (view) Author: erez Date: 2014-09-17.15:59:00
Sounds like the landmarks are detecting that the problem is unsolvable, but not 
expecting that. As part of the refactoring it might be good to add an option for 
detecting unsolvability.
msg3427 (view) Author: malte Date: 2014-09-17.14:28:44
Please add a comment to this assertion explaining where it fails. It may not be
a good idea to try fixing this locally. The landmark code needs some more global
revisions.
msg3418 (view) Author: florian Date: 2014-09-17.12:36:33
The following assertion fails for the unsolvable tasks that are created if the
translator detects unsolvability.
To reproduce, search with "astar(lmcount(lm_rhw()))" on mystery/prob07.pddl in
debug mode.

landmarks/landmark_factory_rpg_sasp.cc:109: int
LandmarkFactoryRpgSasp::min_cost_for_landmark(LandmarkNode*,
std::vector<std::vector<int> >&): Assertion `min_cost <
numeric_limits<int>::max()' failed.
History
Date User Action Args
2014-09-23 19:36:19maltesetmessages: + msg3516
2014-09-23 19:32:38floriansetmessages: + msg3514
2014-09-17 15:59:00erezsetnosy: + erez
messages: + msg3428
2014-09-17 14:28:44maltesetstatus: unread -> chatting
messages: + msg3427
2014-09-17 12:36:56floriansetnosy: + malte
2014-09-17 12:36:33floriancreate