Ply 27: 01:43:39
Ply 28: 12:47:39
I seem to remember that a higher plies (>32) I have seen Rybka spend more than 24 hours considering a move in the middle of a ply, but for me at >30 plies, this is the most extreme branching that I can remember. Does anybody have any more extreme examples.
Ply 28: 12:47:39
I seem to remember that a higher plies (>32) I have seen Rybka spend more than 24 hours considering a move in the middle of a ply, but for me at >30 plies, this is the most extreme branching that I can remember. Does anybody have any more extreme examples.
Here's an extreme example from wac042. Not Rybka, though! 
(no hash tables and just getting started on move ordering...)

(no hash tables and just getting started on move ordering...)
depth nodes time eval pc ---------------------------------------------------------------------------- 6 2436823 3.16 328 Bb4a5 Bg7f8 Qa3c3 Bf8b4 Ba5b6 Bb4c3 7 61594579 80.40 325 Bb4a5 Bg7f8 Qa3c3 Bf8b4 Ba5b4 Nd7e5 e3e4
Good luck with your engine!
What language and compiler are you using?
What language and compiler are you using?
Thanks! I'm writing it in c and compiling with Microsoft Visual C++ 2010 Express. It's been a lot of fun so far! Except for a course in basic that I took in college in the mid-1970's, I don't have any formal programming education, so it takes awhile...
I recall someone reporting a branching factor of >68 for Rybka 3 at some point, but such big branching factors are normal for failing moves (I think that was a reason for Vas to overlook the MultiPV bug, he thought the huge branching factor was related to a deep failing move, or something).
Powered by mwForum 2.27.4 © 1999-2012 Markus Wichitill