Since you’re here...

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: Jangine 2023.03.31 (Windows and Linux)

on

Jangine is a chess engine (computer program that plays chess) I wrote in 2022 (parts in 2015).
Rating CEDR=2251

Language choice:
- C (later C++) was chosen in 2015 due to superior speed over most languages.
 - Because I had no C/C++ experience in 2015 (and still don't have very much), there are code quality issues.
 - Since many features (e.g. using a std::map vs a static C array) of C++ are too slow for my use case I am thinking of switching the engine back to C entirely.

v.2023.03.31:
The March release improves strength by fixing bug, but also reworks time management:
work around Arena bug by writing to stdout as little as possible
always encode correct mate distance in evaluation, even when retrieving from transposition table
this has the unfortunate side effect of causing more timeouts
also some of the mates are so deep they don't seem plausible
mate distance encoding: because mates beyond depth 100 are found, encode M1 as 199.99 instead of 299
now no more illegal moves should ever get played
fix bugs in is_pseudo_legal and add unit test
also check transposition table moves for legality
big fix: fix undefined behavior due to KILLER_TABLE being too small
time use: use time based on move number (use less time in the opening and more in the middlegame)

github:https://github.com/xjcl/jangine/releases/tag/v2023.03.31

Comments

Post a Comment