Title Clarify role of Heuristic class
Priority feature Status unread
Superseder Nosy List cedric, gabi, malte
Assigned To Keywords
Optional summary

Created on 2018-09-14.12:50:43 by gabi, last changed by cedric.

msg7462 (view) Author: gabi Date: 2018-09-14.12:50:43
Since we now (issue727) use almost everywhere Evaluator instead of Heuristic, we
need to think about whether we want to keep the Heuristic class at all, and if
yes, for which purpose.

Relevant note copied from msg7457:

Conceptually, a "heuristic" is evaluator that is supposed to measure goal
distance, but the current distinction between when to derive from Heuristic and
when from Evaluator is mainly based on other considerations. We should think of
how to distribute the responsibility and whether we want a class named
"Heuristic" or whether it should have a name that reflects more closely what it
actually does. For example, I think it could be useful to have an abstract base
class for evaluators that are not composites of other evaluators.

This also affects the discussion of "Heuristic" in task_proxy.h
Date User Action Args
2018-09-17 07:31:40cedricsetnosy: + cedric
2018-09-14 13:20:56maltesetnosy: + malte
2018-09-14 12:50:43gabicreate