What's the latest compiled version of Robo ?

[bigo]

Everyone is claiming it's actually better than Rybka3 true

[Terry McCracken]

Everyone is claiming it's actually better than Rybka3 true

Go look it up. Anyone can. It's close in strenght to Rybka 3, maybe a tad stronger as it contains it would seem Rybka 4.

[Graham Banks]

Everyone is claiming it's actually better than Rybka3 true

Who knows and who cares? A new buggy version seems to come out every day from different triers. Unsurprising when the code is incomplete (now why would that be?).

[Graham Banks]

Also, how do you know the versions coming out evry day are buggy? Have you tried them? Exactly which are the bugs?

I can read.

[Spock]

Everyone is claiming it's actually better than Rybka3 true

Go look it up. Anyone can. It's close in strenght to Rybka 3, maybe a tad stronger as it contains it would seem Rybka 4.

When did Vasik say his house had been intruded and Rybka 4 robbed? He did say the machines on which he develops Rybka have no internet connection.

Incredibly valid point. But don't forget about Lukas, who has the latest version playing on playchess sometimes, doesn't he ? Or am I mistaken ? Is it possible one of his machines has been hacked and an exe obtained ? It could only be an exe, becuase as you say only Vas has the source

[Graham Banks]

Also, how do you know the versions coming out evry day are buggy? Have you tried them? Exactly which are the bugs?

I can read.

So you do care?

You already know my opinion.

[M ANSARI]

I really doubt that the latest Robo is based on Rybka 4. It would take a lot longer to decompile and according to Vas it is from Rybka 3. Decompiled source code can run without encryption natively, so it would probably execute cycles much quicker I would guess at least 10% to 15% quicker depending on how heavy the encryption is. This seems like a more likely scenario than having the latest beta get hacked from Lukas's computer. This also seems to hold out in testing as the engine seems to do better at very fast time controls with no increment against R3. At long time controls the engines perform almost identical. You have to remember that we are talking strictly on single core engines. And really if someone has no problem using a Rybka 3 clone, he might as well go to a warez site and download an illegal copy of MP Rybka 3.

[Jouni]

I think we can consider RobboLito as Rybka3+. It fixes 1) hash use bug 2)
node and depth display 3) bishop promotion and additionally it's lightly stronger and free

Jouni

[M ANSARI]

I think we can consider RobboLito as Rybka3+. It fixes 1) hash use bug 2)
node and depth display 3) bishop promotion and additionally it's lightly stronger and free

Jouni

1. Not true. The hash bug does not affect single core Rybka 3 so this cannot be called a bug in SP R3

2. Not true. Vas has on quite a few occasions mentioned that he simply likes to "real" nodes and depth. In other words he does not like to count nodes which he considers as garbage nodes. And for depth he prefers depth were he has confidence in the accuracy of search for that depth. You can disagree with how he counts this but you will find that no two engine writers use the same counting methods, since it is a preference and not an exact science.

3. Again not true. I am assuming you are refering to the "wrong bishop" knowledge being omitted in Rybka 3. The situation arises when the opposing side with inferior material controls the queening square and the bishop's color is not the same as the queening square and thus it is a dead draw. Robo suffers from this just like R3 does, and I am not sure who came up with the fact that it does not. You can check it out yourself in this position

[d]k7/P7/8/1p2K3/8/P7/5B2/8 w - - 0 107


Actually IMHO in the following position shows that Robo suffers from R3 in a very similar fashion as it does not show a dead draw here. At least not on my computer.


[d]Q7/1k6/3K4/1p6/8/P7/5B2/8 b - - 0 108

[ernest]

[d]k7/P7/8/1p2K3/8/P7/5B2/8 w - - 0 107

Strange, my Toga II 1.4 beta5c 2cpu traps ("causes an exception") on that position...