Issue1208

Title Remove old task transfomation code
Priority feature Status chatting
Superseder Nosy List florian, jendrik, malte
Assigned To Keywords
Optional summary
Some ancillary things to keep in mind:
- Reuse per-task information (which includes Evaluators now) (issue564)
- Can we enable reuse of heuristics across different searches? See issue121.

Created on 2026-03-02.09:25:20 by florian, last changed by florian.

Summary
Some ancillary things to keep in mind:
- Reuse per-task information (which includes Evaluators now) (issue564)
- Can we enable reuse of heuristics across different searches? See issue121.
Messages
msg12041 (view) Author: florian Date: 2026-03-02.12:43:04
I moved some notes from issue559 about related issues here.
msg12036 (view) Author: florian Date: 2026-03-02.09:25:20
Once issue559 is merged, we should remove the traces of the old task transformation code. In particular this includes:
* Heursitic::convert_ancestor_state
* The transformation in Heuristic::set_preferred
* The check that the given task is a transformation of the root task in
  LandmarkHeuristic::initialize

Possibly this requires other changes such as
* making PerStateInformation no longer dispatch on the task
* transforming states in the virtual methods of ModifyCostsEvaluator
* updating the place the tasks are wrapped into the special axioms tasks (tasks::get_default_value_axioms_task_if_needed)
History
Date User Action Args
2026-03-02 12:43:04floriansetmessages: + msg12041
status: unread -> chatting
summary: Some ancillary things to keep in mind: - Reuse per-task information (which includes Evaluators now) (issue564) - Can we enable reuse of heuristics across different searches? See issue121.
2026-03-02 09:25:20floriancreate