Hi Matthew,matthewlai wrote:This one only has some small changes. No 100+ Elo jump like last time.
https://bitbucket.org/waterreaction/gir ... 150908.zip
Changes:
1) Score reporting is now scaled down by 1/10. Hopefully that will play better with score-based adjudication systems. Score magnitudes are now more inline with what other engines report, though it's still probabilistic.
2) Time management has been improved (thanks to Graham Banks' testing that led me to notice this). About 33 Elo gained.
3) Gaviota tablebases now supported. See https://bitbucket.org/waterreaction/giraffe for details. I want to switch to a neural-network based endgame system later, but EGTB will do for now.
By the way, Giraffe is now open source, and the thesis is now available online. See thread on the programming forum if interested - http://talkchess.com/forum/viewtopic.ph ... 136#640136
This is probably going to be the last Giraffe release for a while. I have just submitted and defended my thesis. I think my brain needs a break from working on Giraffe full time for 3 months.
Will be travelling for a few weeks before getting back to Giraffe.
Thanks
I played a few games against it now after I followed its reported progress since the first release and I must say I am really surprised how good it plays openings now
compared to the first few released games I have seen here. My congratulations it is already quite strong against Humans at least.
Memory usage seems hardcoded to be around 300MB right?
What would be the commandline param for WB to always load the Gaviota bases at start?
I noticed that the eval/meval files still are ascii - can you gain something later by a binary approach? (I guess the files will grow quite a bit when you do more training/learning?)
Guenther