Intel i5 Quad
ChessGUI
256mb hash each where possible
3-4-5 piece tablebases
Ponder off
GBSelect2014.cgb book
40 moves in 25 minutes repeating (adapted for the CCRL)
2 cycles 30 rounds
All engines 64-bit where available
Alternatively, if you install TLCV (Tom's Live Chess Viewer) on your computer, you can watch the games live move by move. You'll also be able to chat to others following the tournament in the chatroom there. http://home.pacific.net.au/~tommyinoz/client.zip
Host - GrahamCCRL.dyndns.org Port - 16002
You're welcome.
This tournament will give me a rough idea as to the strength of four new engines at this time control - CyberPagno, Ecce, Nemeton and Soldat.
took a peek through TLCV, and it seems you're not using the updated Nemeton version that actually supports x moves in y minutes timecontrols and plays a bit better as well.
took a peek through TLCV, and it seems you're not using the updated Nemeton version that actually supports x moves in y minutes timecontrols and plays a bit better as well.
took a peek through TLCV, and it seems you're not using the updated Nemeton version that actually supports x moves in y minutes timecontrols and plays a bit better as well.
I'll take a look.
It is the latest version that is being used. I checked.
took a peek through TLCV, and it seems you're not using the updated Nemeton version that actually supports x moves in y minutes timecontrols and plays a bit better as well.
I'll take a look.
It is the latest version that is being used. I checked.
Nah, was leaving around half it's time on it's clock at move 40 when updated version would leave exactly 2 seconds.
Versionnumber remained the same though as it was a quick update not what I would consider a new release. That's comming in a couple weeks.
Could be the culprit but the updated version was dated nov 26th 19:16.
took a peek through TLCV, and it seems you're not using the updated Nemeton version that actually supports x moves in y minutes timecontrols and plays a bit better as well.
I'll take a look.
It is the latest version that is being used. I checked.
Nah, was leaving around half it's time on it's clock at move 40 when updated version would leave exactly 2 seconds.
Versionnumber remained the same though as it was a quick update not what I would consider a new release. That's comming in a couple weeks.
Could be the culprit but the updated version was dated nov 26th 19:16.
Could you paste the "level" command that is sent to the engines as that (a horribly mangled level command, a level command each move, who knows) is the other explanation. But a lot of programs will have problems then.
