Re: [gnugo-devel] influence and more

[Gunnar Farneback]

Arend wrote:
> I have considered reorganizing the influence code for a while now, and
> by now I have some very concrete plans, affecting the interface to the
> influence code, but also the dragon safety computation and possibly
> other stuff. I would like to invite comments.

Sounds good.

> 2. use compute_dragon_weakness() already pre-owl for this decision.
> As far as I am concerned, the safety values
> WEAK, WEAKLY_ALIVE, ALIVE, and STRONGLY_ALIVE could be all be treated
> as ALIVE, and if we need to make a decision based on the weakness of
> a dragon, we use the continuos .weakness instead. (INESSENTIAL,
> TACTICALLY_DEAD and INVINCIBLE should stay, as they do contain
> important additional information that .weakness cannot provide.)

It may be useful to leave STRONGLY_ALIVE too, as an indication that
even taking miscalculations into account, the dragon is almost
certainly alive (but less certainly than INVINCIBLE). I suspect we'd
like to have weakness 0 at a somewhat weaker point.

/Gunnar