See last position. Fairy max exceeds time limit.
[pgn]
[Event "Computer Chess Game"]
[Site "HP"]
[Date "2016.06.01"]
[Round "-"]
[White "Fairy-Max 4.8S"]
[Black "SkipperWinb"]
[Result "1/2-1/2"]
[TimeControl "120"]
[Annotator "1. +0.11 1... +0.07"]
1. c4 {+0.11/8} d5 {+0.07/12 2.0} 2. cxd5 {+0.17/8 1.7} Qxd5 {+0.06/13 2.0}
3. Nc3 {+0.22/8 8} Qa5 {+0.10/12 2.0} 4. d4 {+0.00/8 4} e5 {-0.01/11 1.9}
5. dxe5 {+0.09/9 2.9} Qxe5 {-0.01/10 1.9} 6. Nf3 {+0.11/8 2.7} Qd6
{+0.00/9 1.9} 7. Qxd6 {+0.02/8 1.5} Bxd6 {-0.16/11 1.8} 8. Nb5
{+0.15/8 1.7} Nc6 {-0.38/11 1.8} 9. Nxd6+ {+0.57/9 2.1} cxd6 {-0.35/13 1.8}
10. Bf4 {+0.55/9 1.6} d5 {-0.17/12 1.8} 11. O-O-O {+0.33/9 2.2} Nge7
{-0.23/11 1.7} 12. e3 {+0.16/8 1.4} O-O {-0.26/10 1.7} 13. h3 {+0.32/8 2.2}
Bf5 {-0.25/10 1.7} 14. Bd3 {+0.24/9 3} Bxd3 {-0.23/11 1.6} 15. Rxd3
{+0.16/10 4} h6 {-0.28/10 1.7} 16. Ne5 {+0.29/9 8} g5 {-0.21/12 1.6} 17.
Nxc6 {+0.25/10 1.4} Rfc8 {-0.31/12 1.6} 18. Rc3 {+0.31/10 1.0} bxc6
{-0.31/12 1.5} 19. Be5 {+0.38/11 2.0} a5 {-0.34/11 1.5} 20. g4
{+0.40/10 1.2} Ng6 {-0.28/12 1.5} 21. Bd4 {+0.37/11 1.0} Rab8
{-0.50/11 1.5} 22. Rd1 {+0.39/10 1.6} Nh4 {-0.52/11 1.5} 23. f4
{+0.49/10 1.1} gxf4 {-0.45/11 1.4} 24. Be5 {+0.47/11 1.3} Ra8
{-0.26/12 1.4} 25. Bxf4 {+0.49/12 1.8} Kg7 {-0.28/13 1.5} 26. Be5+
{+0.36/11 1.5} Kf8 {-0.35/12 1.3} 27. Bd6+ {+0.50/9 0.8} Kg7 {-0.41/11 1.3}
28. a4 {+0.37/10 0.9} Ng6 {-0.27/12 1.3} 29. Re1 {+0.36/11 2.0} Ra6
{-0.31/11 1.3} 30. e4 {+0.37/11 0.8} Re8 {-0.23/11 1.3} 31. e5
{+0.39/11 0.9} Nf8 {+0.22/12 1.3} 32. b3 {+0.27/10 1.3} d4 {+0.31/12 1.3}
33. Rd3 {+0.26/11 1.0} c5 {+0.26/13 1.2} 34. Rf1 {+0.26/10 1.1} Kg8
{+0.23/10 1.2} 35. Rdf3 {+0.31/9 1.4} Ra7 {+0.23/11 1.2} 36. Rg3
{+0.30/9 1.2} Rb7 {+0.31/11 1.2} 37. Rf2 {+0.30/8 0.8} Nd7 {+0.31/11 1.2}
38. Rc2 {+0.56/9 0.6} Rc8 {+0.27/12 1.2} 39. g5 {+0.59/11 2.2} h5
{+0.32/11 1.1} 40. g6 {+0.63/10 1.6} Kg7 {+0.38/11 1.1} 41. gxf7+
{+1.39/9 0.9} Kxf7 {+0.38/9 1.2} 42. Rf2+ {+1.45/11 1.1} Ke6 {+0.17/12 1.0}
43. Rg6+ {+1.23/11 0.6} Kd5 {+0.34/12 1.0} 44. e6 {+1.12/11 0.8} Ne5
{+0.24/11 1.0} 45. Bxe5 {+1.02/11 1.4} Kxe5 {+0.29/11 1.1} 46. Re2+
{+0.99/10 1.5} Kf4 {+0.55/12 0.9} 47. e7 {+0.93/10 1.0} Re8 {+0.56/12 0.9}
48. Rge6 {+0.93/10 0.8} h4 {+0.88/11 0.9} 49. Re1 {+0.99/10 1.3} Rxb3
{+1.59/11 0.9} 50. Rf6+ {+2.66/11 0.6} Kg3 {+1.78/12 0.9} 51. Rf8
{+2.43/11 0.6} Reb8 {-0.69/12 0.9} 52. Rxb8 {+2.44/11 0.6} Rxb8
{-1.78/14 0.9} 53. e8=Q {+2.40/13 0.7} Rxe8 {-2.37/16 0.8} 54. Rxe8
{+2.45/14 0.6} Kxh3 {-2.14/17 0.8} 55. Rc8 {+2.42/13 0.5} Kg4
{-2.14/15 0.8} 56. Rxc5 {+2.51/13 0.4} h3 {-2.29/15 0.8} 57. Rd5
{+2.48/15 0.6} h2 {+0.00/18 0.8} 58. Rxd4+ {+2.49/16 0.4} Kg3
{+0.00/17 0.8} 59. Rd1 {+2.50/19 0.5} Kg2 {-0.86/18 0.8} 60. Rd2+
{+2.46/19 0.4} Kh3 {-0.86/19 0.8} 61. Rd3+ {+0.70/18 0.5} Kg2
{-0.01/15 0.7} 62. Rd1 {+0.69/18 0.5} h1=Q {-0.91/21 0.7} 63. Rxh1
{+1.77/26 0.4} Kxh1 {-1.46/22 0.7} 64. Kc2 {+1.69/28 0.3} Kg2
{-1.52/18 0.7} 65. Kd3 {+1.66/28 0.3} Kf3 {-1.52/16 0.7} 66. Kc4
{+1.63/28 0.1} Ke4 {-2.38/21 0.7} 67. Kb5 {+1.63/28 0.1} Kd5 {-2.46/24 0.7}
68. Kxa5 {+1.68/28 0.2} Kc5 {-2.74/23 0.7} 69. Ka6 {+1.72/28 0.2} Kc6
{-2.74/23 0.6} 70. a5 {+1.74/28 0.3} Kc7 {-2.74/23 0.6} 71. Kb5
{+1.64/28 0.4} Kb7 {-2.74/28 0.6} 72. a6+ {+1.51/27 0.3} Kc7 {-2.74/28 0.6}
73. Kc5 {+1.52/28 0.1} Kc8 {-2.74/26 0.6} 74. Kc6 {+1.47/28 0.2} Kb8
{-2.74/29 0.6} 75. Kb6 {+1.44/28 0.2} Ka8 {-2.74/30 0.6} 76. Kc5
{+1.40/28 0.2} Ka7 {-2.74/23 0.6} 77. Kb5 {+1.40/28 0.1} Ka8 {-2.74/25 0.5}
78. Kb6 {+1.41/28 0.2} Kb8 {+0.00/30 0.5}
{Black wins on time but bare king} 1/2-1/2
[/pgn]
Fairy max joke
Moderators: hgm, Dann Corbit, Harvey Williamson
-
Henk
- Posts: 7210
- Joined: Mon May 27, 2013 10:31 am
Re: Fairy max joke
Fairy max at last position had at least five seconds left on the clock. Maybe twelve I can't remember.
-
Gurcan Uckardes
- Posts: 196
- Joined: Wed Oct 29, 2014 12:42 am
Re: Fairy max joke
It claimed the draw and the command sent by Fairy was not acknowledged. Adjudicate as draw and check the gui & the protocol.
My blog for Android users: http://chesstroid.blogspot.com
-
hgm
- Posts: 27701
- Joined: Fri Mar 10, 2006 10:06 am
- Location: Amsterdam
- Full name: H G Muller
Re: Fairy max joke
There is no reason why it should claim a draw here: this is not even a repeat.
Yet this is fishy. When I set Fairy-Max thinking from scratch in the final position it reaches 28 ply (its maximum depth) in 0.12 sec, and moves a6a7 with a +0.01 score.
Yet this is fishy. When I set Fairy-Max thinking from scratch in the final position it reaches 28 ply (its maximum depth) in 0.12 sec, and moves a6a7 with a +0.01 score.
-
Gurcan Uckardes
- Posts: 196
- Joined: Wed Oct 29, 2014 12:42 am
Re: Fairy max joke
HG, doesn't Fairy use draw offer? Is it supposed to play until mate?
I'm curious about these weird terminations. In Android i have many similar terminations which are reported as loss and to maintain Rapidroid ranking i'm wasting a lot of time to adjudicate manually. There should be an explanation.
It's not only Fairy but also many other engines, mostly xb.
I'm curious about these weird terminations. In Android i have many similar terminations which are reported as loss and to maintain Rapidroid ranking i'm wasting a lot of time to adjudicate manually. There should be an explanation.
It's not only Fairy but also many other engines, mostly xb.
My blog for Android users: http://chesstroid.blogspot.com
-
hgm
- Posts: 27701
- Joined: Fri Mar 10, 2006 10:06 am
- Location: Amsterdam
- Full name: H G Muller
Re: Fairy max joke
Fairy-Max doesn't offer or accept draws. It does claim 3-fold rep and 50-move draws, but this is really an add-on outside the AI, in the protocol interface. It just stores all positions of the game in an array, and after every move scans through them to see if it occurred twice before. If it is it claims a draw through a RESULT command. (This was a requirement to participate in WBEC, in the days that WinBoard did not adjudicate 50-move and rep-draws by itself.)
In other cases it would play until mate. It would also never resign early.
This code is not bug-prone, and not changed for ages. I have never heard of Fairy-Max making a false claim. (And most interfaces would not ignore a RESULT claim either.)
I don't know what could be the problem with the Android interface. It could be ignoring draw claims, but that is only a likely explanation if the positions where the game hangs are indeed claimable draws.
In other cases it would play until mate. It would also never resign early.
This code is not bug-prone, and not changed for ages. I have never heard of Fairy-Max making a false claim. (And most interfaces would not ignore a RESULT claim either.)
I don't know what could be the problem with the Android interface. It could be ignoring draw claims, but that is only a likely explanation if the positions where the game hangs are indeed claimable draws.
-
Daniel Anulliero
- Posts: 759
- Joined: Fri Jan 04, 2013 4:55 pm
- Location: Nice
Re: Fairy max joke
That's indeed more à New Skipper's joke ...
Or need to fix a same bug over and over again ?
More seriously, Henk , how can you juge the engine of others, when yours play always buggy/badly?
Boring posts ...
Or need to fix a same bug over and over again ?
More seriously, Henk , how can you juge the engine of others, when yours play always buggy/badly?
Boring posts ...
-
Henk
- Posts: 7210
- Joined: Mon May 27, 2013 10:31 am
Re: Fairy max joke
That would be bad news for testers who have not written an engine like say Komodo. For they are not qualified according to you or they are not allowed to say anything.
First read the name of the author of a post and skip if appropriate.
First read the name of the author of a post and skip if appropriate.
-
Robert Pope
- Posts: 558
- Joined: Sat Mar 25, 2006 8:27 pm
Re: Fairy max joke
But is this thread for a real game, or a "joke"?
-
Daniel Anulliero
- Posts: 759
- Joined: Fri Jan 04, 2013 4:55 pm
- Location: Nice
Re: Fairy max joke
That's what I do , the most of the timeHenk wrote: First read the name of the author of a post and skip if appropriate.
But if I feel some disrespectful things , I answer , even in one of your boring post