[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [gnugo-devel] attack_either ...
From: |
alain Baeckeroot |
Subject: |
Re: [gnugo-devel] attack_either ... |
Date: |
Thu, 30 Nov 2006 15:20:28 +0100 |
User-agent: |
KMail/1.9.3 |
hi again
I reformulate my second question :)
how could i know where/when is use a specific db ?
[patterns]$ grep -c attack_either *.db | grep -v ":0"
aa_attackpats.db:1
barriers.db:32
conn.db:1
endgame.db:4
owl_attackpats.db:15
owl_defendpats.db:22
patterns2.db:50
patterns.db:55
[patterns]$ grep -c defend_both *.db | grep -v ":0"
aa_attackpats.db:1
barriers.db:22
endgame.db:1
owl_attackpats.db:29
owl_defendpats.db:13
owl_vital_apats.db:3
patterns2.db:44
patterns.db:28
The idea is to use current attack_either/defend_both, when we cannot avoid
it (very early matchpat), and to use a better one (find_double_threats?)
when we already have some info available
Alain