Closed domino14 closed 1 year ago
this happens in prod sometimes, but since the lambda panics it succeeds on one of the 3 retries afterwards
This only seems to happen in multi-threaded mode.
very likely seems to just be the transposition table lookup succeeding on the first try and the PV doesn't get updated.
https://github.com/domino14/macondo/blob/master/endgame/negamax/solver.go#L551-L569
other threads can update the TT before the main thread does (since the other threads can look a level or two deeper and thus ttEntry.depth() >= uint8(depth)
can be true. The negamax function would return immediately with the score but not the PV.
we already know the PV gets swallowed up partially, but with one tile left and lazysmp on, sometimes sequences get swallowed up:
Note the final sequence is empty, and so is the sequence after 4 plies (although the spread is still correct).