RE: [gnugo-devel] Joseki variations question

[Evan Berggren Daniel]

For analysing, what you're looking for is probably to run Gnu Go in GTP
mode (--mode gtp), and then load the sgf (loadsgf sgffilename movenum).
You can then use the gtp commands to ask Gnu Go questions.

What happened in the game was B Q6, W S4.  The corner lives, but black
gets the better of the deal.  I would worry about B Q6 W R6 B R7.
Basically, if Gnu Go plays tenuki here, B will get a significant
advantage; there is no danger of the corner dying, but we need to worry
about much more than that.

The question isn't whether Gnu Go should help the stones; it's whether
modifying the database is the right way to get it to help them.

Evan Daniel

On Thu, 27 Mar 2003, Smith, Christopher wrote:

> This is an interesting question, it appears that GnuGo should somehow help 
> those stones- but I am not sure if that is actually needed.
>
> If black played R2, Q2 would be a good follow-up. If Q6, R6 and then so on. 
> It would obviously get messy in the battle for the corner but I am not sure 
> if it is _guaranteed_ to die. But then again I am not an exceptionally strong 
> player.
>
> Is there a way to just 'start' GnuGo from a position like this, but as the 
> other color and see what GnuGo would think? Perhaps there is a great attack 
> we know of and just the defense to it isn't in our DB.
>
> -Chris Smith
>
>       -----Original Message-----
>       From: Evan Berggren Daniel [mailto:address@hidden
>       Sent: Thu 3/27/2003 9:36 AM
>       To: address@hidden
>       Cc:
>       Subject: [gnugo-devel] Joseki variations question
>
>
>
>       I noticed a problem in the game gnugo-3.3.17-ylamaki-200303262305.sgf.  
> At
>       move 9, the position is:
>
>          A B C D E F G H J K L M N O P Q R S T
>       19 . . . . . . . . . . . . . . . . . . . 19
>       18 . . . . . . . . . . . . . . . . . . . 18
>       17 . . . . . . . . . . . . . . . . . . . 17
>       16 . . . X . . . . . + . . . . . X . . . 16
>       15 . . . . . . . . . . . . . . . . . . . 15
>       14 . . . . . . . . . . . . . . . . . . . 14
>       13 . . . . . . . . . . . . . . . . . . . 13
>       12 . . . . . . . . . . . . . . . . . . . 12
>       11 . . . . . . . . . . . . . . . . . . . 11
>       10 . . . + . . . . . + . . . . . + . . . 10
>        9 . . . . . . . . . . . . . . . . . . . 9
>        8 . . . . . . . . . . . . . . . . . . . 8
>        7 . . . . . . . . . . . . . . . . . . . 7
>        6 . . . . . . . . . . . . . . . . . . . 6
>        5 . . . . . . . . . . . . . . X O . . . 5
>        4 . . . X . . . . . + O . . . X O . . . 4
>        3 . . . . . . . . . . . . . X . X O . . 3
>        2 . . . . . . . . . . . . . . . . . . . 2
>        1 . . . . . . . . . . . . . . . . . . . 1
>          A B C D E F G H J K L M N O P Q R S T
>
>
>       Clearly, a play in the lower right is in order.  However, Gnu Go plays
>       tenuki.  To what degree do we wish to fix problems in variations like 
> this
>       with changes to the joseki database?  I think it should be obvious to 
> Gnu
>       Go that the lower right is the place to play, and there aren't any 
> complex
>       considerations that it doesn't understand.  Clearly, complex or subtle
>       variations that aren't quite joseki need to be in the database, but 
> there
>       is also value (I believe) to keeping the database small and uncluttered.
>
>       What do other people think about this?
>
>       Evan Daniel
>
>
>       _______________________________________________
>       gnugo-devel mailing list
>       address@hidden
>       http://mail.gnu.org/mailman/listinfo/gnugo-devel
>
>
>