Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Berserk stops search mid-pondering #348

Closed
jhonnold opened this issue Apr 8, 2022 · 1 comment
Closed

Berserk stops search mid-pondering #348

jhonnold opened this issue Apr 8, 2022 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@jhonnold
Copy link
Owner

jhonnold commented Apr 8, 2022

When a search is started using with the keyword "ponder", Berserk should continue to search indefinitely as long as the opponent is still "thinking". Recent TM changes prior to Berserk 8.5.1 did not consider "ponder", resulting in Berserk not thinking as long as it should.

Example output of Berserk stopping at depth 11 when pondering the startpos

❯ ./berserk                                                                                                                                                           berserk/src -> main $
setoption name Ponder value true
info string set Ponder to value true
go ponder wtime 1000 btime 1000 winc 0 binc 0
info string time 1000 start 1649432003254 alloc 35 max 192 depth 99 timeset 1 searchmoves 0
info depth 1 seldepth 0 multipv 1 score cp 18 nodes 3 nps 3000 hashfull 0 tbhits 0 time 0 pv a2a3
info depth 2 seldepth 1 multipv 1 score cp 78 nodes 14 nps 14000 hashfull 0 tbhits 0 time 0 pv g1f3 a7a6
info depth 3 seldepth 2 multipv 1 score cp 18 nodes 47 nps 47000 hashfull 0 tbhits 0 time 1 pv g1f3 g8f6 a2a3
info depth 4 seldepth 3 multipv 1 score cp 70 nodes 127 nps 127000 hashfull 0 tbhits 0 time 1 pv e2e4 b8c6 b1c3 g8f6
info depth 5 seldepth 4 multipv 1 score cp 55 nodes 361 nps 361000 hashfull 0 tbhits 0 time 1 pv g1f3 g8f6 b1c3 b8c6 e2e4
info depth 6 seldepth 5 multipv 1 score cp 67 nodes 1101 nps 367000 hashfull 1 tbhits 0 time 3 pv e2e4
info depth 7 seldepth 6 multipv 1 score cp 54 nodes 1481 nps 370250 hashfull 1 tbhits 0 time 4 pv e2e4 c7c5 g1f3 b8c6 b1c3 g8f6 e4e5
info depth 8 seldepth 8 multipv 1 score cp 58 nodes 2095 nps 419000 hashfull 1 tbhits 0 time 5 pv e2e4 c7c5 g1f3 e7e6 b1c3 b8c6 d2d4 c5d4
info depth 9 seldepth 13 multipv 1 score cp 64 nodes 4855 nps 485500 hashfull 4 tbhits 0 time 10 pv e2e4 e7e5 g1f3 b8c6 d2d4 e5d4 f3d4 d8f6 c2c3 f8c5
info depth 10 seldepth 13 multipv 1 score cp 58 nodes 7696 nps 513066 hashfull 4 tbhits 0 time 15 pv e2e4 e7e5 g1f3 b8c6 f1b5 g8f6 b1c3 c6d4 f3e5 d4b5
info depth 11 seldepth 13 multipv 1 score cp 63 nodes 16135 nps 597592 hashfull 7 tbhits 0 time 27 pv e2e4 c7c5 g1f3 b8c6 b1c3 e7e6 f1b5 d7d5 e4d5 e6d5 e1g1 g8f6
@jhonnold jhonnold added the bug Something isn't working label Apr 8, 2022
@jhonnold jhonnold self-assigned this Apr 8, 2022
@jhonnold
Copy link
Owner Author

jhonnold commented Apr 8, 2022

This issue is related to this comment in issue #282.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant