-
Notifications
You must be signed in to change notification settings - Fork 11
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
SAI periodically disconnects in sabaki #123
Comments
has anyone come across this? maybe the problem is sabaki? |
launched in q5go - same problem. 0.17.5 works, 0.17.6 not. and if I want to play against sai, the same. does this problem exist? or am I doing something wrong? |
@cryptpark can you give more information? For example command line in Sabaki for example? |
Yes of course! now did it again: Sabaki 0.51.1, sai-0.17.6-gpu, networkfile a8e32bb8, --gtp --noponder -w networkfile.gz Thinking at most 36.3 seconds... Q17 -> 112 (V: 52.29%) (LCB: 51.81%) (N: 5.74%) (A: -0.7) (B: 0.13) PV: Q17 R4 D4 Q16 R16 R15 R17 O4 Root -> 1157 (V: 51.79%) (LCB: 51.54%) (N: 0.00%) (A: -0.6) (B: 0.13) 6.2 average depth, 15 max depth and that is all! nothing on the board! sometimes after several moves, sometimes, like now - after the first. |
Uhm, I tried to reproduce your bug, without success. I don't suppose you are using a peculiar gpu or gpu driver? Because it is known that some OpenCL drivers can be broken and this sort of things could happen. |
sai-0.17.6-cpu doesn't work either (the same way). I noticed that the last attempts didn't even have one move. I'll try to find out why there were sometimes several moves before. |
I added "-t 2" and sai-0.17.6-gpu, network 12b works now. interesting to see your comment. |
Wow. This is interesting and I don't think I have ever seen this problem anywhere else. |
I disabled CPU virtualization, it gave nothing. and today, at "-t 3", the stop at move 74. there is little information in the sabaki log file. can I get a more detailed log somehow? |
I closed all other applications and sai-0.17.6-gpu, network 20b work with "t-5". but without parameter "t-" it still doesn't work. in general, nothing is clear :) |
with the parameter "-t 3" sai-0.17.6-gpu is reasonably stable (~ 50%). does this parameter affect strength or playstyle? |
It is an optimization parameter. To get the most "nodes" per second (and hence the less seconds per move) you have to find the optimal value, which will be generally depend on your hardware configuration. Actually, changing this number will also change a bit the playing style, as the tree exploration will change. The difference should be small though. |
AMD Athlon X4 950, GF GT610, 8GB RAM, Windows 7. ok? |
you previously wrote "info move does not appear means that the search has crashed." in the sabaki log file I found this: [2020-09-08 15:03:05.161] sai (in) : play B D8 here: (I clicked "start engine vs engine game", the game resumed) [2020-09-08 15:03:19.758] (in) : undo |
it's still very interesting to find the cause of the failure! I ran it in SmartGo, and so far everything is fine! (sai-0.17.6-gpu, --gtp --noponder -w networkfile.gz, network 20b 7fa70321, game over, 242 moves) I want to check, make a match of several dozen games |
SmartGo does not have a separate line like Sabaki for time_settings. (eg time_settings 0 6 1) how to do it? |
I am at a loss. Glad to hear that at least with smartgo SAI seems to work fine. Will think about this further. |
works with drago too! works with sabaki 0.33.4. "incompatibility" probably arose with the latest versions of sabaki. in about an hour I will search starting from which version of sabaki the crash occurs |
works with sabaki 0.33.4, 0.35.1, 0.40.0, 0.40.1. Further 0.41.0, 0.43.3 doesn't work. does it tell you anything? |
I didn't expect this, but it works on the old version q5go-1.1-win! maybe there is a simple explanation for this? |
even "-t 1" does not help in version 0.18.1. stops after a few moves, often does not even make 1 move. with sai network and lz network |
Try version 0.18.2. We reverted from a shared mutex update that might make the problem worse. |
I tried cpu and gpu. now I will check sai-0.18.2-gpu. but it works with drago! |
I was not expecting!!! sai-0.18.2-gpu works! I will check again |
worked with sai network without stopping until the end of the game. for some reason the problem with the lz network remains |
sai-0.18.2-cpu does not work with the networks sai and lz |
again launched sai-0.18.2-gpu with lz network - now it works. |
0.17.5 works without problems. but 0.17.6 when playing against lz periodically stops and you have to start the match further
The text was updated successfully, but these errors were encountered: