[gnugo-devel] doc update

[Gunnar Farnebäck]

This documentation patch replaces debugboard with view.pike in
analyze.texi and fixes some out of date information in install.texi.

/Gunnar

Index: doc/analyze.texi
===================================================================
RCS file: /cvsroot/gnugo/gnugo/doc/analyze.texi,v
retrieving revision 1.14
diff -u -r1.14 analyze.texi
--- doc/analyze.texi    20 Aug 2004 10:30:12 -0000      1.14
+++ doc/analyze.texi    6 Oct 2005 21:14:58 -0000
@@ -17,7 +17,7 @@
 * Decide string::              Checking the reading code
 * Decide dragon::              Checking the owl code
 * GTP and GDB techniques::      GTP and GDB techniques
-* Debugboard::                  Debugboard
+* view.pike::                   Debugging on a Graphic Board
 * Scoring::                     Finding out the winner of the game
 * Colored Display::             Colored Display
 @end menu
@@ -46,13 +46,12 @@
 
 If you use the @option{-w} option, GNU Go will report the statuses of
 worms and dragons around the board. This type of information is
-available by different methods, however (@pxref{Debugboard},
+available by different methods, however (@pxref{view.pike},
 @pxref{Colored Display}).
 
 @node Output File
 @section The Output File
 @cindex output file
address@hidden output file
 
 If GNU Go is invoked with the option @option{-o filename} it will
 produce an output file. This option can be added at the command line
@@ -152,7 +151,7 @@
 @code{sgf_trace}.
 
 @node Decide dragon
address@hidden Checking the Owl code
address@hidden Checking the Owl Code
 @cindex decide-dragon
 
 You can similarly debug the Owl code using the option
@@ -185,17 +184,22 @@
 
 Similarly you can get the worm data with @command{worm P12}.
 
address@hidden Debugboard
address@hidden Debugboard
address@hidden debugboard
-
-A useful utility called @command{debugboard} is made in
-the @file{interface/debugboard/} directory. This can be run
-in an Xterm. Use a smaller font since it requires 50 rows
-and 80 columns. This runs @code{examine_position()}, then
-makes a graphical display of the board. Using the cursor
-movement keys, you can move around the board and find
-out the contents of the worm, dragon and eye arrays.
address@hidden view.pike
address@hidden Debugging on a Graphical Board
address@hidden debugging on a graphical board
+
+The quickest way to analyze most positions is to use the tool
address@hidden in the @file{regression} directory. It can be started
+with a testcase specified, e.g. @command{pike view.pike strategy:40} or
+at a move in an sgf file, e.g. @command{pike view.pike mistake.sgf:125}.
+When started it shows the position on a grapical board on which it also
+marks information like move values, dragon status, and so on. By
+clicking on the board further information about the valuation of moves,
+contents of various data structures, and other data can be made
+available.
+
+Specific information on how to use @file{view.pike} for influence tuning
+can be found in @xref{Influence Tuning}.
 
 @node Scoring
 @section Scoring the game
Index: doc/install.texi
===================================================================
RCS file: /cvsroot/gnugo/gnugo/doc/install.texi,v
retrieving revision 1.20
diff -u -r1.20 install.texi
--- doc/install.texi    16 Apr 2005 20:47:36 -0000      1.20
+++ doc/install.texi    6 Oct 2005 21:14:58 -0000
@@ -79,7 +79,6 @@
 @menu
 * Ram Cache::                 Ram Cache
 * Default Level::             Default Level
-* DFA Option::                DFA Option
 * Other Options::             Other Options
 @end menu
 
@@ -148,23 +147,13 @@
 you want to change the default you may rerun configure
 and recompile the program.
 
address@hidden DFA Option
address@hidden DFA Configure Option
-
-There are two distinct implementations of the pattern matcher in GNU
-Go. The DFA (Discrete Finite-state Automata) option was considered
-experimental in GNU Go 3.0 but is now standard. You can disable it by
-with the configure option @command{./configure --disable-dfa}.  The
-option is harder to debug than the old matcher but significantly
-faster (@pxref{DFA}).
-
 @node Other Options
 @subsection Other Options
 
-Anything new in the engine is generally tested as an experimental
-option which can be turned on or off at compile time or run time.
-Some ``experimental'' options such as the break-in code and the
-semeai code are no longer experimental but are enabled by default.
+Anything new in the engine is generally tested as an experimental option
+which can be turned on or off at compile time or run time. Some
+``experimental'' options such as the break-in code are no longer
+experimental but are enabled by default.
 
 This section can be skipped unless you are interested in the
 experimental options.