Author: Omid David Tabibi
Date: 04:07:32 05/01/04
Go up one level in this thread
On April 30, 2004 at 23:04:24, Andrew Wagner wrote:
>Here's the position:
>
>[d] 8/7p/5k2/5p2/p1p2P2/Pr1pPK2/1P1R3P/8 b - -
>
Falcon finds it at depth 11:
Falcon 1.0.12.7 running on GenuineIntel 733MHz 256MB:
depth time nodes nps score variation
8/15 0.20 25k 127k 1.71 1...b3b8 1.e3e4 f5e4 2.f3e4 b8e8
3.e4f3 f6f5 4.d2g2 e8d8 5.f3e3
9/17 0.29 42k 147k 1.52 1...b3b8 1.e3e4 f5e4 2.f3e4 b8e8
3.e4d5 e8e2 4.d2d1 e2c2 5.h2h3 f6f5
10/19 0.73 134k 184k 1.52 1...b3b8 1.e3e4 f5e4 2.f3e4 b8e8
3.e4d5 e8e2 4.d2d1 e2c2 5.h2h3 f6f5
6.d1f1 c2b2 7.d5c4
11/20 1.59 328k 206k 1.52 1...b3b8 1.e3e4 f5e4 2.f3e4 b8e8
3.e4d5 e8e2 4.d2d1 e2c2 5.h2h3 f6f5
6.d1f1 c2b2 7.d5c4
11/24 2.85 608k 213k 1.53 1...b3b2++
12/28 3.50 755k 216k 1.83 1...b3b2++
12/28 4.07 886k 217k 2.43 1...b3b2++
12/29 4.77 1037k 217k 1.72 1...b3b2 1.d2b2 c4c3 2.b2b6 f6e7
3.b6b7 e7d6 4.b7b6 d6c7 5.b6f6 c3c2
6.f6f7 c7c6 7.f7f6 c6d5 8.f6f5
13/26 6.44 1393k 216k 2.02 1...b3b2++
13/28 7.56 1651k 218k 2.62 1...b3b2++
13/31 9.58 2107k 219k 4.08 1...b3b2 1.d2b2 c4c3 2.b2b6 f6e7
3.b6b7 e7d6 4.b7b6 d6c7 5.b6h6 c3c2
6.h6h7 c7b6 7.h7h6 b6b5 8.h6f6 c2c1q
9.f6f5 b5c6 10.f5f6 c6d5
14/32 12.55 2747k 218k 4.38 1...b3b2++
14/36 17.61 3879k 220k 4.98 1...b3b2++
14/37 20.33 4474k 220k 4.98 1...b3b2 1.d2b2 c4c3 2.b2b6 f6e7
3.b6b7 e7d6 4.b7b6 d6c5 5.b6b8 c3c2
6.b8c8 c5b6 7.f3f2 d3d2 8.c8c2 d2d1q
9.c2a2 b6c5 10.a2b2
15/41 39.75 8682k 218k 5.00 1...b3b2 1.d2b2 c4c3 2.b2b6 f6e7
3.f3f2 c3c2 4.b6c6 e7d7 5.c6c5 d3d2
6.c5c2 d2d1q 7.c2c5 d7d6 8.c5e5 d1h5
9.f2g3
>The move to find here is Rxb2. My question is...what ply does your program find
>the solution on? To tactically work it out to see that you can force queening
>requires something like 13 or 14 ply. This is an interesting knowledge vs.
>search position...can you special-case this somehow to find it sooner? The
>problem is, as an FM friend of mine pointed out, if the king were just a bit
>closer, the sac is losing. E.g. In this position:
>
>[d] 8/7p/5k2/5p2/p1p2P2/Pr1p1K2/1P1R3P/8 b - - (white pawn missing on e3)
>...the sac would be losing because the king is close enough to stop the pawns.
>So my first inclination to somehow make the static eval see that the pawns were
>worth being down a pawn seems to be bad. Any thoughts?
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.