KnightX 2.7 64-bit Gauntlet for CCRL 40/15

Discussion of computer chess matches and engine tournaments.

Moderator: Ras

User avatar
Graham Banks
Posts: 45304
Joined: Sun Feb 26, 2006 10:52 am
Location: Auckland, NZ

KnightX 2.7 64-bit Gauntlet for CCRL 40/15

Post by Graham Banks »

gbanksnz at gmail.com
User avatar
Graham Banks
Posts: 45304
Joined: Sun Feb 26, 2006 10:52 am
Location: Auckland, NZ

Re: KnightX 2.7 64-bit Gauntlet for CCRL 40/15

Post by Graham Banks »

Code: Select all

CCRL 40/15 Rating List - Custom engine selection
1240737 games played by 2832 programs, run by 24 testers
Ponder off, General books (up to 12 moves), 3-4-5 piece EGTB
Time control: Equivalent to 40 moves in 15 minutes on an Intel i7-4770k.
Computed on May 1, 2021 with Bayeselo based on 1'240'737 games
Tested by CCRL team, 2005-2021, http://ccrl.chessdom.com/ccrl/4040/

Rank                 Engine                   Elo   +    -   Score  AvOp  Games
1 KnightX 2.61 64-bit                     2626  +32  -32  45.8%  +26.2   324
  KnightX 2.7 64-bit                      2622  +30  -30  45.1%  +35.6   368
  KnightX 2.4 64-bit                      2598  +28  -28  51.6%  -12.3   438
  KnightX 1.98 64-bit                     2542  +27  -27  49.1%   +7.4   482
  KnightX 2.3 64-bit                      2525  +26  -26  48.7%  +10.2   512
  KnightX 1.97a 64-bit                    2485  +27  -27  51.3%  -12.3   523
  KnightX 1.94 64-bit                     2352  +22  -22  49.5%   +2.6   744
  KnightX 1.93 64-bit                     2321  +20  -20  51.6%  -12.6   930
  KnightX 1.92                            2317  +19  -19  48.6%  +10.1  1046
gbanksnz at gmail.com
chrjly
Posts: 41
Joined: Wed Feb 03, 2021 10:45 pm
Full name: Christophe Jolly

Re: KnightX 2.7 64-bit Gauntlet for CCRL 40/15

Post by chrjly »

Thanks for testing KnightX Graham
At this time, the new 2.8 version has not made significant progress against other programs
I think that the program has reached its limits, because of bugs or bad parameter values somewhere
Or bad implementation, or lack of time to evaluate precisely a modification... Several possible causes
It was written in 1995 in C language and was (badly) designed to be fast. At that time I didn't imagine that 24 years later I would rediscover it and modify it, with not the same ability to concentrate
Anyway, either I make a significant progress, either I rewrite it entirely in C++
it may take some time before a new version comes out