Author: Robert Hyatt
Date: 12:46:36 04/29/02
Go up one level in this thread
On April 29, 2002 at 15:06:54, Miguel A. Ballicora wrote:
>I guess that Bc3 played by CT is partially because CT has code that detects
>a trapped queen. So, after Bc3 Qxb6 CT thinks that the queen is in bad shape
>so it is worth losing a doubled pawn. Some time ago CT was very succesful in a
>position that few commercial programs (including Fritz) detected as bad, when a
>queen was trapped. I guess that this code backfired here, in combination with a
>horizon effect in which it did not see that Bc3 did not really threat the rook
>at a1.
>
>My program gaviota has some code to detect a trapped queen and wants to play Bc3
>for while up to ply 10 when it changes to Bc5. Interestingly, Gaviota did well
>in that position that CT did well. I am not trying to compare my weak amateur
>program with tiger, I am just trying to make a correlation.
>
>I guess that this code could have created a problem in this particular position.
>
>Did I guess right Christophe?
>
>Regards,
>Miguel
I ran this on Crafty and got the following:
8-> 0.23 -1.38 1. ... Bc3 2. Qxd7 Bxd7 3. Rab1 Kg8
4. Rc2 Rxa4 5. Nd2
9 0.34 ++ 1. ... Bc3!!
9 0.75 -1.95 1. ... Bc3 2. Qxd7 Bxd7 3. Rab1 Rxa4
4. Bf1 R4a5 5. Rc2 Rb8 6. Rbc1 Bxb5
9-> 0.82 -1.95 1. ... Bc3 2. Qxd7 Bxd7 3. Rab1 Rxa4
4. Bf1 R4a5 5. Rc2 Rb8 6. Rbc1 Bxb5
10 0.98 -2.18 1. ... Bc3 2. Qxd7 Bxd7 3. Rab1 Rxa4
4. Bf1 R4a5 5. Be2 Bxb5 6. Bf1 Rb8
7. Rc2 <HT>
(3) 10-> 1.41 -2.18 1. ... Bc3 2. Qxd7 Bxd7 3. Rab1 Rxa4
4. Bf1 R4a5 5. Be2 Bxb5 6. Bf1 Rb8
7. Rc2 <HT>
(2) 11 2.33 -2.21 1. ... Bc3 2. Qxd7 Bxd7 3. Rab1 Rxa4
4. Rd1 R4a5 5. Kh2 Ra2 6. Kg1 R8a5
7. Rbc1 Bxb5
(2) 11-> 4.04 -2.21 1. ... Bc3 2. Qxd7 Bxd7 3. Rab1 Rxa4
4. Rd1 R4a5 5. Kh2 Ra2 6. Kg1 R8a5
7. Rbc1 Bxb5
12 5.90 -2.27 1. ... Bc3 2. Qxd7 Bxd7 3. Rab1 Rxa4
4. Kh2 R4a5 5. Ng1 Bxb5 6. Rb3 Bxd3
7. Rxb6 Bc4 8. Rxb7
12-> 6.75 -2.27 1. ... Bc3 2. Qxd7 Bxd7 3. Rab1 Rxa4
4. Kh2 R4a5 5. Ng1 Bxb5 6. Rb3 Bxd3
7. Rxb6 Bc4 8. Rxb7
13 11.26 -2.34 1. ... Bc3 2. Qxd7 Bxd7 3. Rab1 Rxa4
4. Rd1 R4a5 5. Kh2 Ra2 6. Kg1 R8a5
7. Rbc1 Kg8 <HT>
13-> 13.27 -2.34 1. ... Bc3 2. Qxd7 Bxd7 3. Rab1 Rxa4
4. Rd1 R4a5 5. Kh2 Ra2 6. Kg1 R8a5
7. Rbc1 Kg8 <HT>
14 21.58 -2.35 1. ... Bc3 2. Qxd7 Bxd7 3. Rab1 Rxa4
4. Rd1 R4a5 5. Kh2 Rxb5 6. Bh3 Bc6
7. Kg2 Ke7 8. Rbc1 Rc5
14-> 25.41 -2.35 1. ... Bc3 2. Qxd7 Bxd7 3. Rab1 Rxa4
4. Rd1 R4a5 5. Kh2 Rxb5 6. Bh3 Bc6
7. Kg2 Ke7 8. Rbc1 Rc5
15 1:28 -2.04 1. ... Bc3 2. Qxb6 Qe7 3. Nh4 Kg8 4.
Bf3 Bb3 5. Bg4 Bf7 6. Bd1 Bxa1 7. Rxa1
R5a7 8. Nf3 <HT>
15-> 2:06 -2.04 1. ... Bc3 2. Qxb6 Qe7 3. Nh4 Kg8 4.
Bf3 Bb3 5. Bg4 Bf7 6. Bd1 Bxa1 7. Rxa1
R5a7 8. Nf3 <HT>
16 5:44 -2.12 1. ... Bc3 2. Qxb6 Qe7 3. Nh4 Kf7 4.
f4 Bxa1 5. Rc7 Bd7 6. Bh3 Bxh3 7. Rxe7+
Kxe7 8. Qc7+ Bd7 9. fxe5 fxe5 10. Qxe5+
Kd8 11. Qh8+ Kc7 12. Qxh7 Rxa4 13.
Nxg6
16-> 6:11 -2.12 1. ... Bc3 2. Qxb6 Qe7 3. Nh4 Kf7 4.
f4 Bxa1 5. Rc7 Bd7 6. Bh3 Bxh3 7. Rxe7+
Kxe7 8. Qc7+ Bd7 9. fxe5 fxe5 10. Qxe5+
Kd8 11. Qh8+ Kc7 12. Qxh7 Rxa4 13.
Nxg6
17 11:57 -1.93 1. ... Bc3 2. Qxb6 Qe7 3. Nh4 Kf7 4.
f4 exf4 5. gxf4 Bxa1 6. Rc7 Bd7 7.
e5 fxe5 8. Nf3 Kg8 9. Nxe5 Qe6 10.
Nxd7
17 20:16 -2.06 1. ... Bc5 2. Qxd7 Bxd7 3. Rab1 Rxa4
4. Nd2 Ra3 5. Nb3 Bd6 6. Bf1 Kf7 7.
Nd2 Rc3 8. Nc4 Bf8 9. f4 Bxh6 10. Nxb6
Rxc1 11. Rxc1
(3) 17-> 20:21 -2.06 1. ... Bc5 2. Qxd7 Bxd7 3. Rab1 Rxa4
4. Nd2 Ra3 5. Nb3 Bd6 6. Bf1 Kf7 7.
Nd2 Rc3 8. Nc4 Bf8 9. f4 Bxh6 10. Nxb6
Rxc1 11. Rxc1
So for my code, thru depth 17, Bc3 and Bc5 are very close. Only after a
monstrous search does Bc5 look .1 better...
If a program plays Bc5 over Bc3 it probably is not due to tactics, but due
to some eval term instead...
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.