[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [gnugo-devel] Inessential worms
From: |
Daniel Bump |
Subject: |
Re: [gnugo-devel] Inessential worms |
Date: |
Sun, 25 Nov 2001 07:14:45 -0800 |
> The long-term solution to the amalgamation problems is to give
> readconnect responsibility for doing the amalgamation. For the time
> being, any change of inessential strings that improves matters is okay
> with me.
Then it would seem that readconnect is going to have to
be able to either consult the semeai module or duplicate
its functionality. If the potentially inessential worm
has a lot of liberties the tactical reading code won't
be able to determine whether or not it is truly inessential.
Could you explain what you envision readconnect doing in
a situation like semeai6.sgf (upper left)?
Dan
- [gnugo-devel] Inessential worms, Daniel Bump, 2001/11/25
- Re: [gnugo-devel] Inessential worms, Gunnar Farneback, 2001/11/25
- Re: [gnugo-devel] Inessential worms,
Daniel Bump <=
- Re: [gnugo-devel] Inessential worms, Gunnar Farneback, 2001/11/25
- Re: [gnugo-devel] Inessential worms, Daniel Bump, 2001/11/25
- Re: [gnugo-devel] Inessential worms, Gunnar Farneback, 2001/11/25
- Re: [gnugo-devel] Inessential worms, Daniel Bump, 2001/11/25
- Re: [gnugo-devel] Inessential worms, Daniel Bump, 2001/11/25