[Computer-go] Scoring a go board.

Nick Wedd nick at maproom.co.uk
Sat Feb 9 01:53:49 PST 2013


On 08/02/2013 21:31, Rémi wrote:
> If there really is a difference between (1) and (2) then I have always
> been completely oblivious to it. For your third (3) case I again see not
> what the difference is.

Here are some very simple examples, all on 9x9 boards:

Case 1:

  . . . . O # . . .
  . . . . O # . . .
  . . . . O # . . .
  . . . . O # . . .
  . . . . O # . . .
  . . . . O # . . .
  . . . . O # . . .
  . . . . O # . . .
  . . . . O # . . .

Case 2:

  . . . . O # . . .
  . . . . O # . . .
  . . . . O # . . .
  . . . . O # . . .
  . . . . O # . . .
  . . . . O # . . .
  . . . . O # . . .
  . . . . O # . . .
  . . . . . # . . .

Case 3:

  . . . . . . . . .
  . . . . . . . . .
  . . . O # . . . .
  . . . O O # . . .
  . . . . # # . . .
  . . . O . . . . .
  . . . . . . . . .
  . . . . . . . . .
  . . . . . . . . .

Nick

>
>
> On 8 February 2013 22:02, Nick Wedd <nick at maproom.co.uk
> <mailto:nick at maproom.co.uk>> wrote:
>
>     On 08/02/2013 20:34, Rémi wrote:
>
>         Hy,
>
>         There are a lot of interesting papers on UCT and selection
>         strategies
>         ... But it's harder to find information about the more
>         'pragmatic' side
>         of computer-go.
>
>         How do you score a go board?
>
>
>     What do you mean by "score a go board"?  I can think of three
>     reasonable possibilities.
>
>     (1.) Count the score in a game that is over.
>
>     (2.) Count the score in a game that is not over, but both players
>     have passed because they think it is.
>
>     (3.) Count the score in a game that is still being played.
>
>     (1) is difficult but practicable. (2) is similar to (1), so long as
>     you are not bothered about the result being meaningful, but just
>     want to calculate the score as a referee might if asked to score a
>     game in which both players have passed prematurely. (3) is as
>     difficult as playing Go perfectly.
>
>     Nick
>
>
>         What would be a faster algorithm to score a go-board?
>         Could you pre-calculate and accumulate some information early in the
>         game (on every move), knowing you're going to evaluate the board
>         many times?
>         When do you decide to finish/score the game?
>
>         Also, what are some of the languages used besides C(++)? Does anyone
>         work in something like java or a functional language?
>
>         Rémi de Zoeten.
>
>
>         _________________________________________________
>         Computer-go mailing list
>         Computer-go at dvandva.org <mailto:Computer-go at dvandva.org>
>         http://dvandva.org/cgi-bin/__mailman/listinfo/computer-go
>         <http://dvandva.org/cgi-bin/mailman/listinfo/computer-go>
>
>
>
>     --
>     Nick Wedd
>     nick at maproom.co.uk <mailto:nick at maproom.co.uk>
>     _________________________________________________
>     Computer-go mailing list
>     Computer-go at dvandva.org <mailto:Computer-go at dvandva.org>
>     http://dvandva.org/cgi-bin/__mailman/listinfo/computer-go
>     <http://dvandva.org/cgi-bin/mailman/listinfo/computer-go>
>
>


-- 
Nick Wedd
nick at maproom.co.uk



More information about the Computer-go mailing list