Crem and the Lc0 developers have been nothing but awesome about the introduction and development of Allie. Indeed, crem was kindly answering questions about the Lc0 backend and how it works when I started to create Allie.
As I said, Allie would not be possible without the Lc0 project and developer team. That said, it is original and different than Lc0 (which can be plainly seen in that it is weaker than Lc0 currently given the same network
The plan is to make Allie even more different in the future with regards to the search. Although I have not released it, the patch to switch to pure AlphaBeta search exists and plays decent chess although it is weaker (currently) than the mcts search. In fact, if I had not entered or released Allie yet it would probably be much further along, but I have been spending my time making Allie scale.
All this is to say that there exists little to no contentiousness here and I see no reason to introduce it.
velmarin wrote: ↑Thu Mar 07, 2019 3:06 am
I am unfamiliar with QT, I get this error when I try it on Windows.
A link is appreciated if someone has got it.
I have been making an appveyor.yml script for building on windows, but it still doesn't quite work for reasons I don't understand. If I do roughly the same thing on my own windows 10 vmware instance it works. Anyway, here is the appveyor.yml that should give you an idea about how to compile this for Windows.
If anyone would like to help me bugfix the script I will hook it up so that Windows executables are automatically generated when I release a new version of Allie in the future.
In the meantime, @borg has also been working on an appveyor.yml that produced the executable, but it is dynamically linked so you'll have to get ahold of Qt dlls for it to work. You can find that here: https://ci.appveyor.com/project/borg323/allie/history
Steppenwolf, to close out the thread... I have been doing opensource development for quite a long time and I've never published pre-built executables for any of my hobby projects. I dare say that the vast, vast, vast majority of open source projects on github are the same way. I hope you will understand that there was no maliciousness in my failure to do so for this project either. Anyway, like I said, it will be rectified shortly hopefully.
velmarin wrote: ↑Thu Mar 07, 2019 3:06 am
I am unfamiliar with QT, I get this error when I try it on Windows.
A link is appreciated if someone has got it.
I have been making an appveyor.yml script for building on windows, but it still doesn't quite work for reasons I don't understand. If I do roughly the same thing on my own windows 10 vmware instance it works. Anyway, here is the appveyor.yml that should give you an idea about how to compile this for Windows.
If anyone would like to help me bugfix the script I will hook it up so that Windows executables are automatically generated when I release a new version of Allie in the future.
In the meantime, @borg has also been working on an appveyor.yml that produced the executable, but it is dynamically linked so you'll have to get ahold of Qt dlls for it to work. You can find that here: https://ci.appveyor.com/project/borg323/allie/history
Program needs some exotic dlls before it will run cudart64_100.dll........any ideas? Thx AR
velmarin wrote: ↑Thu Mar 07, 2019 3:06 am
I am unfamiliar with QT, I get this error when I try it on Windows.
A link is appreciated if someone has got it.
I have been making an appveyor.yml script for building on windows, but it still doesn't quite work for reasons I don't understand. If I do roughly the same thing on my own windows 10 vmware instance it works. Anyway, here is the appveyor.yml that should give you an idea about how to compile this for Windows.
If anyone would like to help me bugfix the script I will hook it up so that Windows executables are automatically generated when I release a new version of Allie in the future.
In the meantime, @borg has also been working on an appveyor.yml that produced the executable, but it is dynamically linked so you'll have to get ahold of Qt dlls for it to work. You can find that here: https://ci.appveyor.com/project/borg323/allie/history
Program needs some exotic dlls before it will run cudart64_100.dll........any ideas? Thx AR
unless you can find that lone dll, you need to download several gbytes of cuda 10 or 10.1, which requires that you sign up to nvidia developers with a password of at least eight chars, mixed upper lower case numerical bla bla, and install it. Quite possibly you also need to have downloaded cuda development toolkit beforehand as well.
velmarin wrote: ↑Thu Mar 07, 2019 3:06 am
I am unfamiliar with QT, I get this error when I try it on Windows.
A link is appreciated if someone has got it.
I have been making an appveyor.yml script for building on windows, but it still doesn't quite work for reasons I don't understand. If I do roughly the same thing on my own windows 10 vmware instance it works. Anyway, here is the appveyor.yml that should give you an idea about how to compile this for Windows.
If anyone would like to help me bugfix the script I will hook it up so that Windows executables are automatically generated when I release a new version of Allie in the future.
In the meantime, @borg has also been working on an appveyor.yml that produced the executable, but it is dynamically linked so you'll have to get ahold of Qt dlls for it to work. You can find that here: https://ci.appveyor.com/project/borg323/allie/history
Program needs some exotic dlls before it will run cudart64_100.dll........any ideas? Thx AR 8-)
unless you can find that lone dll, you need to download several gbytes of cuda 10 or 10.1, which requires that you sign up to nvidia developers with a password of at least eight chars, mixed upper lower case numerical bla bla, and install it. Quite possibly you also need to have downloaded cuda development toolkit beforehand as well.
The cuda dlls are delivered with each LC0 download since several months at least. He will also need the appropriate qt5core.dll.
But all of this is invain anyway, because he has no available cuda hardware (can be deducted from earlier posts of him).
velmarin wrote: ↑Thu Mar 07, 2019 3:06 am
I am unfamiliar with QT, I get this error when I try it on Windows.
A link is appreciated if someone has got it.
I have been making an appveyor.yml script for building on windows, but it still doesn't quite work for reasons I don't understand. If I do roughly the same thing on my own windows 10 vmware instance it works. Anyway, here is the appveyor.yml that should give you an idea about how to compile this for Windows.
If anyone would like to help me bugfix the script I will hook it up so that Windows executables are automatically generated when I release a new version of Allie in the future.
In the meantime, @borg has also been working on an appveyor.yml that produced the executable, but it is dynamically linked so you'll have to get ahold of Qt dlls for it to work. You can find that here: https://ci.appveyor.com/project/borg323/allie/history
Program needs some exotic dlls before it will run cudart64_100.dll........any ideas? Thx AR
unless you can find that lone dll, you need to download several gbytes of cuda 10 or 10.1, which requires that you sign up to nvidia developers with a password of at least eight chars, mixed upper lower case numerical bla bla, and install it. Quite possibly you also need to have downloaded cuda development toolkit beforehand as well.
The cuda dlls are delivered with each LC0 download since several months at least. He will also need the appropriate qt5core.dll.
But all of this is invain anyway, because he has no available cuda hardware (can be deducted from earlier posts of him).
It depends. It used to be that one had to go through hoops to get the dll’s, because nvidia only distributed them via the password developer download. Then Crem or someone persuaded nvidia to allow the dll’s to be distributed along with lczero. That was with cuda 9.
But, if developers have upgraded to tensorflow13 plus, they then need to cuda10 toolkit download and a cuda 10 download to get at another nvidia dll, the 100.dll named above.
I don’t think (not sure) and am being too lazy to go look, that lczero requires cuda 10, and therefore only comes with the 9-series dlls.
If other developers have compiled with 10 series, then their user products will likely require 10 series nvidia support stuff. which probably “other” developers haven’t yet organised as a free distribution. Guessing a bit here.
Guenther wrote: ↑Sat Mar 09, 2019 11:49 am
The cuda dlls are delivered with each LC0 download since several months at least. He will also need the appropriate qt5core.dll.
But all of this is invain anyway, because he has no available cuda hardware (can be deducted from earlier posts of him).
It depends. It used to be that one had to go through hoops to get the dll’s, because nvidia only distributed them via the password developer download. Then Crem or someone persuaded nvidia to allow the dll’s to be distributed along with lczero. That was with cuda 9.
But, if developers have upgraded to tensorflow13 plus, they then need to cuda10 toolkit download and a cuda 10 download to get at another nvidia dll, the 100.dll named above.
I don’t think (not sure) and am being too lazy to go look, that lczero requires cuda 10, and therefore only comes with the 9-series dlls.
If other developers have compiled with 10 series, then their user products will likely require 10 series nvidia support stuff. which probably “other” developers haven’t yet organised as a free distribution. Guessing a bit here.
Since October 2018 the cuda 10 dlls are integrated in the LC0 download and already in September 2018 they were available as
separate download at the LC0 github site. No need for wrong guesswork. Cuda 10 is already 7 months old...
In the meantime, @borg has also been working on an appveyor.yml that produced the executable, but it is dynamically linked so you'll have to get ahold of Qt dlls for it to work. You can find that here: https://ci.appveyor.com/project/borg323/allie/history
...
Well, the last working compilation called 1.0.6 there issues illegal moves not only in the pv, but also while playing? Any idea?
The excerpt below is pasted from running it at cmd. I tried several nets, because I first thought it can't read older or newer nets,
but the result was always the same.
Guenther wrote: ↑Sat Mar 09, 2019 11:49 am
The cuda dlls are delivered with each LC0 download since several months at least. He will also need the appropriate qt5core.dll.
But all of this is invain anyway, because he has no available cuda hardware (can be deducted from earlier posts of him).
It depends. It used to be that one had to go through hoops to get the dll’s, because nvidia only distributed them via the password developer download. Then Crem or someone persuaded nvidia to allow the dll’s to be distributed along with lczero. That was with cuda 9.
But, if developers have upgraded to tensorflow13 plus, they then need to cuda10 toolkit download and a cuda 10 download to get at another nvidia dll, the 100.dll named above.
I don’t think (not sure) and am being too lazy to go look, that lczero requires cuda 10, and therefore only comes with the 9-series dlls.
If other developers have compiled with 10 series, then their user products will likely require 10 series nvidia support stuff. which probably “other” developers haven’t yet organised as a free distribution. Guessing a bit here.
Since October 2018 the cuda 10 dlls are integrated in the LC0 download and already in September 2018 they were available as
separate download at the LC0 github site. No need for wrong guesswork. Cuda 10 is already 7 months old...
So they are. took me two days and about ten retries downloading all of cuda10 to rural France, when I had the one file all along. Doh!
Guenther, almost certainly the problem you are seeing is because of a mismatch between the cuda libraries I built with and the ones you have installed. I built the binary with cuda 10.0. You can look at the appveyor.yml script which has the exact cuda files to download and install.
