55 self-play elo at normal time controls, about double that at cyclic time control (1.0 did not handle cyclic well)
Windows binaries provided as usual - you can likely get better performance compiling yourself with "make pgo". This assumes a machine that supports pext, if anyone wants to try compiling with pgo for older machines I can give directions on how to do it, it's simple
From the command line 'go depth 15' exits the program. I tried ucinewgame and position startpos first, to no avail. So I had to install under Shredder both your exe and my compile to measure speed.
From the command line 'go depth 15' exits the program. I tried ucinewgame and position startpos first, to no avail. So I had to install under Shredder both your exe and my compile to measure speed.
Some strangers and I have written this engine for about 4 months now, and we estimate its strength to be between 2800 and 2900.
We're still figuring out the build process, so for now, you might have to compile yourself. It's a single makefile.
September 2, 2020: Stockfish 12 released. This version of Stockfish plays significantly stronger than any of its predecessors. In a match against Stockfish 11, Stockfish 12 will typically win at least ten times more game pairs than it loses.
Some strangers and I have written this engine for about 4 months now, and we estimate its strength to be between 2800 and 2900.
We're still figuring out the build process, so for now, you might have to compile yourself. It's a single makefile.
Some strangers and I have written this engine for about 4 months now, and we estimate its strength to be between 2800 and 2900.
We're still figuring out the build process, so for now, you might have to compile yourself. It's a single makefile.
Some strangers and I have written this engine for about 4 months now, and we estimate its strength to be between 2800 and 2900.
We're still figuring out the build process, so for now, you might have to compile yourself. It's a single makefile.
The engine supports all important UCI commands together with additional print (to print the board) and eval for a detailed overview of the evaluation.
We'd also like to have this run in CCRL, but we're not very familiar with the process. We hope there is interest in testing our engine.
Not clear what figuring out the build process means. And, at your home page you write:
A few compiler warnings about unused functions might pop up. Those functions are only from the syzygy code which have been copied from Fathom
If you don't use syzygy/*.c in your make file, only syzygy/tbprobe.c then all compiler warnings disappear.
Oh thank you very much on this one!
What we mean is that we are not yet able to build a static executable due to marche=native which is required for our SSE/AVX code to run.
Therefor one needs to compile the project in order to get a working executable. We are trying to solve this issue at the moment.
I estimate from limited fast testing that Beef is around 3000.
I work on a linux machine, so the makefile should work for linux, and my windows compiles are made with visual c++, but I am not completely sure yet if everything is correct. Please tell me if there are any problems with the given binaries. Thanks![/i]
[/quote]
55 self-play elo at normal time controls, about double that at cyclic time control (1.0 did not handle cyclic well)
Windows binaries provided as usual - you can likely get better performance compiling yourself with "make pgo". This assumes a machine that supports pext, if anyone wants to try compiling with pgo for older machines I can give directions on how to do it, it's simple
[/quote]
