Igel 3.4.0 at
https://github.com/vshcherbyna/igel/releases/tag/3.4.0 (official executable binaries for Windows and IGN-3 net).
Hello there,
I am really sorry to disrupt the testing community having released Igel 3.3.0 just 2 weeks ago, but ... When debugging some unrelated issue I discovered a
really serious bug in Igel's handling of nnue accumulator for null moves. This bug is present since August 2020 and results in Igel having wrong evaluations which is especially noticible in long time control in early and mid games when nnue eval is dominant compared to lazy (HCE) eval.
When the fix was applied to master branch (Igel 3.3.0) I saw a
massive ~25 elo increase at LTC:
http://chess.grantnet.us/test/31014/.
When I applied this fix to my dev version (upcoming Igel 3.4.0) which features fully NNUE eval I saw
huge elo gains ranging from 75 to 90 elo in LTC against Igel 3.3.0:
http://chess.grantnet.us/test/31024/
I obviously see a valid reason to interrupt my dev cycle and release whatever Igel state I currently have even though it may not feature the strongest Igel network released in 3.4.0 (HalfKav2_hm).
Disclaimer: Keep in mind that these are indicative numbers and elo gain against other engines may vary.
Igel 3.4.0 is yet another milestone in Igel's development as I removed all HCE code and the eval is purely NNUE.
What's new:
- fixing major bug in accumulator handling for null moves
- avoid heap objects (std::vector) in search function to reduce heap fragementation
- switching to pure nnue evaluation
- new network architecture HalfKav2_hm
- new network ign-3-debc71a4
Regression run against Igel 3.3.0 on Long Time Control (60+0.6)
Code: Select all
ELO | 75.10 +- 5.38 (95%)
CONF | 60.0+0.60s Threads=1 Hash=64MB
GAMES | N: 8480 W: 3133 L: 1328 D: 4019
In case of any questions please ask them in the main thread for Igel at
https://talkchess.com/forum3/viewtopic. ... 76#p942376