Seagull changes:
- source code cleaned up, simplified, and broken up into various source and header files
- a couple of VS code analysis fixes (ex: gen_kpk() was causing stack exceed error)
- compiler warnings resolved up to level 4
- benchmark and perft utilities added (type 'bench' and engine will write a date-stamped text file with results)
- support for syzygy tablebases
All include Visual Studio 2015 project files and x64 binaries.
Best Regards,
Norm
thanks Norman!
+5 elo to Fridolin and +146 elo to Gull would have been much more appreciated.
Seagull changes:
- source code cleaned up, simplified, and broken up into various source and header files
- a couple of VS code analysis fixes (ex: gen_kpk() was causing stack exceed error)
- compiler warnings resolved up to level 4
- benchmark and perft utilities added (type 'bench' and engine will write a date-stamped text file with results)
- support for syzygy tablebases
All include Visual Studio 2015 project files and x64 binaries.
has not listed your releases, while including some other derivatives (Sugar, for example), especially since you obviously had to put in some real effort into producing actual Elo gains over the originals.
Seagull changes:
- source code cleaned up, simplified, and broken up into various source and header files
- a couple of VS code analysis fixes (ex: gen_kpk() was causing stack exceed error)
- compiler warnings resolved up to level 4
- benchmark and perft utilities added (type 'bench' and engine will write a date-stamped text file with results)
- support for syzygy tablebases
All include Visual Studio 2015 project files and x64 binaries.
has not listed your releases, while including some other derivatives (Sugar, for example), especially since you obviously had to put in some real effort into producing actual Elo gains over the originals.
Regards,
CL
Hi Carl,
Please send me a complete list of derivatives that you feel deserve or don't deserve listing and I will consider them. I have little time for computer chess these days, so my decisions may seem arbitrary to a knowledgeable insider such as yourself. It is the amount of coding changes that interests me here: What percentage of the original code remains unchanged compared to new code? Are the changes substantive, or merely a restating, a re-arrangement of original code, or an implementation of well-known techniques? Is the fixing of several bugs sufficient to announce another derivative engine with a different name? These are the questions that I do not have time to research and answer.
Keep in mind that Elo gains have nothing to do with an engine's authorship.
I see Norman's valuable contributions as an appeal to the authors of these engines to implement his bugfixes and improvements. If they do, I will consider that as a new version and it is possible I will add Norman's name as a co-author of that engine.
Seagull changes:
- source code cleaned up, simplified, and broken up into various source and header files
- a couple of VS code analysis fixes (ex: gen_kpk() was causing stack exceed error)
- compiler warnings resolved up to level 4
- benchmark and perft utilities added (type 'bench' and engine will write a date-stamped text file with results)
- support for syzygy tablebases
All include Visual Studio 2015 project files and x64 binaries.
has not listed your releases, while including some other derivatives (Sugar, for example), especially since you obviously had to put in some real effort into producing actual Elo gains over the originals.
Regards,
CL
Hi Carl,
Please send me a complete list of derivatives that you feel deserve or don't deserve listing and I will consider them. I have little time for computer chess these days, so my decisions may seem arbitrary to a knowledgeable insider such as yourself. It is the amount of coding changes that interests me here: What percentage of the original code remains unchanged compared to new code? Are the changes substantive, or merely a restating, a re-arrangement of original code, or an implementation of well-known techniques? Is the fixing of several bugs sufficient to announce another derivative engine with a different name? These are the questions that I do not have time to research and answer.
Keep in mind that Elo gains have nothing to do with an engine's authorship.
I see Norman's valuable contributions as an appeal to the authors of these engines to implement his bugfixes and improvements. If they do, I will consider that as a new version and it is possible I will add Norman's name as a co-author of that engine.
Best regards,
Ron
Because no one so far mentioned it, I want to add that all the numbers (elo increase) given are w/o any objective reference so far.