The vast majority is UCI, some are winboard. All of the engines have a CCRL rating, so one may assume they are crash free playing games.chrisw wrote: ↑Mon Jun 29, 2020 11:01 amAre they uci-compliant and checked non-crashing?Rebel wrote: ↑Sun Jun 28, 2020 5:44 pmA try to collect the websites of engine authors among other things.
http://rebel13.nl/download/download-engines.html
1. Engines listed on alphabet, click on the picture to move to the author's web site.
2. ELO's are based on the CCRL 40/2 rating list of June 2020 on a single processor.
3. When a website is not (or no longer) available the last known version will be offered for download.
Website engines
Moderators: hgm, Dann Corbit, Harvey Williamson
Forum rules
This textbox is used to restore diagrams posted with the [d] tag before the upgrade.
This textbox is used to restore diagrams posted with the [d] tag before the upgrade.
Re: Website engines
90% of coding is debugging, the other 10% is writing bugs.
Re: Website engines
Hi Ed,
The official Texel repository is actually here:
https://github.com/peterosterlund2/texel
The link you have is from someone else who uploaded source code for released Texel versions (nothing wrong with that) before I made the full Texel history available on github.
The official Texel repository is actually here:
https://github.com/peterosterlund2/texel
The link you have is from someone else who uploaded source code for released Texel versions (nothing wrong with that) before I made the full Texel history available on github.
Re: Website engines
Fixed it.petero2 wrote: ↑Mon Jun 29, 2020 5:21 pmHi Ed,
The official Texel repository is actually here:
https://github.com/peterosterlund2/texel
The link you have is from someone else who uploaded source code for released Texel versions (nothing wrong with that) before I made the full Texel history available on github.
90% of coding is debugging, the other 10% is writing bugs.
-
- Posts: 38
- Joined: Tue Jan 01, 2019 8:34 am
- Full name: Siddhartha Chaudhary
Re: Website engines
it is really helpful ,plz add chess engine from the elo rating also .
can gingko be found here ?
can gingko be found here ?
Re: Website engines
Gingko is part of ChessBase and as far as I know doesn't have an own website.chysiddh14 wrote: ↑Tue Jun 30, 2020 1:09 amit is really helpful ,plz add chess engine from the elo rating also .
can gingko be found here ?
90% of coding is debugging, the other 10% is writing bugs.
Re: Website engines
Hi Ed,
Raven https://github.com/sgriffin53/raven/
Might be worth adding; it is actively developed and steadily improving, currently at ~2400 ELO.
Raven https://github.com/sgriffin53/raven/
Might be worth adding; it is actively developed and steadily improving, currently at ~2400 ELO.
Re: Website engines
Technically Ginkgo has never been released, we know it's the engine powering Fritz 17, just like Rybka 5 powered Fritz 15 or Rybka 6 powered Fritz 16, but the CCRL doesn't acknowledge rebranding (if they did we'd have Pandix and Fritz 12 on the CCRL's Index as they're unique and unrelated to Ginkgo. Plus Rybka 4 has no reason to be in there since it's just some older version of Fritz 16.)
Re: Website engines
Very good.mhib wrote: ↑Tue Jun 30, 2020 8:39 pmHi Ed,
Raven https://github.com/sgriffin53/raven/
Might be worth adding; it is actively developed and steadily improving, currently at ~2400 ELO.
Consider it done.
90% of coding is debugging, the other 10% is writing bugs.
Re: Website engines
It would be nice to have some Chess Tiger (especially Gambit Tiger) UCI versions.
Rebel wrote: ↑Sun Jun 28, 2020 5:44 pmA try to collect the websites of engine authors among other things.
http://rebel13.nl/download/download-engines.html
1. Engines listed on alphabet, click on the picture to move to the author's web site.
2. ELO's are based on the CCRL 40/2 rating list of June 2020 on a single processor.
3. When a website is not (or no longer) available the last known version will be offered for download.
Re: Website engines
I don't have the uci editions and in case I had them, these are copyrighted.
90% of coding is debugging, the other 10% is writing bugs.