[Computer-go] replacing dynamic komi with a scoring function

[Stefan Kaitschick]

The correct answer is 0, because shifting by just 1 point drops the rate to
> 10%
> But is this really a dynamic komi problem?
> I mean, is there really a graceful way to misevaluate semeais?
> apropos semeais: would it be feasible to expand RAVE to include the
> information of the previous move?
> ( like the "killer heuristic" in chess)
> It could be limited to the 5 by 5 surroundings, so that the previous move
> is one of 24 points or "other".
> But that's still not cheap computationally. I just have no idea how much
> effort it takes to maintain the current RAVE.
>
> Stefan
>
>
> On Mon, Jan 9, 2012 at 8:14 PM, Aja Huang <ajahuang at gmail.com> wrote:
>
>> Interesting. I have observed a problem in the current dynamic komi scheme
>> especially when there is a big semeai/life-and-death:
>>
>> Playout 1   B+0.5
>> Playout 2   B+0.5
>> Playout 3   B+0.5
>> Playout 4   B+0.5
>> Playout 5   B+0.5
>> Playout 6   B+0.5
>> Playout 7   B+0.5
>> Playout 8   B+0.5
>> Playout 9   B+0.5
>> Playout 10 W+8.5
>>
>> B has 90% winning rate. How many points should we shift for dynamic komi?
>>
>> Aja
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://computer-go.org/pipermail/computer-go/attachments/20120109/bb6d8511/attachment.html>