These two positions are supposed to be a mate in 19.
Can any engine find it?
[d]3K4/1p5p/1p6/8/8/1B6/1p6/b1k3B1 w - - acd 29; acs 385; c0 "Analyzing engine Rybka 2.3.2a"; ce 0.00; dm 19; id "ChestDB.5659"; pm Be3+; pm Bg1e3+; pv Be3+ Kb1 Bd4 h5 Kc7 b5 Kb6 h4 Kxb5 h3 Bd5 h2 Bxb7 Kc2;
Longer analysis on the above engine with Rybka got a ce of +0.35 pawns, but hardly a checkmate score.
[d]4k3/8/3Q4/8/8/8/3p1pp1/3Kbrrb w - - acd 38; acs 385; c0 "Analyzing engine Rybka 2.3.2a"; ce 0.00; dm 19; id "ChestDB.5643"; pm Qe6+; pm Qd6e6+; pv Qe6+ Kd8 Qd6+ Kc8 Qc6+ Kb8 Qb6+ Kc8 Qc6+ Kb8 Qb6+ Kc8 Qc6+ Kb8;
Rybka says draw.
Mate in 19
Moderator: Ras
-
Edmund
- Posts: 670
- Joined: Mon Dec 03, 2007 3:01 pm
- Location: Barcelona, Spain
Re: Mate in 19
Probably easier for a human to see than for a machine.
In the second one the Wqueen has to drive the Bking to h2 and then mate on h4
In the second one the Wqueen has to drive the Bking to h2 and then mate on h4
-
Dann Corbit
- Posts: 12799
- Joined: Wed Mar 08, 2006 8:57 pm
- Location: Redmond, WA USA
Re: Mate in 19
How can she drive him there without the king to help (who is logically pinned).
-
Edmund
- Posts: 670
- Joined: Mon Dec 03, 2007 3:01 pm
- Location: Barcelona, Spain
Re: Mate in 19
The main problem is getting the King out of the corner but it works ..
1. Qc7 Kf8 2. Qd7 Kg8 3. Qe7 Kh8 4. Qg5 Kh7 5. Qe5 Kg8
6. Qf6 Kh7 7. Qf8 Kg6 8. Qe7 Kh6 9. Qf7 Kg5 10. Qe6 Kf4
11. Qd5 Kg4 12. Qe5 Kh4 13. Qf5 Kg3 14. Qf7 Kg4 15. Qf6 Kg3
16. Qf5 Kh2 17. Qe5 Kh3 18. Qg5 Kh2 19. Qh4#
1. Qc7 Kf8 2. Qd7 Kg8 3. Qe7 Kh8 4. Qg5 Kh7 5. Qe5 Kg8
6. Qf6 Kh7 7. Qf8 Kg6 8. Qe7 Kh6 9. Qf7 Kg5 10. Qe6 Kf4
11. Qd5 Kg4 12. Qe5 Kh4 13. Qf5 Kg3 14. Qf7 Kg4 15. Qf6 Kg3
16. Qf5 Kh2 17. Qe5 Kh3 18. Qg5 Kh2 19. Qh4#
-
hgm
- Posts: 28405
- Joined: Fri Mar 10, 2006 10:06 am
- Location: Amsterdam
- Full name: H G Muller
Re: Mate in 19
Now the 64-dollar question of course is: could engines be made so smart that this becomes as easy to them as it is to humans?
Normally we search each branch leading from a node with equal depth (barring extensions or reductions). The most common situation where this fails badly is in conversion to Pawn endings: if the root has, say, Queens on the board, the branchess where these are not traed eat up all the nodes, so that you don't reach enough depth to see if the Pawn ending in the branches where you do trade is badly won or lost. (Unless you cheat by having recognizers in you eval, or probe EGTs, of course). The promoto will be outside the horizon. For this reason many people extend after trading of te last non-Pawn material by 3 or 4 ply, or even double remaining plies.
The problem in the position above is similar: branches where you unleash the trapped black materal quickly eat up all nodes, so that t branches where the material stays trapped do not reach the required depth. To prevent that, you could go to a search that is not controlled by depth, but by a node budget. Divide all nodes that are available equally over all daughter nodes (or unequally, if you want to implement the equivalent to extensions and reductions).
Note that alpha-beta pruning and hash cutoffs would make that the number of nodes actually searched would be only a very small fraction of the node budget: the budget rellay accounts for the size of the sub-trees as they would have been without any pruning. So if the ranching factor would be 30 everywhere, you have to give a node budget in the root of 30^12 to reach 12 ply. This woud then pass a node budget of 30^11 to each node after 1 ply. When the budget reaches 1, you do QS.
Actually, the depth in ply is the (base 30) logarithm of the node budget. So this is actually equivalent to accounting remaining search depth in fractional plies, and counting each ply made as log(nrOfMoves). And this again is a generalization of the singular extension, as log(1)=0, and a move made in a situation when there is only a single legal move is not counted in the ply depth t all.
As the branch that leads to the mate leaves black only a single move in most of nodes along the path, it would be extended to about twice the depth of most other branches, as the black moves are efectively not counted. While the nominal depth reached would hardly suffer. I guess this should bring the mate in the horizon fast enough. (It would require some form of verified null-move pruning, though, to recognize the zugzwang.)
Normally we search each branch leading from a node with equal depth (barring extensions or reductions). The most common situation where this fails badly is in conversion to Pawn endings: if the root has, say, Queens on the board, the branchess where these are not traed eat up all the nodes, so that you don't reach enough depth to see if the Pawn ending in the branches where you do trade is badly won or lost. (Unless you cheat by having recognizers in you eval, or probe EGTs, of course). The promoto will be outside the horizon. For this reason many people extend after trading of te last non-Pawn material by 3 or 4 ply, or even double remaining plies.
The problem in the position above is similar: branches where you unleash the trapped black materal quickly eat up all nodes, so that t branches where the material stays trapped do not reach the required depth. To prevent that, you could go to a search that is not controlled by depth, but by a node budget. Divide all nodes that are available equally over all daughter nodes (or unequally, if you want to implement the equivalent to extensions and reductions).
Note that alpha-beta pruning and hash cutoffs would make that the number of nodes actually searched would be only a very small fraction of the node budget: the budget rellay accounts for the size of the sub-trees as they would have been without any pruning. So if the ranching factor would be 30 everywhere, you have to give a node budget in the root of 30^12 to reach 12 ply. This woud then pass a node budget of 30^11 to each node after 1 ply. When the budget reaches 1, you do QS.
Actually, the depth in ply is the (base 30) logarithm of the node budget. So this is actually equivalent to accounting remaining search depth in fractional plies, and counting each ply made as log(nrOfMoves). And this again is a generalization of the singular extension, as log(1)=0, and a move made in a situation when there is only a single legal move is not counted in the ply depth t all.
As the branch that leads to the mate leaves black only a single move in most of nodes along the path, it would be extended to about twice the depth of most other branches, as the black moves are efectively not counted. While the nominal depth reached would hardly suffer. I guess this should bring the mate in the horizon fast enough. (It would require some form of verified null-move pruning, though, to recognize the zugzwang.)
-
Jouni
- Posts: 3715
- Joined: Wed Mar 08, 2006 8:15 pm
- Full name: Jouni Uski
Re: Mate in 19
All Rybka versions are unsuitable for mate solving. Maybe Rybka 3+ if it ever appears? Chest is stunning:
ChestUCI:
FEN: 3K4/1p5p/1p6/8/8/1B6/1p6/b1k3B1 w - - (3+6)
Position-Analysis: C0/R0/K3/P4/X9 W:3/20
AutoTurbo-Search for Special-Mate [C1/R0/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Search for Special-Mate [C0/R1/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Search for Special-Mate [C0/R2/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Search for Special-Mate [C0/R-2/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Search for Special-Mate [C0/R3/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Search for Special-Mate [C0/R-3/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Search for Special-Mate [C0/R4/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Search for Special-Mate [C0/R-4/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Search for Special-Mate [C0/R0/K0/P0/X1] in 19 ... (Hash=512MB)
AutoTurbo-Search for Special-Mate [C0/R0/K0/P0/X2] in 19 ... (Hash=512MB)
19/19 00:10 637.979 607.020 +M19 1.Bg1e3+
AutoTurbo-Search for Special-Mate [C0/R0/K3/P0/X2] in 19 ... (Hash=512MB)
19/19 00:12 637.979 601.299 +M19 1.Bg1e3+
AutoTurbo-Search for Special-Mate [C0/R0/K3/P2/X2] in 19 ... (Hash=512MB)
19/19 00:14 637.979 607.020 +M19 1.Bg1e3+
Mate in 19 found ! (1 Solution in 00:01)
19/19 00:14 1.166.164 609.918 +M19 1.Bg1e3+ Kc1b1 2.Be3h6 b6b5 3.Kd8e7 b5b4 4.Ke7f6 b7b5 5.Kf6g5 Kb1c1 6.Kg5f5+ Kc1b1 7.Kf5f4 Kb1c1 8.Kf4e4+ Kc1b1 9.Ke4e3 Kb1c1 10.Ke3d3+ Kc1b1 11.Bb3d5 b4b3 12.Bd5xb3 b5b4 13.Bb3c4 b4b3 14.Kd3c3 Kb1a2 15.Bc4xb3+ Ka2b1 16.Bh6f4 h7h6 17.Bb3c4 h6h5 18.Kc3b3 h5h4 19.Bc4d3+
And second:
FEN: 4k3/8/3Q4/8/8/8/3p1pp1/3Kbrrb w - - 0 1
ChestUCI:
FEN: 4k3/8/3Q4/8/8/8/3p1pp1/3Kbrrb w - - (2+8)
Position-Analysis: C0/R0/K2/P1/X1 W:2/26
AutoTurbo-Search for Special-Mate [C1/R0/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Search for Special-Mate [C0/R1/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Search for Special-Mate [C0/R2/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Search for Special-Mate [C0/R-2/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Search for Special-Mate [C0/R3/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Search for Special-Mate [C0/R-3/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Search for Special-Mate [C0/R4/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Search for Special-Mate [C0/R-4/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Search for Special-Mate [C0/R0/K0/P0/X1] in 19 ... (Hash=512MB)
AutoTurbo-Search for Special-Mate [C0/R0/K0/P0/X2] in 19 ... (Hash=512MB)
AutoTurbo-Search for Special-Mate [C0/R0/K0/P0/X3] in 19 ... (Hash=512MB)
19/19 00:06 18.567 464.174 +M19 1.Qd6c7
AutoTurbo-Search for Special-Mate [C0/R0/K4/P0/X3] in 19 ... (Hash=512MB)
19/19 00:07 90.079 360.315 +M19 1.Qd6c7
AutoTurbo-Search for Special-Mate [C0/R0/K4/P1/X3] in 19 ... (Hash=512MB)
19/19 00:07 90.079 360.315 +M19 1.Qd6c7
Mate in 19 found ! (1 Solution in 00:00)
19/19 00:07 90.079 360.315 +M19 1.Qd6c7 Ke8f8 2.Qc7d7 Kf8g8 3.Qd7e7 Kg8h8 4.Qe7g5 Kh8h7 5.Qg5e5 Kh7g8 6.Qe5f6 Kg8h7 7.Qf6f8 Kh7g6 8.Qf8e7 Kg6h6 9.Qe7f7 Kh6g5 10.Qf7e6 Kg5h5 11.Qe6f6 Kh5g4 12.Qf6e5 Kg4h4 13.Qe5f4+ Kh4h5 14.Qf4g3 Kh5h6 15.Qg3g8 Kh6h5 16.Qg8g7 Kh5h4 17.Qg7g6 Kh4h3 18.Qg6g5 Kh3h2 19.Qg5h4+
Jouni
ChestUCI:
FEN: 3K4/1p5p/1p6/8/8/1B6/1p6/b1k3B1 w - - (3+6)
Position-Analysis: C0/R0/K3/P4/X9 W:3/20
AutoTurbo-Search for Special-Mate [C1/R0/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Search for Special-Mate [C0/R1/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Search for Special-Mate [C0/R2/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Search for Special-Mate [C0/R-2/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Search for Special-Mate [C0/R3/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Search for Special-Mate [C0/R-3/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Search for Special-Mate [C0/R4/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Search for Special-Mate [C0/R-4/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Search for Special-Mate [C0/R0/K0/P0/X1] in 19 ... (Hash=512MB)
AutoTurbo-Search for Special-Mate [C0/R0/K0/P0/X2] in 19 ... (Hash=512MB)
19/19 00:10 637.979 607.020 +M19 1.Bg1e3+
AutoTurbo-Search for Special-Mate [C0/R0/K3/P0/X2] in 19 ... (Hash=512MB)
19/19 00:12 637.979 601.299 +M19 1.Bg1e3+
AutoTurbo-Search for Special-Mate [C0/R0/K3/P2/X2] in 19 ... (Hash=512MB)
19/19 00:14 637.979 607.020 +M19 1.Bg1e3+
Mate in 19 found ! (1 Solution in 00:01)
19/19 00:14 1.166.164 609.918 +M19 1.Bg1e3+ Kc1b1 2.Be3h6 b6b5 3.Kd8e7 b5b4 4.Ke7f6 b7b5 5.Kf6g5 Kb1c1 6.Kg5f5+ Kc1b1 7.Kf5f4 Kb1c1 8.Kf4e4+ Kc1b1 9.Ke4e3 Kb1c1 10.Ke3d3+ Kc1b1 11.Bb3d5 b4b3 12.Bd5xb3 b5b4 13.Bb3c4 b4b3 14.Kd3c3 Kb1a2 15.Bc4xb3+ Ka2b1 16.Bh6f4 h7h6 17.Bb3c4 h6h5 18.Kc3b3 h5h4 19.Bc4d3+
And second:
FEN: 4k3/8/3Q4/8/8/8/3p1pp1/3Kbrrb w - - 0 1
ChestUCI:
FEN: 4k3/8/3Q4/8/8/8/3p1pp1/3Kbrrb w - - (2+8)
Position-Analysis: C0/R0/K2/P1/X1 W:2/26
AutoTurbo-Search for Special-Mate [C1/R0/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Search for Special-Mate [C0/R1/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Search for Special-Mate [C0/R2/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Search for Special-Mate [C0/R-2/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Search for Special-Mate [C0/R3/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Search for Special-Mate [C0/R-3/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Search for Special-Mate [C0/R4/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Search for Special-Mate [C0/R-4/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Search for Special-Mate [C0/R0/K0/P0/X1] in 19 ... (Hash=512MB)
AutoTurbo-Search for Special-Mate [C0/R0/K0/P0/X2] in 19 ... (Hash=512MB)
AutoTurbo-Search for Special-Mate [C0/R0/K0/P0/X3] in 19 ... (Hash=512MB)
19/19 00:06 18.567 464.174 +M19 1.Qd6c7
AutoTurbo-Search for Special-Mate [C0/R0/K4/P0/X3] in 19 ... (Hash=512MB)
19/19 00:07 90.079 360.315 +M19 1.Qd6c7
AutoTurbo-Search for Special-Mate [C0/R0/K4/P1/X3] in 19 ... (Hash=512MB)
19/19 00:07 90.079 360.315 +M19 1.Qd6c7
Mate in 19 found ! (1 Solution in 00:00)
19/19 00:07 90.079 360.315 +M19 1.Qd6c7 Ke8f8 2.Qc7d7 Kf8g8 3.Qd7e7 Kg8h8 4.Qe7g5 Kh8h7 5.Qg5e5 Kh7g8 6.Qe5f6 Kg8h7 7.Qf6f8 Kh7g6 8.Qf8e7 Kg6h6 9.Qe7f7 Kh6g5 10.Qf7e6 Kg5h5 11.Qe6f6 Kh5g4 12.Qf6e5 Kg4h4 13.Qe5f4+ Kh4h5 14.Qf4g3 Kh5h6 15.Qg3g8 Kh6h5 16.Qg8g7 Kh5h4 17.Qg7g6 Kh4h3 18.Qg6g5 Kh3h2 19.Qg5h4+
Jouni
-
Uri Blass
- Posts: 10940
- Joined: Thu Mar 09, 2006 12:37 am
- Location: Tel-Aviv Israel
Re: Mate in 19
The second position is clearly a good candidate for movei for the following reasons:Dann Corbit wrote:These two positions are supposed to be a mate in 19.
Can any engine find it?
[d]3K4/1p5p/1p6/8/8/1B6/1p6/b1k3B1 w - - acd 29; acs 385; c0 "Analyzing engine Rybka 2.3.2a"; ce 0.00; dm 19; id "ChestDB.5659"; pm Be3+; pm Bg1e3+; pv Be3+ Kb1 Bd4 h5 Kc7 b5 Kb6 h4 Kxb5 h3 Bd5 h2 Bxb7 Kc2;
Longer analysis on the above engine with Rybka got a ce of +0.35 pawns, but hardly a checkmate score.
[d]4k3/8/3Q4/8/8/8/3p1pp1/3Kbrrb w - - acd 38; acs 385; c0 "Analyzing engine Rybka 2.3.2a"; ce 0.00; dm 19; id "ChestDB.5643"; pm Qe6+; pm Qd6e6+; pv Qe6+ Kd8 Qd6+ Kc8 Qc6+ Kb8 Qb6+ Kc8 Qc6+ Kb8 Qb6+ Kc8 Qc6+ Kb8;
Rybka says draw.
1)Movei does not use null move pruning when the number of legal moves of the opponent is very small.
2)Movei is using a single reply partial extension.
Movei is not a good counter of number of moves to mate after I add using hash for pruning and clearly did not do it correctly(but it was productive for playing strength) but it clearly can see a mate score and I believe it can practically win(maybe earlier versions of movei can see the correct number of moves)
New game
[d]4k3/8/3Q4/8/8/8/3p1pp1/3Kbrrb w - - 0 1
Analysis by Movei00_8_438:
1.Qd6-c7
-+ (-13.81) Depth: 1 00:00:00
1.Qd6-c7
-+ (-13.51) Depth: 2 00:00:00
1.Qd6-c7 Ke8-f8 2.Qc7-d7 Kf8-g8
-+ (-13.40) Depth: 2 00:00:00
1.Qd6-c7 Ke8-f8 2.Qc7-d7 Kf8-g8
-+ (-13.40) Depth: 2 00:00:00
1.Qd6-c7
-+ (-13.10) Depth: 3 00:00:00
1.Qd6-c7
-+ (-12.40) Depth: 3 00:00:00
1.Qd6-c7 Ke8-f8 2.Qc7-h7 Kf8-e8 3.Qh7-c7
= (0.00) Depth: 3 00:00:00
1.Qd6-c7 Ke8-f8 2.Qc7-h7 Kf8-e8 3.Qh7-c7
= (0.00) Depth: 3 00:00:00
1.Qd6-c7
³ (-0.30) Depth: 4 00:00:01
1.Qd6-c7
µ (-1.00) Depth: 4 00:00:01
1.Qd6-c7 Ke8-f8 2.Qc7-h7 Kf8-e8 3.Qh7-c7
= (0.00) Depth: 4 00:00:01
1.Qd6-c7 Ke8-f8 2.Qc7-h7 Kf8-e8 3.Qh7-c7
= (0.00) Depth: 4 00:00:01
1.Qd6-c7
³ (-0.30) Depth: 5 00:00:01
1.Qd6-c7
µ (-1.00) Depth: 5 00:00:01
1.Qd6-c7 Ke8-f8 2.Qc7-h7 Kf8-e8 3.Qh7-c7
= (0.00) Depth: 5 00:00:01
1.Qd6-c7 Ke8-f8 2.Qc7-h7 Kf8-e8 3.Qh7-c7
= (0.00) Depth: 5 00:00:01
1.Qd6-c7
³ (-0.30) Depth: 6 00:00:01 5kN
1.Qd6-c7
µ (-1.00) Depth: 6 00:00:02 5kN
1.Qd6-c7 Ke8-f8 2.Qc7-h7 Kf8-e8 3.Qh7-c7
= (0.00) Depth: 6 00:00:02 5kN
1.Qd6-c7 Ke8-f8 2.Qc7-h7 Kf8-e8 3.Qh7-c7
= (0.00) Depth: 6 00:00:02 6kN
1.Qd6-c7
³ (-0.30) Depth: 7 00:00:02 7kN
1.Qd6-c7
µ (-1.00) Depth: 7 00:00:02 8kN
1.Qd6-c7 Ke8-f8 2.Qc7-h7 Kf8-e8 3.Qh7-c7
= (0.00) Depth: 7 00:00:02 9kN
1.Qd6-c7 Ke8-f8 2.Qc7-h7 Kf8-e8 3.Qh7-c7
= (0.00) Depth: 7 00:00:02 14kN
1.Qd6-c7 Ke8-f8 2.Qc7-h7 Kf8-e8 3.Qh7-c7
= (0.00) Depth: 8 00:00:03 16kN
1.Qd6-c7 Ke8-f8 2.Qc7-h7 Kf8-e8 3.Qh7-c7
= (0.00) Depth: 8 00:00:03 23kN
1.Qd6-c7 Ke8-f8 2.Qc7-h7 Kf8-e8 3.Qh7-c7
= (0.00) Depth: 9 00:00:03 26kN
1.Qd6-c7 Ke8-f8 2.Qc7-h7 Kf8-e8 3.Qh7-c7
= (0.00) Depth: 9 00:00:03 38kN
1.Qd6-c7 Ke8-f8 2.Qc7-h7 Kf8-e8 3.Qh7-c7
= (0.00) Depth: 10 00:00:03 43kN
1.Qd6-c7 Ke8-f8 2.Qc7-h7 Kf8-e8 3.Qh7-c7
= (0.00) Depth: 10 00:00:03 61kN
1.Qd6-c7 Ke8-f8 2.Qc7-h7 Kf8-e8 3.Qh7-c7
= (0.00) Depth: 11 00:00:03 67kN
1.Qd6-c7 Ke8-f8 2.Qc7-h7 Kf8-e8 3.Qh7-c7
= (0.00) Depth: 11 00:00:03 92kN
1.Qd6-c7 Ke8-f8 2.Qc7-h7 Kf8-e8 3.Qh7-c7
= (0.00) Depth: 12 00:00:04 101kN
1.Qd6-c7 Ke8-f8 2.Qc7-h7 Kf8-e8 3.Qh7-c7
= (0.00) Depth: 12 00:00:04 139kN
1.Qd6-c7 Ke8-f8 2.Qc7-h7 Kf8-e8 3.Qh7-c7
= (0.00) Depth: 13 00:00:05 150kN
1.Qd6-c7 Ke8-f8 2.Qc7-h7 Kf8-e8 3.Qh7-c7
= (0.00) Depth: 13 00:00:08 213kN
1.Qd6-c7 Ke8-f8 2.Qc7-h7 Kf8-e8 3.Qh7-c7
= (0.00) Depth: 14 00:00:08 232kN
1.Qd6-c7 Ke8-f8 2.Qc7-h7 Kf8-e8 3.Qh7-c7
= (0.00) Depth: 14 00:00:10 337kN
1.Qd6-c7 Ke8-f8 2.Qc7-h7 Kf8-e8 3.Qh7-c7
= (0.00) Depth: 15 00:00:10 367kN
1.Qd6-c7 Ke8-f8 2.Qc7-h7 Kf8-e8 3.Qh7-c7
= (0.00) Depth: 15 00:00:12 533kN
1.Qd6-c7 Ke8-f8 2.Qc7-h7 Kf8-e8 3.Qh7-c7
= (0.00) Depth: 16 00:00:13 579kN
1.Qd6-c7 Ke8-f8 2.Qc7-h7 Kf8-e8 3.Qh7-c7
= (0.00) Depth: 16 00:00:14 839kN
1.Qd6-c7 Ke8-f8 2.Qc7-h7 Kf8-e8 3.Qh7-c7
= (0.00) Depth: 17 00:00:14 907kN
1.Qd6-c7 Ke8-f8 2.Qc7-h7 Kf8-e8 3.Qh7-c7
= (0.00) Depth: 17 00:00:16 1297kN
1.Qd6-c7 Ke8-f8 2.Qc7-h7 Kf8-e8 3.Qh7-c7
= (0.00) Depth: 18 00:00:16 1399kN
1.Qd6-c7 Ke8-f8 2.Qc7-h7 Kf8-e8 3.Qh7-c7
= (0.00) Depth: 18 00:00:18 1974kN
1.Qd6-c7 Ke8-f8 2.Qc7-h7 Kf8-e8 3.Qh7-c7
= (0.00) Depth: 19 00:00:18 2100kN
1.Qd6-c7 Ke8-f8 2.Qc7-h7 Kf8-e8 3.Qh7-c7
= (0.00) Depth: 19 00:00:20 2930kN
1.Qd6-c7 Ke8-f8 2.Qc7-h7 Kf8-e8 3.Qh7-c7
= (0.00) Depth: 20 00:00:20 3091kN
1.Qd6-c7 Ke8-f8 2.Qc7-h7 Kf8-e8 3.Qh7-c7
= (0.00) Depth: 20 00:00:22 4278kN
1.Qd6-c7 Ke8-f8 2.Qc7-h7 Kf8-e8 3.Qh7-c7
= (0.00) Depth: 21 00:00:22 4532kN
1.Qd6-c7 Ke8-f8 2.Qc7-h7 Kf8-e8 3.Qh7-c7
= (0.00) Depth: 21 00:00:26 6545kN
1.Qd6-c7 Ke8-f8 2.Qc7-d7 Kf8-g8 3.Qd7-e7 Kg8-h8 4.Qe7-f8+ Kh8-h7 5.Qf8-f7+ Kh7-h8 6.Qf7-e7 Kh8-g8 7.Qe7-f6
= (0.01) Depth: 22 00:00:27 7063kN
1.Qd6-c7 Ke8-f8 2.Qc7-d7 Kf8-g8 3.Qd7-e7 Kg8-h8 4.Qe7-f8+ Kh8-h7 5.Qf8-f7+ Kh7-h8 6.Qf7-e7 Kh8-g8 7.Qe7-f6
= (0.01) Depth: 22 00:00:33 9603kN
1.Qd6-c7 Ke8-f8 2.Qc7-d7 Kf8-g8 3.Qd7-e7 Kg8-h8 4.Qe7-f8+ Kh8-h7 5.Qf8-f7+ Kh7-h8 6.Qf7-e7 Kh8-g8 7.Qe7-f6
= (0.01) Depth: 23 00:00:35 10418kN
1.Qd6-c7 Ke8-f8 2.Qc7-d7 Kf8-g8 3.Qd7-e7 Kg8-h8 4.Qe7-f8+ Kh8-h7 5.Qf8-f7+ Kh7-h8 6.Qf7-e7 Kh8-g8 7.Qe7-f6
= (0.01) Depth: 23 00:00:49 14280kN
1.Qd6-c7 Ke8-f8 2.Qc7-d7 Kf8-g8 3.Qd7-e7 Kg8-h8 4.Qe7-f8+ Kh8-h7 5.Qf8-f7+ Kh7-h8 6.Qf7-e7 Kh8-g8 7.Qe7-f6
= (0.01) Depth: 24 00:00:53 15498kN
1.Qd6-c7 Ke8-f8 2.Qc7-d7 Kf8-g8 3.Qd7-e7 Kg8-h8 4.Qe7-f8+ Kh8-h7 5.Qf8-f7+ Kh7-h8 6.Qf7-e7 Kh8-g8 7.Qe7-f6
= (0.01) Depth: 24 00:01:07 20615kN
1.Qd6-c7 Ke8-f8 2.Qc7-d7 Kf8-g8 3.Qd7-e7 Kg8-h8 4.Qe7-f8+ Kh8-h7 5.Qf8-f7+ Kh7-h8 6.Qf7-e7 Kh8-g8 7.Qe7-f6
= (0.01) Depth: 25 00:01:18 22084kN
1.Qd6-c7 Ke8-f8 2.Qc7-d7 Kf8-g8 3.Qd7-e7 Kg8-h8 4.Qe7-f8+ Kh8-h7 5.Qf8-f7+ Kh7-h8 6.Qf7-e7 Kh8-g8 7.Qe7-f6
= (0.01) Depth: 25 00:01:46 29104kN
1.Qd6-c7
² (0.31) Depth: 26 00:01:46 29104kN
1.Qd6-c7 Ke8-f8 2.Qc7-d7 Kf8-g8 3.Qd7-e7 Kg8-h8 4.Qe7-f8+ Kh8-h7 5.Qf8-f7+ Kh7-h8 6.Qf7-e7 Kh8-g8 7.Qe7-f6 Kg8-h7 8.Qf6-f8
² (0.31) Depth: 26 00:01:58 33390kN
1.Qd6-c7 Ke8-f8 2.Qc7-d7 Kf8-g8 3.Qd7-e7 Kg8-h8 4.Qe7-f8+ Kh8-h7 5.Qf8-f7+ Kh7-h8 6.Qf7-e7 Kh8-g8 7.Qe7-f6 Kg8-h7 8.Qf6-f8
² (0.31) Depth: 26 00:02:32 43624kN
1.Qd6-c7 Ke8-f8 2.Qc7-d7 Kf8-g8 3.Qd7-e7 Kg8-h8 4.Qe7-f8+ Kh8-h7 5.Qf8-f7+ Kh7-h8 6.Qf7-e7 Kh8-g8 7.Qe7-f6 Kg8-h7 8.Qf6-f8
² (0.31) Depth: 27 00:02:40 46330kN
1.Qd6-c7 Ke8-f8 2.Qc7-d7 Kf8-g8 3.Qd7-e7 Kg8-h8 4.Qe7-f8+ Kh8-h7 5.Qf8-f7+ Kh7-h8 6.Qf7-e7 Kh8-g8 7.Qe7-f6 Kg8-h7 8.Qf6-f8
² (0.31) Depth: 27 00:03:22 59704kN
1.Qd6-c7
² (0.61) Depth: 28 00:03:29 62290kN
1.Qd6-c7 Ke8-f8 2.Qc7-d7 Kf8-g8 3.Qd7-e7 Kg8-h8 4.Qe7-f8+ Kh8-h7 5.Qf8-f7+ Kh7-h8 6.Qf7-e7 Kh8-g8 7.Qe7-f6 Kg8-h7
² (0.61) Depth: 28 00:04:44 84838kN
1.Qd6-c7 Ke8-f8 2.Qc7-d7 Kf8-g8 3.Qd7-e7 Kg8-h8 4.Qe7-f8+ Kh8-h7 5.Qf8-f7+ Kh7-h8 6.Qf7-e7 Kh8-g8 7.Qe7-f6 Kg8-h7
² (0.61) Depth: 28 00:05:54 107946kN
1.Qd6-c7
± (0.91) Depth: 29 00:05:55 108364kN
1.Qd6-c7
+- (1.61) Depth: 29 00:05:55 108364kN
1.Qd6-c7 Ke8-f8 2.Qc7-d7 Kf8-g8 3.Qd7-e7 Kg8-h8 4.Qe7-f8+ Kh8-h7 5.Qf8-f7+ Kh7-h8 6.Qf7-e7 Kh8-g8 7.Qe7-f6 Kg8-h7 8.Qf6-f8 Kh7-g6 9.Qf8-e7 Kg6-h6 10.Qe7-f7 Kh6-g5 11.Qf7-e6 Kg5-f4 12.Qe6-d5 Kf4-g4 13.Qd5-e5 Kg4-f3 14.Qe5-d4 Kf3-g3 15.Qd4-e4 Kg3-h3 16.Qe4-e6+ Kh3-g3
+- (#10) Depth: 29 00:07:04 132837kN
(so k, 04.04.2009)
Uri
-
Dann Corbit
- Posts: 12799
- Joined: Wed Mar 08, 2006 8:57 pm
- Location: Redmond, WA USA
Re: Mate in 19
What are the exact UCI settings you use to achieve these results?
-
Jouni
- Posts: 3715
- Joined: Wed Mar 08, 2006 8:15 pm
- Full name: Jouni Uski
Re: Mate in 19
You talkin' to me? 
Autoturbo search for mate in 19 with XKP search order.
Jouni
Autoturbo search for mate in 19 with XKP search order.
Jouni
-
kgburcham
- Posts: 2016
- Joined: Sun Feb 17, 2008 4:19 pm
Dan question
Did Chest pull this out of an internal database?
I ran this for myself----amazing result in 0 time
I will spend more time learning Chest settings.
[d] 3K4/1p5p/1p6/8/8/1B6/1p6/b1k3B1 w - - (3+6)
Stellungs-Analyse: C0/R0/K3/P4/X9 W:3/20
Parameter in Datenbank gefunden: #19; 00:10 @ C2/R0/K3/P2/X2;
AutoTurbo-Suche nach Spezial-Matt [C1/R0/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Suche nach Spezial-Matt [C0/R1/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Suche nach Spezial-Matt [C0/R2/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Suche nach Spezial-Matt [C0/R-2/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Suche nach Spezial-Matt [C0/R3/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Suche nach Spezial-Matt [C0/R-3/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Suche nach Spezial-Matt [C0/R0/K0/P0/X1] in 19 ... (Hash=512MB)
AutoTurbo-Suche nach Spezial-Matt [C0/R0/K0/P0/X2] in 19 ... (Hash=512MB)
AutoTurbo-Suche nach Spezial-Matt [C0/R0/K3/P0/X2] in 19 ... (Hash=512MB)
19/19 0:00 +M19 1.Be3+ Kb1 2.Bh6 b5 3.Ke7 b4 4.Kf6 b5 5.Kg5 Kc1 6.Kf5+ Kb1 7.Kf4 Kc1 8.Ke4+ Kb1 9.Ke3 Kc1 10.Kd3+ Kb1 11.Bd5 b3 12.Bxb3 b4 13.Bc4 b3 14.Kc3 1287
19.01 0:00 +M19 1.Be3+ 1287
19/19 0:00 +M19 1.Be3+ Kb1 2.Bh6 b5 3.Ke7 b4 4.Kf6 b5 5.Kg5 Kc1 6.Kf5+ Kb1 7.Kf4 Kc1 8.Ke4+ Kb1 9.Ke3 Kc1 10.Kd3+ Kb1 11.Bd5 b3 12.Bxb3 b4 13.Bc4 b3 14.Kc3 1287
AutoTurbo-Suche nach Spezial-Matt [C0/R0/K3/P2/X2] in 19 ... (Hash=512MB)
19.01 0:00 +M19 1.Be3+ 1287
19/19 0:00 +M19 1.Be3+ Kb1 2.Bh6 b5 3.Ke7 b4 4.Kf6 b5 5.Kg5 Kc1 6.Kf5+ Kb1 7.Kf4 Kc1 8.Ke4+ Kb1 9.Ke3 Kc1 10.Kd3+ Kb1 11.Bd5 b3 12.Bxb3 b4 13.Bc4 b3 14.Kc3 1287
Matt in 19 gefunden ! (1 Lösung in 00:00)
19/19 0:00 +M19 1.Be3+ Kb1 2.Bh6 b5 3.Ke7 b4 4.Kf6 b5 5.Kg5 Kc1 6.Kf5+ Kb1 7.Kf4 Kc1 8.Ke4+ Kb1 9.Ke3 Kc1 10.Kd3+ Kb1 11.Bd5 b3 12.Bxb3 b4 13.Bc4 b3 14.Kc3 1287
best move: Bg1-e3 time: 0:02.937 min n/s: 1.287.156 nodes: 1.166.164
I ran this for myself----amazing result in 0 time
I will spend more time learning Chest settings.
[d] 3K4/1p5p/1p6/8/8/1B6/1p6/b1k3B1 w - - (3+6)
Stellungs-Analyse: C0/R0/K3/P4/X9 W:3/20
Parameter in Datenbank gefunden: #19; 00:10 @ C2/R0/K3/P2/X2;
AutoTurbo-Suche nach Spezial-Matt [C1/R0/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Suche nach Spezial-Matt [C0/R1/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Suche nach Spezial-Matt [C0/R2/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Suche nach Spezial-Matt [C0/R-2/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Suche nach Spezial-Matt [C0/R3/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Suche nach Spezial-Matt [C0/R-3/K0/P0/X0] in 19 ... (Hash=512MB)
AutoTurbo-Suche nach Spezial-Matt [C0/R0/K0/P0/X1] in 19 ... (Hash=512MB)
AutoTurbo-Suche nach Spezial-Matt [C0/R0/K0/P0/X2] in 19 ... (Hash=512MB)
AutoTurbo-Suche nach Spezial-Matt [C0/R0/K3/P0/X2] in 19 ... (Hash=512MB)
19/19 0:00 +M19 1.Be3+ Kb1 2.Bh6 b5 3.Ke7 b4 4.Kf6 b5 5.Kg5 Kc1 6.Kf5+ Kb1 7.Kf4 Kc1 8.Ke4+ Kb1 9.Ke3 Kc1 10.Kd3+ Kb1 11.Bd5 b3 12.Bxb3 b4 13.Bc4 b3 14.Kc3 1287
19.01 0:00 +M19 1.Be3+ 1287
19/19 0:00 +M19 1.Be3+ Kb1 2.Bh6 b5 3.Ke7 b4 4.Kf6 b5 5.Kg5 Kc1 6.Kf5+ Kb1 7.Kf4 Kc1 8.Ke4+ Kb1 9.Ke3 Kc1 10.Kd3+ Kb1 11.Bd5 b3 12.Bxb3 b4 13.Bc4 b3 14.Kc3 1287
AutoTurbo-Suche nach Spezial-Matt [C0/R0/K3/P2/X2] in 19 ... (Hash=512MB)
19.01 0:00 +M19 1.Be3+ 1287
19/19 0:00 +M19 1.Be3+ Kb1 2.Bh6 b5 3.Ke7 b4 4.Kf6 b5 5.Kg5 Kc1 6.Kf5+ Kb1 7.Kf4 Kc1 8.Ke4+ Kb1 9.Ke3 Kc1 10.Kd3+ Kb1 11.Bd5 b3 12.Bxb3 b4 13.Bc4 b3 14.Kc3 1287
Matt in 19 gefunden ! (1 Lösung in 00:00)
19/19 0:00 +M19 1.Be3+ Kb1 2.Bh6 b5 3.Ke7 b4 4.Kf6 b5 5.Kg5 Kc1 6.Kf5+ Kb1 7.Kf4 Kc1 8.Ke4+ Kb1 9.Ke3 Kc1 10.Kd3+ Kb1 11.Bd5 b3 12.Bxb3 b4 13.Bc4 b3 14.Kc3 1287
best move: Bg1-e3 time: 0:02.937 min n/s: 1.287.156 nodes: 1.166.164