1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
|
ANALYZING GAMES STORED IN SGF FILES
USING GNUGO
Finding out the winner of the game
-------------------------------
gnugo --score last -l filename
loads the sgf file and estimates the winner after the last stored move by
measuring the influence.
gnugo --score end -l filename
loads the sgf file and gnugo continues to play after the last stored move by
itself up to the very end.
Then the winner is determined by counting the territory.
gnugo --score L10 -l filename
loads the sgf file until a stone is placed on L10. Now the winner will be
estimated as with gnugo --score last.
gnugo --score 100 -l filename
loads the sgf file until move number 100. Now the winner will be estimated
as with gnugo --score last.
If the option "-o outputfilename" is provided, the results will also be
written as comment at the end of the output file.
If the option "--analyzerfile outputfilename" is provided, the results
will be written as comment at the end of the output file, the result property
will be set and the territory will be marked.
OTHER OPTIONS
Using --analyze:
----------------
The analyze options allow analysis of a game stored as sgf file by using
--testmode. hen using --testmode with --analyze move tree variations are
ignored.
The --analyze option also works with --benchmark and --score. The analyze
functions will be executed on every move in --benchmark and --testmode game.
Analyzed board states on other modes:
--score end:
gnugo analyzes every move it makes at the end of the
file until the game is finished.
--score last:
board state at the end of the file will be analyzed
--score <movenum>:
board state just before <movenum> will be analyzed
--score <position>:
board state just before <position> is occupied will be analyzed
--testmode annotation:
board state just before the annotated node is reached will be
analyzed
The results of the analyze functions are written to the filename provided by
--analyzerfilename.
description of --analyze options:
---------------------------------
areacolor:
show color of influence
all:
switch on all analyze options
capture:
show capturing move for all caputurable worms
considered:
show considerd moves an their values
defense:
show defending move for all caputurable worms
dragoninfo:
show dragon info
dragonstatus:
the dragons are are marked on the board with letters according to
the status: aLive, Dead, Critial, Unknown
eyeinfo:
show eye info
eyes:
show eye space and the attacking points
gameinfo:
show misc info (captured, territory, move values, ...)
moyocolor:
show moyos by color
recommended:
show moves recommended by the various modules:
A = attacker
B = very big move
D = defender
E = eyefinder
F = fuseki
L = liberty filling
P = pattern
p = reconsidered pattern
S = semeai
terri:
show territory from moyo.c
territory:
show territory from dragons
worminfo:
show worm info
wormliberties:
show the number of liberties for each worm
You can give more than one --analyze option also by concatenating it with ""
or by using commas without space.
Usage examples:
"gnugo --score end --analyzerfile outputfile -l inputfile"
will create outputfile and writes the inputfile to it plus the endgame moves
for scoring and adds the result property.
If you want to overwrite an already existing result property use
"--analyze overwrite". This also overwrites DT, AP and RU.
"gnugo --score end --analyzerfile outputfile -l inputfile --analyze dragonstatus"
same as above, but writes to outputfile the dragonstatus for every move gnugo
made from the last move in inputfile to the end of the game.
"gnugo --testmode game --analyzerfile outputfile -l inputfile --analyze wormliberties"
loads inputfile and writes to outputfile the number of liberties for each worm on
every move.
"gnugo --testmode annotation --analyzerfile outputfile -l inputfile --analyze capture"
loads inputfile and writes to outputfile the capturing move for each weak
group on every move followed by a annotation (see also docs/REGRESSION).
tcsh COMPLETION
If tcsh is your shell, the following completion setting for tcsh allows an
easy use of gnugo and its command line options. You can add this to /etc/csh.chsrc.
complete gnugo c/--/"(allpats analyze analyzerfile backfill_depth benchmark \
boardsize color copyright debug decidestring depth handicap \
hash help infile komi mode moyo outfile playstyle printsgf \
score stack statistics testmode trace seed until worms)"/\
n/{-*o,--analyzerfile}/f:*.{sgf,mgt,SGF,MGT}/\
n/--analyze/"(all overwrite dragoninfo dragonstatus considered wormliberties \
eyes worminfo eyeinfo gameinfo moyocolor recommended capture moyovalue \
defense terricolor terrivalue territory areacolor areavalue)"/\
n/{-h,--help}/"(debug analyze playstyle)"/\
n/--mode/"(ascii test gmp)"/\
n/--testmode/"(annotation game move both)"/\
n/--score/"(end last pass)"/\
n/--color/"(black white)"/\
n/--boardsize/"(3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21)"/\
c/-/"(a b B d D h H L l m o p r s S T t v w)"/
|
