where can I find robbolito-rybka at long time control

Discussion of computer chess matches and engine tournaments.

Moderator: Ras

Uri Blass
Posts: 10889
Joined: Thu Mar 09, 2006 12:37 am
Location: Tel-Aviv Israel

Re: where can I find robbolito-rybka at long time control

Post by Uri Blass »

S.Taylor wrote:
Uri Blass wrote:I am only interested in results and not in the games
I hope that rybka can win.
I do not like engine with unknown authors to beat rybka at long time control and I hope that stockfish can beat rybka so we can forget about robbo or iggorit.

Uri

We need to be objective.

Why shouldn't a no-name thing be better?
What I prefer to see has nothing to do with not being objective.

The reason that I do not like no name thing(even in case that it is legal) to be better is that I think that it is simply against humans.

Humans should be respected for their achievements and if no name thing is better than everything else then it is going to reduce the respect that people are going to give to developers of other programs.

It may cause people to lose interest in chess programming because of the feeling that they are weaker than nothing regardless of what they do.

Uri
User avatar
M ANSARI
Posts: 3726
Joined: Thu Mar 16, 2006 7:10 pm

Re: where can I find robbolito-rybka at long time control

Post by M ANSARI »

kingliveson wrote:
M ANSARI wrote:And what agenda would that be? If it is to note that all the Ippolit based engines are derived from Rybka 3 and not an original work, then you are of course correct. I would hardly say that finding the truth is "an agenda".

With regards to hardware, I was using Skulltrail at 4 Ghz which has 8 cores and RL g3. The point of using Ponder ON was to increase time and thus remove time as a factor in the engine's play. For me I am more interested in evaluation advantages. I don't think that engines would be fighting for resources as they would have each been using 1 core only and there would be 6 cores spare. Again there could be a bug with RL g3 ponder ON that makes it play weaker, but looking at the games I couldn't see any such behavior. There was around 1% or 2% of RL games that were lost due to time, but most of those were in lost positions. I disregard such games and play additional games to cover for them as there is a possibility that instability in the engine before the time loss.

By the way Franklin you seem to come off as one real ass hole. I would be very happy to discuss with you my findings in an adult productive way. You seem to be unable to do that ... maybe you have an "agenda". I have done my tests and I am convinced. I might be wrong in my conclusion and my data might not be enough to convince you, and there is nothing I can do about that. But it would be nice if you would also do some testing and give some meaningful data output instead of simply dismissing everything as one side or the other.
This is funny, what else can I say?! I love this place. Ok, on a serious note, you never present anything to back up your claims.

1) You say one engine is a derivative work, but you don't have any supporting evidence. Take a look at what people think about your god Rybka.
2) When ever I make a statement, I provide concrete data to support what I have said. Go through these forum--I post results as well as the actual games that people can download and anylyze. CONCRETE DATA.
3) You refuse to provide any data to support your claims, whether it be the derivative issue or the strength of a particular engine. You made the claim (here) that given a position, you have yet to see where these 2 engines do not agree. So I gave you a postion ( 8/3N4/8/8/1pp5/brpp3p/qpprp2P/1nkbK3 w - - 0 1 ) to analyze with both engines and report back, and we continue to wait... Please do this and tell us your findings.

Accusations without evidence or unwillingness to provide one is called gossip, propaganda, fabrication, falsehood, fiction, hearsay, hoax, innuendo, lie, tale, belittlement, character assassination, cheap shot, denigration, mud, slime, slur, smear, vilification, etc. This is why I say you have an agenda. And why are you so angry?

You send me a position that Rybka 3 might have a bug or maybe RL has has a bug and you give that as DATA ??? But since you insist I get R3 sees mate in 4 and so does ZM II but RL thinks it is mate in 12 and takes a longer time. Actually I have seen Rybka also stick to the first mate it sees and not the shortest mate .... so ???? I am sorry but that is beyond pathetic. I can show you some even simpler bugs that R3 suffers from that were fixed and for sure there will be bugs in RL that need to be fixed. After all I don't think anyone said that R3 and RL are identical programs. Do you even know how to move chess pieces? Do you ever look at a chess game and analyse it and look for where one engine went wrong. I think I am one of the very few who will actually go into the games played in their tourneys and try to get information from them. It might be weird but I actually enjoy that. I have looked at and analysed several thousand R3 games and I feel I know where it is weak. R3 can devastate any engine on earth but yet can look feeble in some positions. I am not talking about some simple bug ... I am talking about poor evaluation. There are 3 main things that I can point out that are very obviously poor evaluation scenarios in R3 ... and R3 can get CRUSHED due to these poor evaluation scenarios even if it is on 8 cores and the other engine is on 1 core. THE SAME EXACT 3 weaknesses are there in RL or any of IPP derivatives. I will not post what these weaknesses are because I think that is not fair to Vas ... the original author. But it is no secret that I made a huge post about R3 bishop pair weakness, I see you have only 200 posts so you probably were not here when I posted it some time back. RL has the same incorrect evaluation of bishop pair and will get CRUSHED convincingly by an engine more than 250 ELO weaker than it the same way R3 gets crushed. This will most likely be "fixed" very quickly with new versions of the clone as evaluation parameters are tuned, but the cloners will find that actually tuning evaluation is not so simple. Fixing bugs is simple, but tuning evaluation is tremendously difficult.

First I recommend you look at the post I made about a year ago

http://talkchess.com/forum/viewtopic.ph ... ishop+pair

And then I would recommend you look at the following game played by RL on 1 core against N4 on 1 core and tell me what you think. I am hoping that you understand a little about chess otherwise you will not have a clue what I am talking about. Please run your engine and check the evaluation scores just in case you think I am making this up because of the "agenda" issue.

[Event "RLg3_Naum4_1_core_5_2"]
[Site "Microsoft"]
[Date "2010.01.10"]
[Round "4.1"]
[White "Naum 4_1 thread"]
[Black "RobboLito 0.085g3 x64"]
[Result "1-0"]
[ECO "A87"]
[Annotator "0.44;0.24"]
[PlyCount "159"]
[EventDate "2010.01.10"]
[EventType "tourn"]
[TimeControl "300+2"]

{Intel(R) Core(TM)2 Extreme CPU X9775 @ 3.20GHz W=14.7 plies; 1,294kN/s;
Perfect v12.ctg B=17.9 plies; 2,217kN/s; Perfect v12.ctg} 1. d4 {B 0} f5 {B 0}
2. g3 {B 0} Nf6 {B 0} 3. Bg2 {B 0} g6 {B 0} 4. Nf3 {B 0} Bg7 {B 0} 5. O-O {B 0}
O-O {B 0} 6. c4 {B 0} d6 {B 0} 7. Nc3 {B 0} Qe8 {B 0} 8. d5 {B 0} a5 {B 0} 9.
Ne1 {B 0} e6 {0.24/16 14} 10. Nd3 {0.44/15 10 (Be3)} e5 {0.17/18 9 (Na6)} 11.
f3 {0.30/15 14} Na6 {0.14/17 3} 12. e4 {0.28/16 13} fxe4 {0.20/18 20} 13. Nxe4
{0.25/16 10 (fxe4)} b5 {0.11/17 25 (Bd7)} 14. Qb3 {0.16/15 11 (b3)} Bd7 {-0.16/
18 22 (Nb4)} 15. cxb5 {0.00/15 12} a4 {-0.16/18 6} 16. Nxf6+ {0.00/16 10} Rxf6
{-0.17/18 12} 17. Qc2 {0.00/16 33} Bxb5 {-0.17/16 0} 18. Re1 {-0.05/16 7 (Be3)}
Rf8 {-0.26/17 6} 19. Be3 {-0.16/17 29} Qf7 {-0.14/18 9 (Rb8)} 20. Rad1 {-0.02/
16 9} Rab8 {-0.23/17 9} 21. b3 {-0.09/15 5 (a3)} axb3 {-0.46/20 9} 22. axb3 {
-0.20/16 8} Qf5 {-0.44/19 3} 23. Qb1 {-0.19/16 10 (Bf2)} Rf7 {-0.45/17 17} 24.
Rd2 {-0.23/17 17} Bc4 {-0.43/17 3 (c5)} 25. bxc4 {0.06/15 4} Rxb1 {-0.43/15 0}
26. Rxb1 {0.06/6 0} Rf8 {-0.41/20 22} 27. Ra1 {0.05/17 7} Nb8 {-0.43/20 33
(Qc8)} 28. Ra7 {0.04/16 9} Bf6 {-0.35/20 8 (c6)} 29. g4 {0.10/15 4} Bg5 {-0.35/
19 13} 30. f4 {0.11/15 2 (gxf5)} Bxf4 {-0.49/18 4} 31. Bxf4 {0.14/16 4} Qxg4 {
-0.49/17 0} 32. h3 {0.13/16 3 (Be3)} Qh4 {-0.65/18 2} 33. Be3 {0.13/17 5} Qxc4
{-0.65/17 0} 34. Ra1 {0.13/17 7 (Raa2)} Na6 {-0.73/19 7} 35. Re1 {0.14/17 13
(Rc1)} Kg7 {-0.73/18 10 (Qa4)} 36. Rc1 {0.19/16 3} Qb3 {-0.73/18 4} 37. Be4 {
0.16/16 3 (Rc6)} Qa4 {-0.63/17 8} 38. Re2 {0.15/17 7} Rc8 {-0.59/17 11 (Rb8)}
39. Kh2 {0.29/14 7} Rb8 {-0.46/17 11} 40. Bg5 {0.29/15 3 (Bd2)} Rb3 {-0.53/17
7 (Rf8)} 41. Rf1 {0.36/15 3 (Rc6)} Nb4 {-0.31/17 7 (Rb8)} 42. Nxb4 {0.44/15 3}
Rxb4 {0.00/19 6} 43. Bg2 {0.46/16 7 (Ref2)} h6 {-0.63/18 3} 44. Bd2 {0.40/17 9
(Bd8)} Rb3 {0.07/19 22} 45. Ref2 {0.40/16 2 (Rc1)} Qd7 {0.00/17 3} 46. Rc1 {0.
39/16 4 (Rf6)} Ra3 {-0.36/18 4 (g5)} 47. Bb4 {0.44/16 2 (Rc6)} Ra7 {-0.28/18 4
(Ra4)} 48. Rc6 {0.42/15 4 (Rfc2)} Kh8 {-0.35/17 5 (Qd8)} 49. Be4 {0.58/16 5
(Be1)} Qg7 {-0.22/17 4 (Kg7)} 50. Rc4 {0.84/15 8} Ra4 {0.00/18 5 (Ra1)} 51. Bc2
{0.84/15 2} Ra1 {0.00/18 5 (Ra8)} 52. h4 {0.96/15 3 (Rg2)} h5 {0.00/19 3 (Ra2)}
53. Bd2 {1.08/14 5} Ra3 {0.46/20 13} 54. Bc1 {1.16/15 2} Ra8 {0.40/19 4} 55.
Be4 {1.31/15 8} Rf8 {0.46/20 3 (Qg8)} 56. Rfc2 {1.11/15 4 (Rg2)} Rf7 {0.34/19 2
} 57. Bg5 {1.27/14 3 (Rg2)} Kg8 {0.37/19 2 (Qf8)} 58. Rg2 {1.38/17 5 (Kg3)} Kh8
{0.45/19 2} 59. Rb4 {1.39/16 3 (Rcc2)} Rf8 {0.65/18 5 (Qg8)} 60. Be3 {1.44/16
3 (Rb3)} Rf6 {0.89/17 3} 61. Rb8+ {1.45/17 3} Rf8 {0.89/16 0} 62. Rbb2 {1.45/
17 1} Rf6 {1.25/18 6} 63. Rg5 {1.85/16 3} Kg8 {1.05/19 3} 64. Rbg2 {2.13/16 3
(Rb8+)} Kf7 {1.21/20 2} 65. R5g3 {2.33/15 2 (Bd2)} Qg8 {2.00/16 2} 66. Bg5 {2.
96/14 2} Rf1 {3.71/17 3} 67. Bh6 {3.25/14 1} Rf6 {1.98/15 0} 68. Rc3 {3.48/16 2
} Qb8 {6.39/16 4} 69. Rgc2 {4.02/15 2 (Bxg6+)} c5 {4.39/17 3 (Kg8)} 70. dxc6 {
5.20/14 3} Qc7 {4.39/15 0} 71. Bd5+ {6.48/13 2 (Bg5)} Ke8 {6.44/17 2} 72. Ra2 {
6.94/14 4 (Bg5)} Qc8 {10.42/16 3} 73. Bg5 {8.42/14 3} Rf1 {7.29/17 3 (Rf5)} 74.
Rca3 {#15/12 5 (c7)} Rb1 {#10/18 2 (Kf8)} 75. Rf2 {#9/13 0} Rb2 {#9/19 2 (Rb4)}
76. Rxb2 {#6/3 0 (Bf7+)} Kf8 {#4/22 2 (e4)} 77. Ra7 {#4/3 0 (Rb7)} e4 {#3/20 2}
78. Bh6+ {#3/3 0} Ke8 {#2/21 1} 79. Bf7+ {#2/3 0} Kd8 {#1/21 1} 80. Bg5# {#1/3
0} 1-0
User avatar
M ANSARI
Posts: 3726
Joined: Thu Mar 16, 2006 7:10 pm

Re: where can I find robbolito-rybka at long time control

Post by M ANSARI »

Actually I just realized why you wanted me to look at the position you mentioned after seeing you post the same position on another thread .... you actually think the RL does not see a mate ???? And you claim that I don't look at DATA ??? I suggest you spend a little more time looking at what you post otherwise you end up making an ass out of yourself. By the way here is the position that you thought RL was evaluating as a draw. Next time before you post something try spending a little time studying what you are going to post.

New game
[d]8/3N4/8/8/1pp5/brpp3p/qpprp2P/1nkbK3 w - - 0 1

Analysis by RobboLito 0.085g3 x64:

1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nf3 Qa2
-+ (-40.20) Depth: 6/15 00:00:00 0kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nf3 Qa2
-+ (-40.12 !) Depth: 7/15 00:00:00 0kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nf3 Qa2
-+ (-40.04 !) Depth: 7/15 00:00:00 0kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nf3 Qa2
-+ (-39.92 !) Depth: 7/15 00:00:00 0kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nf3 Qa2
-+ (-39.74 !) Depth: 7/15 00:00:00 0kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nf3 Qa2
-+ (-39.47 !) Depth: 7/15 00:00:00 0kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nf3 Qa2
-+ (-39.07 !) Depth: 7/15 00:00:00 0kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nf3 Qa2
-+ (-38.47 !) Depth: 7/15 00:00:00 0kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nf3 Qa2
-+ (-37.57 !) Depth: 7/15 00:00:00 0kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nf3 Qa2
-+ (-36.22 !) Depth: 7/15 00:00:00 0kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nf3 Qa2
-+ (-34.20 !) Depth: 7/15 00:00:00 0kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nf3 Qa2
-+ (-31.17 !) Depth: 7/15 00:00:00 0kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nf3 Qa2
-+ (-26.63 !) Depth: 7/15 00:00:00 0kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nf3 Qa2
-+ (-19.82 !) Depth: 7/15 00:00:00 0kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nf3 Qa2
-+ (-9.61 !) Depth: 7/15 00:00:00 0kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 7/15 00:00:00 0kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 8/15 00:00:00 0kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 9/15 00:00:00 1kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 10/15 00:00:00 1kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 11/15 00:00:00 1kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 12/15 00:00:00 1kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 13/15 00:00:00 1kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 14/15 00:00:00 2kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 15/15 00:00:00 2kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 16/15 00:00:00 3kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 17/15 00:00:00 3kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 18/15 00:00:00 4kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 19/15 00:00:00 5kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 20/15 00:00:00 6kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 21/15 00:00:00 8kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 22/15 00:00:00 9kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 23/15 00:00:00 11kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 24/15 00:00:00 13kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 25/15 00:00:00 15kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 26/15 00:00:00 18kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 27/15 00:00:00 22kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 28/15 00:00:00 26kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 29/15 00:00:00 31kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 30/15 00:00:00 35kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 31/16 00:00:00 40kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 32/17 00:00:00 45kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 33/18 00:00:00 52kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 34/18 00:00:00 61kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 35/18 00:00:00 71kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 36/18 00:00:00 83kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 37/19 00:00:00 94kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 38/19 00:00:00 108kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 39/21 00:00:00 124kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 40/22 00:00:00 146kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 41/22 00:00:00 175kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 42/23 00:00:00 207kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 43/25 00:00:00 242kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 44/25 00:00:00 279kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 45/25 00:00:00 321kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 46/25 00:00:00 375kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 47/26 00:00:00 448kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 48/27 00:00:00 539kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 49/27 00:00:00 641kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 50/27 00:00:00 754kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 51/27 00:00:00 877kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 52/29 00:00:00 1026kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 53/29 00:00:00 1213kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 54/30 00:00:00 1449kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 55/31 00:00:00 1732kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 56/31 00:00:00 2044kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 57/32 00:00:00 2373kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 58/34 00:00:00 2757kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 59/35 00:00:00 3230kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 60/38 00:00:00 3861kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 61/38 00:00:01 4593kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 62/39 00:00:01 5468kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 63/41 00:00:01 6440kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 64/42 00:00:01 7678kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 65/42 00:00:02 9047kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 66/44 00:00:02 10554kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 67/45 00:00:02 12720kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 68/48 00:00:03 15487kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 69/50 00:00:04 18892kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 70/50 00:00:05 23092kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 71/51 00:00:06 27862kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 72/52 00:00:07 33568kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 73/55 00:00:09 41621kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 74/55 00:00:11 50708kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 75/56 00:00:15 64155kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 76/57 00:00:18 79433kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 77/63 00:00:23 97595kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 78/63 00:00:30 129mN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.00) Depth: 79/64 00:00:38 158mN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.08 !) Depth: 80/64 00:00:45 189mN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
= (0.16 !) Depth: 80/64 00:00:49 212mN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
+/= (0.28 !) Depth: 80/64 00:00:53 235mN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
+/= (0.46 !) Depth: 80/64 00:00:57 257mN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
+/- (0.73 !) Depth: 80/64 00:01:02 281mN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
+/- (1.13 !) Depth: 80/64 00:01:06 303mN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
+- (1.73 !) Depth: 80/64 00:01:10 327mN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
+- (2.63 !) Depth: 80/64 00:01:15 349mN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
+- (3.98 !) Depth: 80/64 00:01:19 371mN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
+- (6.00 !) Depth: 80/64 00:01:23 394mN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
+- (9.03 !) Depth: 80/64 00:01:27 416mN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
+- (13.57 !) Depth: 80/64 00:01:31 439mN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
+- (20.38 !) Depth: 80/64 00:01:35 462mN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
+- (30.59 !) Depth: 80/64 00:01:40 484mN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
+- (45.90 !) Depth: 80/64 00:01:44 507mN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
+- (68.86 !) Depth: 80/64 00:01:48 529mN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
+- (103.30 !) Depth: 80/64 00:01:52 552mN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
+- (154.96 !) Depth: 80/64 00:01:56 574mN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
+- (232.45 !) Depth: 80/64 00:02:01 597mN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nf3 Qa2 5.Ng5 Qa1 6.Nxh3 Qa2 7.Ng5 Qa1 8.h4 Qa2 9.Ne6 Qa1 10.Nc5 Qa2 11.h5 Qa1 12.Nxb3#
+- (#12) Depth: 80/64 00:07:14 674mN

(, Microsoft 13.01.2010)
kingliveson

Re: where can I find robbolito-rybka at long time control

Post by kingliveson »

M ANSARI wrote:Actually I just realized why you wanted me to look at the position you mentioned after seeing you post the same position on another thread .... you actually think the RL does not see a mate ???? And you claim that I don't look at DATA ??? I suggest you spend a little more time looking at what you post otherwise you end up making an ass out of yourself. By the way here is the position that you thought RL was evaluating as a draw. Next time before you post something try spending a little time studying what you are going to post.

New game
[d]8/3N4/8/8/1pp5/brpp3p/qpprp2P/1nkbK3 w - - 0 1

Analysis by RobboLito 0.085g3 x64:

1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nf3 Qa2
-+ (-40.20) Depth: 6/15 00:00:00 0kN
.
.
.
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nc4
+- (232.45 !) Depth: 80/64 00:02:01 597mN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne5 Qa1 4.Nf3 Qa2 5.Ng5 Qa1 6.Nxh3 Qa2 7.Ng5 Qa1 8.h4 Qa2 9.Ne6 Qa1 10.Nc5 Qa2 11.h5 Qa1 12.Nxb3#
+- (#12) Depth: 80/64 00:07:14 674mN

(, Microsoft 13.01.2010)
As for is this position, I never claim Robbolito sees it as draw. You made the clam that you have yet to see a position where Rybka and Robbolito don't agree. So I gave it to you for analysis. It took it 7 minutes for RobboLito to find mate in 12. Rybka and a few others solves the mate in 4 in less than 5 seconds. And Yes I have analyzed the position before I gave it to you as I posted in another topic.

Here are the engines that sees mate in 4 right away:

Deep Shredder 12: Yes
Fruit 2.3.1: Yes
Glaurung 2.2: Yes
Rybka 3: Yes
Stockfish 1.62: Yes
Toga II 1.4.1: Yes
Zappa Mexico II: Yes

These cannot find it:
Crafty 23.1: No
Igorrit: No
RobboLito: No
Naum 4: No

And here is Naum 4 after 6 minutes:

Code: Select all

8/3N4/8/8/1pp5/brpp3p/qpprp2P/1nkbK3 w - - 0 1

Analysis by Naum 4:

1.Ne5 Qa1 2.Nxc4 Qa2 3.Kf2 e1Q+ 
  -+  (-36.92)   Depth: 6/12   00:00:00  0kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (0.00)   Depth: 7/19   00:00:00  1kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 8/8   00:00:00  1kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 9/9   00:00:00  1kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 10/10   00:00:00  1kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 11/11   00:00:00  1kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 12/12   00:00:00  1kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 13/13   00:00:00  1kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 14/14   00:00:00  2kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 15/15   00:00:00  2kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 16/16   00:00:00  3kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 17/17   00:00:00  4kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 18/18   00:00:00  5kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 19/19   00:00:00  6kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 20/20   00:00:00  8kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 21/21   00:00:00  12kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 22/22   00:00:00  17kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 23/23   00:00:00  25kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 24/24   00:00:00  35kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 25/25   00:00:00  49kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 26/26   00:00:00  69kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 27/27   00:00:00  97kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 28/28   00:00:00  134kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 29/29   00:00:00  185kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 30/30   00:00:00  252kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 31/31   00:00:00  341kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 32/32   00:00:00  451kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 33/33   00:00:00  601kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 34/34   00:00:00  807kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 35/35   00:00:00  1086kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 36/36   00:00:00  1441kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 37/37   00:00:00  1906kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 38/38   00:00:00  2555kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 39/39   00:00:01  3357kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 40/40   00:00:01  4474kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 41/41   00:00:01  5753kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 42/42   00:00:02  7655kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 43/43   00:00:03  10206kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 44/44   00:00:03  13426kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 45/45   00:00:05  17667kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 46/46   00:00:07  23830kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 47/47   00:00:09  31300kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 48/48   00:00:12  42018kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 49/49   00:00:16  55829kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 50/50   00:00:21  73126kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 51/51   00:00:28  97753kN
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 52/52   00:00:38  131mN, tb=4
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 53/53   00:00:52  175mN, tb=7
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 54/54   00:01:08  231mN, tb=19
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 55/55   00:01:31  310mN, tb=43
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 56/56   00:02:01  410mN, tb=116
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 57/57   00:02:37  533mN, tb=210
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 58/58   00:03:36  729mN, tb=438
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 59/59   00:04:51  980mN, tb=1241
1.Ne5 Qa1 2.Nxc4 Qa2 3.Ne3 Qa1 4.Nc4 
  =  (-0.04)   Depth: 60/60   00:06:36  1333mN, tb=1790

(, Microsoft 13.01.2010)
So once again, you are proven wrong. But why are you so emotional?
Dann Corbit
Posts: 12792
Joined: Wed Mar 08, 2006 8:57 pm
Location: Redmond, WA USA

Re: where can I find robbolito-rybka at long time control

Post by Dann Corbit »

Quite an interesting position (Chest analysis):
8/3N4/8/8/1pp5/brpp3p/qpprp2P/1nkbK3 w - - acn 372; acs 0; bm Nb6 Ne5; ce 32760; dm 4; pv Nb6 Qa1 Nxc4 Qa2 Na5 Qa1 Nxb3#;

I think it is a good idea for all of us to try to be as civil as possible.
Of course, that is just common sense.
User avatar
M ANSARI
Posts: 3726
Joined: Thu Mar 16, 2006 7:10 pm

Re: where can I find robbolito-rybka at long time control

Post by M ANSARI »

OK you are right and I am wrong ... if that makes you feel any better. You clearly were using this position to show that R3 finds the mate and RL does not, otherwise you would not have posted it ... otherwise your post simply makes no sense. Anyway I will not try to convince you either way, but you should at least keep an open mind that I might have my own reasons for believing RL is a clone and that it was not because of an "agenda" but rather many hours analyzing the actual games played. Even if someone would come out ala Strelka and fess up, you would still not believe it.

One more thing ... the reason I realized that the position that you posted will be solved by RL and would simply need more time is because when I looked at the position it was similar to many positions where I mentioned that RL is missing code that makes it play very poorly in some positions. Telling you what it is would simply make the cloners life much easier. So why don't you look at the position and try to figure out why RL takes so much time and R3 does not. Do you know why RL takes longer to solve this mate?
Last edited by M ANSARI on Wed Jan 13, 2010 10:13 pm, edited 1 time in total.
kingliveson

Re: where can I find robbolito-rybka at long time control

Post by kingliveson »

M ANSARI wrote:
kingliveson wrote:
M ANSARI wrote:And what agenda would that be? If it is to note that all the Ippolit based engines are derived from Rybka 3 and not an original work, then you are of course correct. I would hardly say that finding the truth is "an agenda".

With regards to hardware, I was using Skulltrail at 4 Ghz which has 8 cores and RL g3. The point of using Ponder ON was to increase time and thus remove time as a factor in the engine's play. For me I am more interested in evaluation advantages. I don't think that engines would be fighting for resources as they would have each been using 1 core only and there would be 6 cores spare. Again there could be a bug with RL g3 ponder ON that makes it play weaker, but looking at the games I couldn't see any such behavior. There was around 1% or 2% of RL games that were lost due to time, but most of those were in lost positions. I disregard such games and play additional games to cover for them as there is a possibility that instability in the engine before the time loss.

By the way Franklin you seem to come off as one real ass hole. I would be very happy to discuss with you my findings in an adult productive way. You seem to be unable to do that ... maybe you have an "agenda". I have done my tests and I am convinced. I might be wrong in my conclusion and my data might not be enough to convince you, and there is nothing I can do about that. But it would be nice if you would also do some testing and give some meaningful data output instead of simply dismissing everything as one side or the other.
This is funny, what else can I say?! I love this place. Ok, on a serious note, you never present anything to back up your claims.

1) You say one engine is a derivative work, but you don't have any supporting evidence. Take a look at what people think about your god Rybka.
2) When ever I make a statement, I provide concrete data to support what I have said. Go through these forum--I post results as well as the actual games that people can download and anylyze. CONCRETE DATA.
3) You refuse to provide any data to support your claims, whether it be the derivative issue or the strength of a particular engine. You made the claim (here) that given a position, you have yet to see where these 2 engines do not agree. So I gave you a postion ( 8/3N4/8/8/1pp5/brpp3p/qpprp2P/1nkbK3 w - - 0 1 ) to analyze with both engines and report back, and we continue to wait... Please do this and tell us your findings.

Accusations without evidence or unwillingness to provide one is called gossip, propaganda, fabrication, falsehood, fiction, hearsay, hoax, innuendo, lie, tale, belittlement, character assassination, cheap shot, denigration, mud, slime, slur, smear, vilification, etc. This is why I say you have an agenda. And why are you so angry?

You send me a position that Rybka 3 might have a bug or maybe RL has has a bug and you give that as DATA ??? But since you insist I get R3 sees mate in 4 and so does ZM II but RL thinks it is mate in 12 and takes a longer time. Actually I have seen Rybka also stick to the first mate it sees and not the shortest mate .... so ???? I am sorry but that is beyond pathetic. I can show you some even simpler bugs that R3 suffers from that were fixed and for sure there will be bugs in RL that need to be fixed. After all I don't think anyone said that R3 and RL are identical programs. Do you even know how to move chess pieces? Do you ever look at a chess game and analyse it and look for where one engine went wrong. I think I am one of the very few who will actually go into the games played in their tourneys and try to get information from them. It might be weird but I actually enjoy that. I have looked at and analysed several thousand R3 games and I feel I know where it is weak. R3 can devastate any engine on earth but yet can look feeble in some positions. I am not talking about some simple bug ... I am talking about poor evaluation. There are 3 main things that I can point out that are very obviously poor evaluation scenarios in R3 ... and R3 can get CRUSHED due to these poor evaluation scenarios even if it is on 8 cores and the other engine is on 1 core. THE SAME EXACT 3 weaknesses are there in RL or any of IPP derivatives. I will not post what these weaknesses are because I think that is not fair to Vas ... the original author. But it is no secret that I made a huge post about R3 bishop pair weakness, I see you have only 200 posts so you probably were not here when I posted it some time back. RL has the same incorrect evaluation of bishop pair and will get CRUSHED convincingly by an engine more than 250 ELO weaker than it the same way R3 gets crushed. This will most likely be "fixed" very quickly with new versions of the clone as evaluation parameters are tuned, but the cloners will find that actually tuning evaluation is not so simple. Fixing bugs is simple, but tuning evaluation is tremendously difficult.

First I recommend you look at the post I made about a year ago

http://talkchess.com/forum/viewtopic.ph ... ishop+pair

And then I would recommend you look at the following game played by RL on 1 core against N4 on 1 core and tell me what you think. I am hoping that you understand a little about chess otherwise you will not have a clue what I am talking about. Please run your engine and check the evaluation scores just in case you think I am making this up because of the "agenda" issue.

[Event "RLg3_Naum4_1_core_5_2"]
[Site "Microsoft"]
[Date "2010.01.10"]
[Round "4.1"]
[White "Naum 4_1 thread"]
[Black "RobboLito 0.085g3 x64"]
[Result "1-0"]
[ECO "A87"]
[Annotator "0.44;0.24"]
[PlyCount "159"]
[EventDate "2010.01.10"]
[EventType "tourn"]
[TimeControl "300+2"]

{Intel(R) Core(TM)2 Extreme CPU X9775 @ 3.20GHz W=14.7 plies; 1,294kN/s;
Perfect v12.ctg B=17.9 plies; 2,217kN/s; Perfect v12.ctg} 1. d4 {B 0} f5 {B 0}
2. g3 {B 0} Nf6 {B 0} 3. Bg2 {B 0} g6 {B 0} 4. Nf3 {B 0} Bg7 {B 0} 5. O-O {B 0}
O-O {B 0} 6. c4 {B 0} d6 {B 0} 7. Nc3 {B 0} Qe8 {B 0} 8. d5 {B 0} a5 {B 0} 9.
Ne1 {B 0} e6 {0.24/16 14} 10. Nd3 {0.44/15 10 (Be3)} e5 {0.17/18 9 (Na6)} 11.
f3 {0.30/15 14} Na6 {0.14/17 3} 12. e4 {0.28/16 13} fxe4 {0.20/18 20} 13. Nxe4
{0.25/16 10 (fxe4)} b5 {0.11/17 25 (Bd7)} 14. Qb3 {0.16/15 11 (b3)} Bd7 {-0.16/
18 22 (Nb4)} 15. cxb5 {0.00/15 12} a4 {-0.16/18 6} 16. Nxf6+ {0.00/16 10} Rxf6
{-0.17/18 12} 17. Qc2 {0.00/16 33} Bxb5 {-0.17/16 0} 18. Re1 {-0.05/16 7 (Be3)}
Rf8 {-0.26/17 6} 19. Be3 {-0.16/17 29} Qf7 {-0.14/18 9 (Rb8)} 20. Rad1 {-0.02/
16 9} Rab8 {-0.23/17 9} 21. b3 {-0.09/15 5 (a3)} axb3 {-0.46/20 9} 22. axb3 {
-0.20/16 8} Qf5 {-0.44/19 3} 23. Qb1 {-0.19/16 10 (Bf2)} Rf7 {-0.45/17 17} 24.
Rd2 {-0.23/17 17} Bc4 {-0.43/17 3 (c5)} 25. bxc4 {0.06/15 4} Rxb1 {-0.43/15 0}
26. Rxb1 {0.06/6 0} Rf8 {-0.41/20 22} 27. Ra1 {0.05/17 7} Nb8 {-0.43/20 33
(Qc8)} 28. Ra7 {0.04/16 9} Bf6 {-0.35/20 8 (c6)} 29. g4 {0.10/15 4} Bg5 {-0.35/
19 13} 30. f4 {0.11/15 2 (gxf5)} Bxf4 {-0.49/18 4} 31. Bxf4 {0.14/16 4} Qxg4 {
-0.49/17 0} 32. h3 {0.13/16 3 (Be3)} Qh4 {-0.65/18 2} 33. Be3 {0.13/17 5} Qxc4
{-0.65/17 0} 34. Ra1 {0.13/17 7 (Raa2)} Na6 {-0.73/19 7} 35. Re1 {0.14/17 13
(Rc1)} Kg7 {-0.73/18 10 (Qa4)} 36. Rc1 {0.19/16 3} Qb3 {-0.73/18 4} 37. Be4 {
0.16/16 3 (Rc6)} Qa4 {-0.63/17 8} 38. Re2 {0.15/17 7} Rc8 {-0.59/17 11 (Rb8)}
39. Kh2 {0.29/14 7} Rb8 {-0.46/17 11} 40. Bg5 {0.29/15 3 (Bd2)} Rb3 {-0.53/17
7 (Rf8)} 41. Rf1 {0.36/15 3 (Rc6)} Nb4 {-0.31/17 7 (Rb8)} 42. Nxb4 {0.44/15 3}
Rxb4 {0.00/19 6} 43. Bg2 {0.46/16 7 (Ref2)} h6 {-0.63/18 3} 44. Bd2 {0.40/17 9
(Bd8)} Rb3 {0.07/19 22} 45. Ref2 {0.40/16 2 (Rc1)} Qd7 {0.00/17 3} 46. Rc1 {0.
39/16 4 (Rf6)} Ra3 {-0.36/18 4 (g5)} 47. Bb4 {0.44/16 2 (Rc6)} Ra7 {-0.28/18 4
(Ra4)} 48. Rc6 {0.42/15 4 (Rfc2)} Kh8 {-0.35/17 5 (Qd8)} 49. Be4 {0.58/16 5
(Be1)} Qg7 {-0.22/17 4 (Kg7)} 50. Rc4 {0.84/15 8} Ra4 {0.00/18 5 (Ra1)} 51. Bc2
{0.84/15 2} Ra1 {0.00/18 5 (Ra8)} 52. h4 {0.96/15 3 (Rg2)} h5 {0.00/19 3 (Ra2)}
53. Bd2 {1.08/14 5} Ra3 {0.46/20 13} 54. Bc1 {1.16/15 2} Ra8 {0.40/19 4} 55.
Be4 {1.31/15 8} Rf8 {0.46/20 3 (Qg8)} 56. Rfc2 {1.11/15 4 (Rg2)} Rf7 {0.34/19 2
} 57. Bg5 {1.27/14 3 (Rg2)} Kg8 {0.37/19 2 (Qf8)} 58. Rg2 {1.38/17 5 (Kg3)} Kh8
{0.45/19 2} 59. Rb4 {1.39/16 3 (Rcc2)} Rf8 {0.65/18 5 (Qg8)} 60. Be3 {1.44/16
3 (Rb3)} Rf6 {0.89/17 3} 61. Rb8+ {1.45/17 3} Rf8 {0.89/16 0} 62. Rbb2 {1.45/
17 1} Rf6 {1.25/18 6} 63. Rg5 {1.85/16 3} Kg8 {1.05/19 3} 64. Rbg2 {2.13/16 3
(Rb8+)} Kf7 {1.21/20 2} 65. R5g3 {2.33/15 2 (Bd2)} Qg8 {2.00/16 2} 66. Bg5 {2.
96/14 2} Rf1 {3.71/17 3} 67. Bh6 {3.25/14 1} Rf6 {1.98/15 0} 68. Rc3 {3.48/16 2
} Qb8 {6.39/16 4} 69. Rgc2 {4.02/15 2 (Bxg6+)} c5 {4.39/17 3 (Kg8)} 70. dxc6 {
5.20/14 3} Qc7 {4.39/15 0} 71. Bd5+ {6.48/13 2 (Bg5)} Ke8 {6.44/17 2} 72. Ra2 {
6.94/14 4 (Bg5)} Qc8 {10.42/16 3} 73. Bg5 {8.42/14 3} Rf1 {7.29/17 3 (Rf5)} 74.
Rca3 {#15/12 5 (c7)} Rb1 {#10/18 2 (Kf8)} 75. Rf2 {#9/13 0} Rb2 {#9/19 2 (Rb4)}
76. Rxb2 {#6/3 0 (Bf7+)} Kf8 {#4/22 2 (e4)} 77. Ra7 {#4/3 0 (Rb7)} e4 {#3/20 2}
78. Bh6+ {#3/3 0} Ke8 {#2/21 1} 79. Bf7+ {#2/3 0} Kd8 {#1/21 1} 80. Bg5# {#1/3
0} 1-0
It's funny you keep giving me evidence to prove you wrong. So I did better than you asked. After analyzing the game per your request, I went a step further. I created an epd test set for all the positions played by black (RobboLito) starting from move 9 when it exited the book. I then used 5 engines to go through this position to see the percentage of agreement in move. I used 10 seconds per position. I arrived at 10 seconds using a basic formula to obtain the average time per move. The time control in the game you posted is 5+2. the game ended in 80 moves. I used [(300+(2x80))/80]+4. I add the 4 seconds to account for ponder. You used a CPU clocked at 3.2 GHz and I used one clocked at 3.6 GHz, so this shouldn't be an issue.

Here is the results:

Code: Select all

Engine	              Match	  Percentage						
	                 (Out of 69)	
						
RobboLito 0085g3 x64	51	      73.91%						
Deep Shredder 12 x64	45	      65.22%						
Zappamexico II x64	  44	      63.77%						
Rybka 3 x64	         40	      57.97%						
Naum 4 x64	          39	      56.52%						

Once again you are proven wrong. But you seem to get upset when you make unsubstantiated claims, and someone comes with data that contradicts your account. Why are you surprised that someone would actually check a statement you make and try to validate it?!

The test set and full analysis with all the engines can be downloaded from here under the name mansari_claims_011310.
Milos
Posts: 4190
Joined: Wed Nov 25, 2009 1:47 am

Re: where can I find robbolito-rybka at long time control

Post by Milos »

M ANSARI wrote:One more thing ... the reason I realized that the position that you posted will be solved by RL and would simply need more time is because when I looked at the position it was similar to many positions where I mentioned that RL is missing code that makes it play very poorly in some positions. Telling you what it is would simply make the cloners life much easier. So why don't you look at the position and try to figure out why RL takes so much time and R3 does not.
Why do you pretend that you know something about the RL and specially R3 code, when you have no clue at all?
You are the same guy that claimed R3 has its binary encrypted. For most ppl at this site this is sufficient to never take seriously anything you say...
User avatar
M ANSARI
Posts: 3726
Joined: Thu Mar 16, 2006 7:10 pm

Re: where can I find robbolito-rybka at long time control

Post by M ANSARI »

First of all ... my CPU is running at 4 Ghz and not 3.2 Ghz even if CB software thinks otherwise. Second ... do you think I fabricated this game and that this game was not actually played. If so, go through that game first running R3 then again running RL ... the time is not relevant because this issue is about EVALUATION. The problem is that you are going out of your way to "create" statistical tests when all you have to do is look at the game and look at the CHESS played and then look at the EVALUATIONS. You might think I fabricated my one year old post as well, but again anything is possible.

So my friend ... did you figure out why RL had a problem with the position you posted and thought was drawn? Have you seen a game where such behavior by RL causes it to lose games? ... because I have and it doesn't have to be an obscure position as you posted. Or are you drawing a blank? If you are drawing a blank I suggest instead of doing silly statistics that you look into the actual chess being played.
Milos
Posts: 4190
Joined: Wed Nov 25, 2009 1:47 am

Re: where can I find robbolito-rybka at long time control

Post by Milos »

M ANSARI wrote:If you are drawing a blank I suggest instead of doing silly statistics that you look into the actual chess being played.
Engines whose games you are "looking" have more than 3200 ELO on your hardware. No man on planet can take a win against them in even odds game. Most except few ppl on the planet have no clue for 99.9% of the time why engine is playing exactly what is playing.
And you base your assumptions on those completely statistically irrelevant 0.1% of the time when you actually have clue what and why engine played.