Sunsetter missed m2 #2199
Comments
isaacl
added a commit
to isaacl/lila
that referenced
this issue
Sep 3, 2016
Improve sunsetter output and behavior, especially in positions close to mate. - fix eval sign in "analyze" mode, which is used after sunsetter plays a forced move - enter analyze mode if sunsetter quickly picks an obvious move without fully evaluating. For example, if alternatives allow mate in 1, sunsetter might move with only depth 1 evaluation, giving the best move but an incorrect eval score. - approximate depth when sunsetter finds mate but doesn't give a depth. Fixes lichess-org#2198 and lichess-org#2199.
Merged
isaacl
added a commit
to isaacl/lila
that referenced
this issue
Sep 3, 2016
Improve sunsetter output and behavior, especially in positions close to mate. - fix eval sign in "analyze" mode, which is used after sunsetter plays a forced move - enter analyze mode if sunsetter quickly picks an obvious move without fully evaluating. For example, if alternatives allow mate in 1, sunsetter might move with only depth 1 evaluation, giving the best move but an incorrect eval score. - approximate depth when sunsetter finds mate but doesn't give a depth. Fixes lichess-org#2198 and lichess-org#2199.
ornicar
added a commit
that referenced
this issue
Sep 20, 2016
* 'master' of github.com:ornicar/lila: Upgrade to Sunsetter8 (fixes #2199)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For FEN
lichess reports -7.3. Sunsetter found m3 the previous move, but now can't find m2. Sunsetter output:
@niklasf
The text was updated successfully, but these errors were encountered: