[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gnugo-devel] Revise TODO?

From: Gunnar Farnebäck
Subject: Re: [gnugo-devel] Revise TODO?
Date: Fri, 09 Nov 2007 20:15:26 +0100
User-agent: Mozilla-Thunderbird (X11/20071008)

alain Baeckeroot wrote:
Maybe add somewhere a section "Known weakness" or "Simplifications" with
 short comment if needed (in the trac wiki or in Doc...):
 - intransitivity in connection
        - group A is connected (cannot be cut) to B
        - B is connected to C
        GNU Go _assumes_ that A is connected to C, and this can be false

The connection code can often detect intransitivities, but the dragon
amalgamation is not quite as smart. This could well be added as a proper
TODO item.

 - underestimate danger when surrounded at some distance
        there are tons of example where a dragon_status suddenly change from
        "alive" to "dead" after one move.  It would be better to have an
        intermediate step with "unknown" (easy to say, hard to program :)

This ties in both with dragon weakness estimation and with the fact that
the owl code is by nature optimistic about status for big dragons with
many places to make moves.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]