Sabaki github6/13/2023 From the error message, the issue apparently is that KataGo does not manage to find the net, so that's what you should check first Is the file (g170-b15c192.) in the "C:\users\david\etc" folder? If not, that would explain the problem. There surely can't be a permission problem with Katago, since LZ works just fine from a neighbouring folder?Īny advice to this real beginner would be very much appreciated! I've also tried more or less every single one of the other ways of connecting the model suggested on the beginner's Github pages, but to no avail either. Maybe that's because the network model couldn't be accessed and the whole benchmarking routine aborted? No config file was generated - or at least not visible in the Katago folder. It's the second line which accesses the network model, which is my issue.Īnyway, here's what happened when I ran the custom benchmarking command: see attached. I think the first line which identifies the simple path to katago.exe is okay. My machine is MS Surface Book 3 running Windows 10. I've successfully installed Leela Zero on Sabaki, but keep coming up against the same issue trying unsuccessfully to hook up the Katago engine. If you would like to see a donation link for the application here, please include one in the AppStream data.Forgive what is possibly an embarrassingly naive beginner's question (which is what I am: not a code geek at all, just an overambitious go player!) You can specify the URL to a nicer one by shipping an AppStream metainfo file. The screenshot for sabaki has been automatically taken during a fully automated test. There is an online tool that makes it easy to make one. Improve this entry by shipping an AppStream metainfo file inside the AppImage in the usr/share/metainfo directory. Tools like appimagetool and linuxdeployqt can do this for you easily. zsync file so that it can be updated using AppImageUpdate. Please consider to add update information to the sabaki AppImage and ship a. Pro Tips for further enhancing the sabaki AppImage Great! Here are some ideas on how to make it even better. Thanks for distributing sabaki in the AppImage format for all common Linux distributions. If you would like to have the executable bit set automatically, and would like to see sabaki and other AppImages integrated into the system (menus, icons, file type associations, etc.), then you may want to check the optional appimaged daemon. If you would like to update to a new version, simply download the new sabaki AppImage. This is entirely optional and currently needs to be configured by the user. If you want to restrict what sabaki can do on your system, you can run the AppImage in a sandbox like Firejail. Then double-click the AppImage in the file manager to open it. Use at your own risk!ĭownload the sabaki AppImage and make it executable using your file manager or by entering the following commands in a terminal: Follow these instructions only if you trust the developer of the software. This is a Linux security feature.īehold! AppImages are usually not verified by others. However, they need to be marked as executable before they can be run. Unlike other applications, AppImages do not need to be installed before they can be used. Running sabaki on Linux without installation Most AppImages run on recent versions of Arch Linux, CentOS, Debian, Fedora, openSUSE, Red Hat, Ubuntu, and other common desktop distributions. No system libraries or system preferences are altered. Download an application, make it executable, and run! No need to install. Awesome!ĪppImages are single-file applications that run on most Linux distributions. Sabaki is available as an AppImage which means "one app = one file", which you can download and run on your Linux system while you don't need a package manager and nothing gets changed in your system. An elegant Go/Baduk/Weiqi board and SGF editor for a more civilized age.
0 Comments
Leave a Reply. |