Issue845

Title Guard against unsupported task transformations in the landmark heuristics
Priority wish Status resolved
Superseder Nosy List cedric, florian, jendrik, malte
Assigned To florian Keywords
Optional summary

Created on 2018-09-21.12:53:43 by florian, last changed by cedric.

Messages
msg7742 (view) Author: florian Date: 2018-09-21.14:01:37
merged
msg7736 (view) Author: malte Date: 2018-09-21.13:25:06
Done with my comments on bitbucket.
msg7733 (view) Author: florian Date: 2018-09-21.13:13:55
I created a pull request for this here:
https://bitbucket.org/FlorianPommerening/downward-issues/pull-requests/50/issue845/diff
msg7730 (view) Author: florian Date: 2018-09-21.12:53:43
The landmark heuristics currently compute the landmarks on the transformed task
but evaluate whether a landmark has been reached using transitions from the
global task. This only works because we currently only use task transformations
that modify the costs and leave everything else the same.

Fully supporting task transformations in path-dependent heuristics is issue686.
Here we just want to prevent accidental mis-use of the transform argument in the
landmark heuristic by verifying that only compatible task transformations are used.
History
Date User Action Args
2018-09-21 15:48:47cedricsetnosy: + cedric
2018-09-21 14:01:37floriansetstatus: in-progress -> resolved
messages: + msg7742
2018-09-21 13:25:06maltesetmessages: + msg7736
2018-09-21 13:13:55floriansetmessages: + msg7733
2018-09-21 12:53:43floriancreate