Skip to main content

Since you’re here...

... we have a small favour to ask. More people, like you, are reading and supporting our blog: "Chess Engines Diary". And unlike many other sites and blogs, we made the choice to keep our articles open for all, regardless of where they live or what they can afford to pay.

We hope you will consider supporting us today. We need your support to continue to exist, because good entries are more and more work time. Every reader contribution, however big or small, is so valuable. Support "Chess Engines Diary" even a small amount– and it only takes a minute. Thank you.

============================== My email: jotes@go2.pl



Chess engine: Simbelmyne 1.7.0

 


Simbelmyne UCI engine
Rating CEDR=2474

v.1.7.0:
What's new
This release mostly focuses on improving the search. Simbelmyne prunes much more accurately (and aggresively!), and the average branching factor across the bench suite has dropped significantly.

A small gauntlet puts it at ~2900 Elo, around 233 Elo stronger than Simbelmyne v1.6.0

Rank Name                          Elo     +/-   Games   Score    Draw 
   0 Simbelmyne main                79      13    2261   61.1%   25.4% 
   1 Nalwald 15 (2912)              24      28     452   53.4%   24.6% 
   2 Avalanche 1.1.0 (2902)         15      27     452   52.1%   27.2% 
   3 Cheers 0.3.1 (2838)           -68      27     452   40.4%   28.5% 
   4 Princhess 0.13 (2845)        -166      31     452   27.8%   21.9% 
   5 Simbelmyne v1.6.0 (2750?)    -233      31     453   20.8%   24.7% 

Added features
🔍 Search
SPSA rqetune of search parameters (37.9 +/- 12)
Refactor futility pruning (13.1 +/- 8.8) (#198)
Switch to log-based LMR (32.8 +/- 16.3)
Reduce soft-time (32.5 +/- 15.6) (#200)
Enable LMR in check (27.5 +/- 15.6)
Stop searching if there's only one legal move
Use LMP formula instead of LMP table (19.5 +/- 12.9)
Switch to simpler FP formula (14 +/- 10.9) (#201)
Another SPSA re-tune (66.6 +/- 13.6)

⚖️: Evaluation
Fix contempt factor

🐛 Bugfixes
Actually use soft-time limit instead of hard-time (9.3 +/- 9.4) (#197)
Fix PVS (50.2 +/- 18) (#199)
See the respective PRs for self-play results where relevant

Choosing a binary
This release comes with precompiled binaries for all major platforms. Because the engine benefits tremendously from more modern CPU instruction sets, there are binaries compiled for major instruction sets, following the x86-64 microarchitecture levels as a naming scheme.

Realistically, on modern hardware (< 10 years old), you should be okay to use the binaries labeled V3. If the engine crashes within the first seconds, try V2, and so on.

What's Changed
Search/better time management by @sroelants in #197
Move futility pruning into move loop by @sroelants in #198
Switch to simpler futility pruning formula (14 +/- 10.9) by @sroelants in #201

Simbelmyne 1.5.1 - results:
Critter 1.6a0.5/3-23 Partii
Caissa 1.180/3-33 Partii
Alexandria 6.1.00/3-33 Partii
Akimbo 1.0.00/3-33 Partii
Victoire 1.3.02/2+22 Partii
Zagreus 5.02/2+22 Partii
Cadabra 2.0.12/2+22 Partii
Tcheran 2.22/2+22 Partii
Yakka 1.01.5/2+12 Partii
Delocto 0.71/2+02 Partii
Bagatur 3.7e0.5/2-12 Partii
Vafra 14.12.1 Stockfish0/2-22 Partii
Peacekeeper 2.400/2-22 Partii
Pawn 3.00/2-22 Partii
Obsidian 12.00/2-22 Partii
Midnight 90/2-22 Partii
Velvet 7.3.00/2-22 Partii
Clarity 6.0.00/2-22 Partii
Seer 2.7.00/2-22 Partii
Rebel 16.30/2-22 Partii
Arasan 24.20/2-22 Partii

Simbelmyne 1.7.0 download


Comments

Popular posts from this blog

New Strong Engines Test, by Chess Engines Diary, 2024.04.12

  💾  552 (!) games from the tournament download   👍 @chessenginesdiary  Country - Poland, City -  Malbork 🕓 Time 3'+3" 💻HP Pavilion i5-1035G1 8GB RAM 🖬 GUI-Banksia All  CEDR  317.321 games download  (01.04.2024 - 3'+3")  HypnoS 030424, Yuli GM Pro 16, Stockfish 16.1 and ShashChess 35 . These four engines scored the same number of points and placed at the top of the table in this strong tournament. Tech table: Engine KN/move NPS dep/mov time/mov mov/game time/game fails Alexandria 6.1.0 3218 576429 30.2 5.6 56.7 316.2 Berserk 13 4779 841025 36.7 5.7 56.0 318.1 Brainlearn 28 2275 366977 31.4 6.2 43.5 269.4 Caissa 1.18 5492 923486 30.2 5.9 50.4 299.7 Clover 6.1.19 4803 854377 31.4 5.6 62.2 349.4 Cool Iris 12.10 2201 356730 27.6 6.2 51.2 315.5 CorChess 20240331 2253 372774 27.4 6.0 52.2 315.8 Crystal 8 3582 571994 20.3 6.3 47.7 298.8 Fire 9.3 5225 876565 22.0 6.0 55.5 331.1 Fisherov chess monk 1.2 3487 619728 36.0 5.6 60.4 340.0 Hyp

End of the Torch Experiement?

 Andrew Grant: "Almost exactly one year ago we announced the release of Torch. We were a bit ambitious at the time, and announced it as the #2 engine, after beating Leela in the most recent Bullet event at CCC at the time. Today, that claim rings much more true, although still has some minor points of contention. Torch has beaten Leela in multiple Bullet and Blitz events in a row; Never managed to win one of the Rapid events; But has beaten Leela in a h2h classical event. Chesscom got into the space out of a need to develop a replacement for Komodo. They needed a strong chess engine which could be used for integrating their other products. Many features on Chesscom, from Game Review, to puzzle generation, to Bots (obviously!) are powered by high quality engines. The goal was always for that. In fact, despite me being the only full time employee working on Torch, a plurality of my time was spent on things not related to Torch's strength. Its a bit self-aggrandizing, but the Tor

SugaR AI SE wins New Strong Engines Test, by Chess Engines Diary, 2024.05.25-29

The tournament of strong chess engines was won by SugaR AI SE . This is a very good compilation though. In places 2 to 4: Stockfish 20240523 Ivec , Sun 15 and Deep Blue-20240518-assassin . All CEDR  333.448 games download  (01.05.2024 - 3'+3")  💾  600 (!) games from the tournament download 👍 @chessenginesdiary Country - Poland, City -  Malbork   🕓 Time 3'+3"  💻HP Pavilion i5-1035G1 8GB RAM 🖬 GUI-Banksia Tech table: Engine KN/mov NPS dep/mov time/mov mov/game time/game fail Caissa 1.18 4920 906675 27.5 5.4 64.4 349.7 Chess-System-Tal-2.00 2263 448276 20.6 5.0 64.5 325.8 Clover 6.1.24 JA 4435 820982 27.6 5.4 70.4 380.3 Cool Iris 12.10 2138 356907 26.7 6.0 54.2 324.7 CorChess 20240523 1885 330718 28.5 5.7 55.7 317.3 Crystal 8 3408 585347 20.7 5.8 55.3 321.7 Deep Blue-20240518 1717 308790 31.1 5.6 59.6 331.4 Dragon 1 by Komodo 3688 693178 24.0 5.3 68.2 362.7 Fisherov chess monk 1.2 3290 620116 34.0 5.3 67.9 360.2 HypnoS 160524 1871 328

New chess engine: Steel Fighter (Stockfish derivatives)

Steel Fighter by Solista.  Eduard NemethI created this engine for playing on Lichess. The engine uses an extremely fast random op. MultiPV mode! With a value of 2 (default) the engine is only slightly slower than Stockfish dev. Positionally, the Enghine plays a little weaker than Stockfish dev, but tactically it is much better. On Lichess, where half of the enemies are non-Stockfish and make more tactical mistakes, you'll have more fun with Steel Fighter. Steel Fighter is also a good addition for short tactical analyses. Download Win 64 Bit (avx2, bmi2, sse41, source code): https://pixeldrain.com/u/Yqp3g6TT Note: This engine uses special code and specially adapted networks. A change leads to worse results and also incorrect ratings. Steel Fighter download

Chess engine: Deep Ripper -1 (Stockfish derivatives)

Deep Ripper (Stockfish derivatives) by Eduard Nemeth Author: " Here is the first official version of Deep Ripper. For now, I have decided on a version that can be used for any hardware. If you only have a few cores, you should set the number of variants to 1 or 2. However, 4 variants are standard (1 to 10 can be set), which deliver very good analysis results on 6 or more cores. Playing on servers is also possible. I hope you enjoy testing." Deep Ripper - 1 download Deep Ripper - 1 download This engine uses the Random Op. MultiPV mode. Here, several variants are examined in parallel and, after e.g. 16 plies, merged into a single variant. This is not the same as the normal multi-variant mode, where all variants are examined separately. The results can be completely different! So it makes no sense to create an identical engine without the random mode.