Peter
Thank you very much. I'm under Aquarium and it work also very well for me. No path problem, program found the exe by itself.
Best regards
I downloaded 4.1 and pointed it to where I feel is right, which was:
program files (x86\common files\chessbase\Engines.uci\rybka 4
did not work. I pointed it to many other locations etc. no work. What up ?
thank you
Wayne
I cannot find any chess program *.exe. Yet all my programs work ? any advise ? I hate Computers.
I should go back to OTB, but at 81, I think not :)
Wayne
My thank Uly
p.s. good luck in remainder of Jimmy's tournament.
Wayne
> Rybka 4.1 is the latest UCI Rybka chess engine and is a free update for Rybka 4 customers.
Thanx, Vas!
We'll have an interested look...
Quap
Note 1: The updater should be pointed to the directory in which the Rybka 4 executables reside. If you have trouble finding the Rybka 4 executables, you can perform a system file search for "Rybka*.exe".
However, this is incorrect. Instead of “Rybka*.exe”, the correct search term should be “*Rybka*4*.exe” (with the addition of an asterisk before “Rybka”, and also the insertion of a “*4” immediately after “Rybka”), for the following two reasons:
1. The Deep Rybka program installs executables called “Deep Rybka”, so that they will not be disclosed by the original search term suggested on your web site. Accordingly, users need to insert the asterisk wild card before “Rybka” (as well as after it).
2. By inserting the number 4, the many users who have many older versions of Rybka installed (i.e., Rybka 2 and 3), will not get confused with the many directories and files that contain such older versions.
> you can perform a system file search for "Rybka*.exe".
>
> However, this is incorrect. Instead of “Rybka*.exe”, the correct search term should be “*Rybka*4*.exe” (with the addition of an asterisk before “Rybka”, and also the insertion of a “*4” immediately after “Rybka”), for the following two reasons:
>
> 1. The Deep Rybka program installs executables called “Deep Rybka”, so that they will not be disclosed by the original search term suggested on your web site. Accordingly, users need to insert the asterisk wild card before “Rybka” (as well as after it).
>
A good advice, as this is what I encountered yesterday and was shocked to see search returned no results! :-)
I could not place it on my c drive it says i need administrator rights, even though i am the administrator.
http://rybkaforum.net/mwf/rybkaattach/68/320768/Rybka41Update.exe
Try installing a third-party solution, such as Free download manager (that's what I use to download my files)
http://www.freedownloadmanager.org/download.htm
Change User Account Control settings.
Analysis by Deep Rybka 4.1 SSE42 x64:
19...Ra5 20.h4 gxh4 21.g5 hxg5 22.Bxg5 Rh8 23.Nxd4 cxd4 24.Nd5 Rxb5 25.Rxb5 Bxb5 26.Rg1 Kg8 27.Bf3 Kf8 28.Qb1 Bc6 29.Nxb6 Bh6 30.Bxh6+ Rxh6 31.Nc4 Ne8 32.Qb4 Qe7 33.Na5 Bd7 34.Qb7 Rh8
= (-0.18) Depth: 25 00:44:33 1387mN, tb=2
19...Ra5 20.h4 gxh4 21.g5 hxg5 22.Bxg5 Rh8 23.Nxd4 cxd4 24.Nd5 Rxb5 25.Rxb5 Bxb5 26.Rg1 Kg8[] 27.Bf3 Kf8[] 28.Qb1 Bc6 29.Nxb6 Bh6 30.Bxf6 Qxf6 31.Nc4 Qd8 32.Qb4 Rg8 33.Nxe5 Rxg1+ 34.Kxg1 Qg5+
= (0.00) Depth: 26 10:13:57 19431mN, tb=254
(Williamson, Microsoft 15.03.2011)
>depth 26 in a complex, closed position might be considered an example of an exploding branching factor, but this isn't the stalling bug...
> it may be that people that claim this just didn't have the nerve to wait for the new iterration to come up
No, it was debugged with the Visualizer, and when the stall bug hit the search just dies, Rybka is using 100% of the CPU but doing nothing, she dies other than receiving further commands. Basically, with the Visualizer you could tell the difference between an exploding branching factor and the stall bug because in the former you can see what is Rybka doing all that time, and in the latter you can see that Rybka is doing nothing.
So, here Harvey could have checked with the Visualizer what was Rybka doing on those 10 hours, it could have been the unfixed wrong move ordering bug where Rybka randomly (you never know when she'll do it) orders some random move (you'll never know what move or where) first (in some deep branch) and has to resolve it first before ordering the right move, and it could easily take 10 hours to do so (unless the bug was fixed, I'm just saying the report of what happened is incomplete, we just know is not the stall bug because Rybka eventually came back).
>In a nuttshell, we IA people feel this is a bug,
Exploding branching factor is not a bug, it would be a bug if with the Vizualizer the user notices Rybka is doing it wrong. There have been reports of those branching factors since Rybka 2 or before, Vas said they're normal (in fact, the stall bug was overlooked in Rybka 4 because he thought it was exploding branching factor).
>I personaly don't have the time to test the problem in detail
Nobody has, that's why it could be some bug in there that causes the exploding branching factor, but we don't know unless we look at Vizualizer output.
It's possible the exploding branching factor is not the problem, but a symptom of an underlying bug. You'd need to check the Visualizer to see what Rybka is doing when that happens for any abnormality.
> Basically, with the Visualizer you could tell the difference between an exploding branching factor and the stall bug because in the former you can see what is Rybka doing all that time, and in the latter you can see that Rybka is doing nothing.
>
> So, here Harvey could have checked with the Visualizer what was Rybka doing on those 10 hours, it could have been the unfixed wrong move ordering bug where Rybka randomly (you never know when she'll do it) orders some random move (you'll never know what move or where) first (in some deep branch) and has to resolve it first before ordering the right move, and it could easily take 10 hours to do so (unless the bug was fixed, I'm just saying the report of what happened is incomplete, we just know is not the stall bug because Rybka eventually came back).
>
Vas himself said the visualizer was untested and somewhat buggy. He also recommended that most users not use it, and that it does support multi-pv. And why should the users have to check the visualizer to see if Rybka is working or not? Isn't that what the bug fix was for?
- The visualizer is a useful tool, but it is in alpha form. It is useful for people who are willing to put up with bugs in order to get more information out of the engine.
> User hostile
Well, Aquarium is like that and many people use it, I don't see why wouldn't they use the Visualizer (or at least try it, maybe they discover that the extra information is of no use to them).
> No, it was debugged with the Visualizer
You are right on all accounts, I totally forgot about the Visualizer.
19...Ra5 20.h4 gxh4 21.g5 hxg5 22.Bxg5 Rh8 23.Nxd4 cxd4 24.Nd5 Rxb5 25.Rxb5 Bxb5 26.Rg1 Kg8 27.Bf3 Kf8 28.Qb1 Bc6 29.Nxb6 Bh6 30.Bxh6+ Rxh6 31.Nc4 Ne8 32.Qb4 Qe7 33.Na5 Bd7 34.Qb7 Rh8
= (-0.18) Depth: 25 00:44:33 1387mN, tb=2
Then you get nothing, ever. THAT was fixed.
In this specific case, if it was a fail low, you have to switch on "Show upperbounds" in engine settings, then, if you see a fail low, you know it could take 10 hours or more to resolve, so what you do it forcing 19...Ra5, and reach depth 25 (which is equivalent to depth 26 at the root), it'll turn it into a fail high from the white side and it'll be solved in reasonable time (if you're lucky even relative root depth 27 could be reached in another 50 minutes).
There was more interest in this thread when all it said was "TBA".
Vas
> If it's not too much trouble, can you briefly describe the problem and solution?
I think the problem might be what happened to me. I directed the updater to the Rybka folder in C:\Aquarium\Engines
However the Rybka engines are actually in subfolders of this folder eg C:\Aquarium\Engines\Rybka\1-cpu\x64 or
C:\Aquarium\Engines\Rybka\Multi-cpu\x64
The updater should perhaps be capable of searching down the subfolders. At any rate, when it's pointed to the right folder it works okay..

Powered by mwForum 2.27.4 © 1999-2012 Markus Wichitill