Thanks for the comparison Louis! My Quad has some trouble competing with your Linux setup, but I let it accidently running so also at depth 45 now, after a few days... I think I'm doing more pruning than Stockfish but the Q6700 system is much much slower of course and using far less hash. 32 bit compile also does not help. Also Scid Serpent is doing longer exclusion searches, and short exclusion searches in nullmove also, and at some point those searches also cost, time and extra TT table space.
27. Nh5-g3 is a nice find, I don't see that move in two best moves here. But I agree that 27. g5 still is the best now
45 1934:21 +2.72 27.g5 dxe4 28.Qxe4 Bd6 29.f6 g6
30.Ng7 Qa8 31.h5 Qxe4 32.dxe4 Kg8
33.hxg6 fxg6 34.Ne6 h5 35.Nxc7 Bxc7
36.Kf2 Bb6 37.Kf3 b4 38.Rd1 a5
39.Rd3 Rf7 40.a3 (329.011.177.054) 2834
45 1934:21 +1.47 27.f6 g6 28.Ng7 dxe4 29.Qxe4 Qa8
30.Qxe5 Qc6 31.Qf4 Kh7 32.h5 g5
33.Qf5+ Kg8 34.Re2 Rd8 35.Ne6 Rd5
36.Qf3 Rc8 37.Ng7 Rd6 38.Qxc6 Rdxc6
39.Nf5 Rxf6 40.Rfe1 (329.011.177.054) 2834
Eelco
test postion: Pinkovetsky-Fischer, WC/27 final ICCF 2011
Moderators: hgm, Rebel, chrisw
-
Eelco de Groot
- Posts: 4561
- Joined: Sun Mar 12, 2006 2:40 am
- Full name:
Re: test postion: Pinkovetsky-Fischer, WC/27 final ICCF 2011
Debugging is twice as hard as writing the code in the first
place. Therefore, if you write the code as cleverly as possible, you
are, by definition, not smart enough to debug it.
-- Brian W. Kernighan
place. Therefore, if you write the code as cleverly as possible, you
are, by definition, not smart enough to debug it.
-- Brian W. Kernighan