You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the position black is worse but can still defend for many moves, yet the moved played allowed white to instantly mate.
This might not be a problem with terminal nodes, it might be related to the cpuct part of the global weights, with that turned on, I have seen it make a totally random move, which perhaps can happen when some bad move gets just enough policy boost to get a instant increase in global weight. If that happens just before it is time to move, then things the move selection get almost random. Perhaps we need some guard against that kind of instability (or just turn down the cpuct coeff a bit).
The text was updated successfully, but these errors were encountered:
I saw a new instance of this with rev 7f9e20e, which is very recent: 29 april, so the problem is not solved, and NN 32603 (a classic NN, I use for testing all the time).
Does not avoid being mated.
position startpos moves e2e4 e7e5 g1f3 b8c6 f1b5 a7a6 b5a4 g8f6 e1g1 f8e7 f1e1 b7b5 a4b3 d7d6 c2c3 e8g8 h2h3 c8b7 d2d4 f8e8 b1d2 e7f8 a2a4 c6a5 b3c2 e5d4 c3d4 b5b4 b2b3 g7g6 c1b2 f8g7 a1b1 f6d7 h3h4 a8c8 f3g5 g7f6 d2f3 f6g7 e4e5 d7f8 d1d2 b7f3 g5f3 c7c5 d4d5 d6e5 b2e5 g7e5 f3e5 f8d7 e5d7 d8d7 h4h5 d7d6 d2d3 g8f8 h5h6 c8c7 e1e8 f8e8 b1e1 e8d8 c2d1 c7a7 e1e3 a7e7 e3e7 d8e7 d1e2 f7f5 g2g3 e7d7 e2f3 d6b6 d3e3 b6d6 f3g2 d6e7 e3d3 e7f6 g2f3 f6b6 g3g4 b6f6 g1f1 f6a1 f1g2 a1f6 f3d1 f5g4 d3g3 f6d6 d1g4 d7c7 g3f3 c5c4 f3f7 c7b6 f7h7 c4c3 h7g8 c3c2 h6h7 c2c1q h7h8q a5b3 g8b8 d6b8 h8b8 b6a5 b8d8 a5a4 d5d6 c1f4 g4d1 f4d4 d8e8 a4a3 d6d7 d4d1 d7d8q d1g4 g2h2 b3d4 e8e3 d4b3 d8b6 a6a5 b6e6 g4d1 h2g3 a5a4 e6e5
In the position black is worse but can still defend for many moves, yet the moved played allowed white to instantly mate.
This might not be a problem with terminal nodes, it might be related to the cpuct part of the global weights, with that turned on, I have seen it make a totally random move, which perhaps can happen when some bad move gets just enough policy boost to get a instant increase in global weight. If that happens just before it is time to move, then things the move selection get almost random. Perhaps we need some guard against that kind of instability (or just turn down the cpuct coeff a bit).
The text was updated successfully, but these errors were encountered: