Meltdown - UCI chess engine
Author: Hans Binderup
NOTE: this is a hobby project that is work in progress.
C++26 chess engine.
Meltdown 1.7 - what's new in this version?
Test results (v1.7 vs v1.6)
Elo | 143.89 +- 10.59 (95%)
Conf | 8.0+0.08s Threads=1 Hash=128MB
Games | N: 3000 W: 1570 L: 394 D: 1036
Penta | [20, 155, 371, 537, 417]
https://openbench.bunny.beer/test/324/
Elo | 162.06 +- 10.25 (95%)
Conf | 40.0+0.40s Threads=1 Hash=128MB
Games | N: 3000 W: 1591 L: 285 D: 1124
Penta | [14, 95, 392, 569, 430]
https://openbench.bunny.beer/test/326/
Elo | 166.41 +- 10.50 (95%)
Conf | 5.0+0.05s Threads=4 Hash=64MB
Games | N: 3004 W: 1641 L: 303 D: 1060
Penta | [20, 88, 377, 568, 449]
https://openbench.bunny.beer/test/327/
syzygy 5man
Elo | 52.09 +- 7.17 (95%)
Conf | 8.0+0.08s Threads=2 Hash=64MB
Games | N: 3004 W: 934 L: 487 D: 1583
Penta | [14, 189, 721, 492, 86]
https://openbench.bunny.beer/test/328/
What's Changed
refactor: update folder structure and naming by @hansbinderup in #114
terms: add king zone by @hansbinderup in #115
static_evaluation: clean up material scoring by @hansbinderup in #116
terms: add piece attacked term by @hansbinderup in #117
terms: add un/safe checks terms by @hansbinderup in #120
readme: remove deprecated information and add ccrl link by @hansbinderup in #121
searcher: improve when stopped | fix syzygy threading bug | fix shutdown memory issue by @hansbinderup in #119
searcher: add qsearch tt alpha move write by @hansbinderup in #122
docker: Add clang to Dockerfile by @clarashepherd in #83
meson: compile static linux binaries by @hansbinderup in #118
searcher: create SearchTable, clean up picker state by @clarashepherd in #124
terms: add pawn push threat by @hansbinderup in #125
searcher: clean up PVS by @hansbinderup in #126
move_picker: add counter moves term by @clarashepherd in #127
searcher: add cut node by @hansbinderup in #129
searcher: add internal iterative reduction by @hansbinderup in #130
build: only allow cache for dev builds by @hansbinderup in #128
move_gen: improve capture generation | improve attack_gen by @hansbinderup in #131
Comments
Post a Comment