Mark Pearce
Joined: 12 Jan 2012 Posts: 61 Location: London, England
|
Post subject: Re: Tough for Engines - Trapped Piece Detection & Zugzwa Posted: Sat Jun 02, 2012 1:44 pm |
|
|
| Steve Maughan wrote: |
5q2/1p1kp3/pP4p1/4B3/3N3K/1B6/P4P2/8 w - - 0 1
The position is really quite deep. The forced win of the Queen is 19 ply. Most of those moves would be regarded as quiet and most forms of selectivity would prune, or aggressively reduce. Most engines struggle, even when shown the first two moves.
From a engine / programming perspective I think the key position is after the following moves:
1. Be6+ Ke8 2. Nf5 gxf5 3. Kg5 f4 4. f3 Kd8
White is a knight down compared to the root position. It isn't zugzwang as black can play a5 with no immediate repercussions. The queen has a safe square to move to as it looks as if she can move to e8 (although it's mate in 1).So aggressive pruning is likely. I think this is difficult for engines to see past this position from the root.
I think only the engines with highly developed code for detecting trapped pieces and zugzwang are able to see it.
Any thoughts?
Steve |
Moving on 2 ply from your initial position (i.e. Be6+, Ke8), Houdini 2.0 finds the win of the Black queen in 14 minutes. This is using 2 cores and 1 GB cache on a i7 2600K. I will now try it on your initial position. _________________ Theory is when you know something, but it doesn't work. Practice is when something works, but you don't know why. Chess programmers combine theory and practice: Nothing works and they don't know why. |
|