[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[gnugo-devel] a few trivial doc fixes
From: |
Douglas Ridgway |
Subject: |
[gnugo-devel] a few trivial doc fixes |
Date: |
Mon, 28 Jun 2004 12:13:02 -0600 (MDT) |
Index: doc/dragon.texi
===================================================================
RCS file: /cvsroot/gnugo/gnugo/doc/dragon.texi,v
retrieving revision 1.17
diff -p -u -w -r1.17 dragon.texi
--- doc/dragon.texi 25 May 2004 03:13:10 -0000 1.17
+++ doc/dragon.texi 28 Jun 2004 17:46:32 -0000
@@ -137,7 +137,7 @@ fourth order liberties, respectively.
The definition of liberties of order >1 is adapted to the
problem of detecting the shape of the surrounding
empty space. In particular we want to be able to see if a group
-is loosely surrounded. @dfn{a liberty of order n} is an empty
+is loosely surrounded. A @dfn{liberty of order n} is an empty
vertex which may be connected to the string by placing n
stones of the same color on the board, but no fewer. The
path of connection may pass through an intervening group
Index: doc/overview.texi
===================================================================
RCS file: /cvsroot/gnugo/gnugo/doc/overview.texi,v
retrieving revision 1.19
diff -p -u -w -r1.19 overview.texi
--- doc/overview.texi 16 Apr 2004 16:21:46 -0000 1.19
+++ doc/overview.texi 28 Jun 2004 17:46:32 -0000
@@ -11,7 +11,7 @@ value (including captures or life-and-de
strategical effects (such as strengthening a weak group).
Note that while GNU Go does, of course, do a lot of reading to analyze
-possible captures, life and death of groups etc., it does not (yet?) have
+possible captures, life and death of groups etc., it does not (yet) have
a fullboard lookahead.
@menu
@@ -36,12 +36,12 @@ Bad judgement of weaknesses of groups ma
This information gathering is done by the function @code{examine_position()}.
It first calls @code{make_worms()}.
-Its first steps are very simple: It identifies sets of directly connected
-stones--we call them @dfn{worms}--, and notes their sizes and their number of
+Its first steps are very simple: it identifies sets of directly connected
+stones, called @dfn{worms}, and notes their sizes and their number of
liberties.
Soon after comes the most important step of the worm analysis:
-The tactical reading code (@pxref{Tactical Reading}) is called for every
+the tactical reading code (@pxref{Tactical Reading}) is called for every
worm. It tries to read
out which worms can be captured directly, giving up as soon as a worm
can reach 5 liberties. If a worm can be captured, the engine of course
@@ -50,7 +50,7 @@ is made to find virtually all moves that
of a worm.
After knowing which worms are tactically stable, we can make a first
-picture of the balance of power across the board: The @ref{Influence}
+picture of the balance of power across the board: the @ref{Influence}
code is called for the first time.
This is to aid the next step, the analysis of dragons. By a @dfn{dragon}
@@ -84,7 +84,7 @@ explanations of the data structures used
see @xref{Worms and Dragons}.
The influence code is then called second time to make a detailed analysis
-of likely territory. Of course, the life-and-death status' of dragons are
+of likely territory. Of course, the life-and-death status of dragons are
now taken into account.
The territorial results of the influence module get corrected by the break-in
Index: doc/eyes.texi
===================================================================
RCS file: /cvsroot/gnugo/gnugo/doc/eyes.texi,v
retrieving revision 1.8
diff -p -u -w -r1.8 eyes.texi
--- doc/eyes.texi 13 Nov 2003 22:48:40 -0000 1.8
+++ doc/eyes.texi 28 Jun 2004 17:46:32 -0000
@@ -501,21 +501,25 @@ this file. Some of them might be slightl
explain one important case here. Consider
@example
address@hidden
Pattern 6141
X
XX.@@x
:1122
address@hidden group
@end example
which e.g. matches in this position:
@example
address@hidden
.OOOXXX
OOXOXOO
OXXba.O
OOOOOOO
address@hidden group
@end example
Now it may look like @samp{X} could take away both eyes by playing @samp{a}
@@ -527,12 +531,14 @@ crucial property of this shape is that w
(at least) one eye, @samp{O} can answer at @samp{b}, giving:
@example
address@hidden
.OOOXXX
OO.OXOO
O.cOX.O
OOOOOOO
address@hidden group
@end example
Now @samp{X} has to continue at @samp{c} in order to keep @samp{O}
@@ -543,12 +549,18 @@ indeed 1122.
As a final note, some of the eye values indicating a threat depend
on suicide to be allowed, e.g.
address@hidden
address@hidden
+
Pattern 301
X.X
:1222
address@hidden group
address@hidden example
+
We always assume suicide to be allowed in this database. It is easy
enough to sort out such moves at a higher level when suicide is
disallowed.
@@ -625,7 +637,7 @@ criteria above and classify the point fr
This section extends the topological eye analysis to handle ko. We
-distinguish between a ko in favor of @samp{O}' and one in favor of @samp{X}:
+distinguish between a ko in favor of @samp{O} and one in favor of @samp{X}:
@example
@group
@@ -867,9 +879,11 @@ The following situation is rare but spec
attention:
@example
address@hidden
OOOOXX
OXaX..
------
address@hidden group
@end example
Here @samp{a} may be characterized by the fact that it is adjacent
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [gnugo-devel] a few trivial doc fixes,
Douglas Ridgway <=