Re: [gnugo-devel] owl goal dragon gets cut

[Gunnar Farnebäck]

Arend wrote:
> Reading +1%, owl +2%, connection +5%. Overall performance penalty <3%.

That's almost nothing for this functionality.

> A detailed analysis of the PASSes/FAILs showed that in the overwhelming
> majority of the cases, owl reading was clearly improved, so I think it
> is well worth the performance cost.

No doubt about that.

> Only problem I have encountered are that sometimes gnugo now generates
> sensesless "escape moves" towards cut off former goal stones, which have
> no escape value at all (and then running out of depth limit etc.).

What about marking such stones as "former goal" and give them zero
escape value in owl_escape_value()?

/Gunnar