I'm discovering how to "debugging" at patterns-level. <shell> $ gnugo.exe --trace -l cisba01.sgf 2>&1 | tail -n 13
Top moves: 1. H5 2.44 2. J10 2.25 3. A1 0.71 4. P5 0.19 5. Q5 0.19 6. F9 0.10 7. N7 0.10 Checking safety of a white move at H5 Move generation likes H5 with value 2.44 genmove() recommends H5 with value 2.44 white (O) move H5 </shell> Move H5 is clearly wrong. <shell> $ gnugo.exe --trace -l cisba01.sgf --decide-owl H4 finished examine_position owl_attack H4 Pattern VA49 found at H5 with value 35 Variation 13: ALIVE (2 or more secure eyes) H4 cannot be attacked (14 variations) owl_defend H4 Pattern VA49 found at H5 with value 35 Variation 13: ALIVE (2 or more secure eyes) H4 is alive as it stands </shell> Can I conclude that pattern VA49 has a bug? <file owl_vital_apats.db> Pattern VA49 # tm New Pattern (3.1.18) (see trevor:430) # FIXME: This is non-sense if the ataried stone has neighbours # in atari (see trevorb:360) X* atari outside eyespace oX :8,-,value(35) X* AB ; lib(B) <= 2 && owl_eyespace(A) </file owl_vital_apats.db> It's first time I try to debug a pattern. Someone can help me? Thanks in advance and regards. -- Emanuele http://www.google.com/reader/shared/07971903590737268053
cisba01.sgf
Description: application/go-sgf
_______________________________________________ gnugo-devel mailing list gnugo-devel@gnu.org http://lists.gnu.org/mailman/listinfo/gnugo-devel
