I again return to the development of my engine. At the moment, I am also developing my platform for distributed engine testing in parallel, which will be available later. This platform allowed me to automate the testing process.
Changes
- Improvements in king safety;
- Fix queen mobility eval;
- Incremental eval for simple part: material and PSQ-tables;
- Minor speed-up changes.
STC:
Code: Select all
tc=10+0.6 Threads=1 Hash=256
Games: 4448/20000 W: 1466 L: 1133 D: 1849
ELO: 26.06 +- 7.80 (95%) LOS: 100.00%LTC:
Code: Select all
tc=60+0.6 Threads=1 Hash=256
Games: 724/3000 W: 236 L: 152 D: 336
ELO: 40.49 +- 18.53 (95%) LOS: 100.00%------------
Also, I am currently developing my own distributed engine testing system (such as FishTest/OpenBench). I wanted to make it for ease of testing and for self-development. What are its features - the data is updated in real time via the socket, and the interface adjusts to the display (smooth color change in SPRT tests + display of a progress bar in Elo tests). I wrote on React (front-end), NestJS (back-end), and a client wrote on a clean Node.js that launches games through cutechess-cli. I plan to open source in the coming months when it gets better. Also, I have an idea to make distributed tournaments possible - a tournament is created and played on different PCs. Real-time data is sent to the server. In this case, the time control adjusts to the hardware. Games are played in parallel. This is just an idea for further development.
I hope you will like it!
