[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [gnugo-devel] Opponent follow-up value and group connection
From: |
SP LEE |
Subject: |
Re: [gnugo-devel] Opponent follow-up value and group connection |
Date: |
Tue, 13 May 2003 13:41:12 -0700 |
This is a more careful treatment for larger dragons. Please ignore my
previous patch. The fix here is like "forget the shape factor if either
attacking or defending a dragon of more than 20 points is involved." This
kind of play can be seen even in professional games.
SP Lee
Index: value_moves.c
===================================================================
RCS file: /cvsroot/gnugo/gnugo/engine/value_moves.c,v
retrieving revision 1.92
diff -u -r1.92 value_moves.c
--- value_moves.c 12 May 2003 08:50:42 -0000 1.92
+++ value_moves.c 13 May 2003 20:34:46 -0000
@@ -2636,7 +2636,9 @@
if (move[pos].secondary_value != 0.0)
TRACE(" %1m: %f - secondary\n", pos, 0.05 *
move[pos].secondary_value);
- if (move[pos].numpos_shape + move[pos].numneg_shape > 0) {
+ if ((move[pos].numpos_shape + move[pos].numneg_shape > 0)
+ && (move[pos].territorial_value < 20)){
+ /* for attack/defend large dragon, ignore shape factor */
/* shape_factor has already been computed. */
float old_value = tot_value;
tot_value *= shape_factor;
- [gnugo-devel] Opponent follow-up value and group connection, SP LEE, 2003/05/10
- Re: [gnugo-devel] Opponent follow-up value and group connection, SP LEE, 2003/05/11
- Re: [gnugo-devel] Opponent follow-up value and group connection, Paul Pogonyshev, 2003/05/13
- Re: [gnugo-devel] Opponent follow-up value and group connection, Heikki Levanto, 2003/05/14
- Re: [gnugo-devel] Opponent follow-up value and group connection, SP LEE, 2003/05/15
- [gnugo-devel] How can I trace "current stack" in owl analysis?, SP LEE, 2003/05/16
- Re: [gnugo-devel] How can I trace "current stack" in owl analysis?, bump, 2003/05/16