Closed BenjaminMichaelis closed 1 year ago
Yeah, it is not an issue with GpuOwl, but with OpenCL on Colab, which unfortunately is currently broken. See #18 for more information.
In the meantime, I would suggest temporally using the previous version of our GPU notebook, which uses CUDALucas. See the note I recently added near the top of our Colab README: https://github.com/tdulcet/Distributed-Computing-Scripts/blob/eac3911950422ffa26ce50477904b2d7d074cf3d/google-colab/README.md?plain=1#L10
I am glad to hear that our CPU notebook is working for you.
\CC @Danc2050
Yeah, it is not an issue with GpuOwl, but with OpenCL on Colab, which unfortunately is currently broken. See #18 for more information.
In the meantime, I would suggest temporally using the previous version of our GPU notebook, which uses CUDALucas. See the note I recently added near the top of our Colab README:
I am glad to hear that our CPU notebook is working for you.
\CC @Danc2050
Ah thank you! This explains it, I must of missed that issue.
I can close the issue now unless you want me to keep it open for visibility
No problem. I will fix the syntax of that note in my next commit, so that it shows up more prominently on the Colab README.
Hopefully Nvidia and/or Colab will fix this OpenCL issue soon...
I seem to have trouble running the gpu script on colab, seems like maybe an upstream issue in gpuowl (a similar issue is here: https://github.com/preda/gpuowl/issues/223 ). The CPU script works great in the meantime! Any suggestions?