-
Notifications
You must be signed in to change notification settings - Fork 9
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
LLVM error on CPU #149
Comments
Hi @Asif-Iqbal-Bhatti, thanks for giving A few questions:
To find the import mat_discover
mat_discover.__version__ Btw, I checked the main Colab notebook, and it had installation issues with installing the latest release. It seems Colab has updated to Python 3.10, and Do you mind trying to run it with your data in the linked Colab notebook? This will help me to debug the LLVM error that you're getting. Lmk if you need any help. |
I am using WSL ubuntu in windows 10 Okay, I will try that in notebook |
Thanks! Also, I just recently saved a new version of the notebook. Please make sure you're using the latest version of it (I was testing things out and didn't expect such a quick reply 😅) |
Also, if you try it on your machine again, I recommend following the pip installation instructions in a fresh conda environment. I had trouble updating the conda package, but hopefully that should be resolved in ~30 minutes, assuming https://github.com/sparks-baird/mat_discover/actions/runs/5310831719 is successful. Whatever the install method, you can double-check by making sure that you're using |
@Asif-Iqbal-Bhatti were you able to get this figured out? Any updates? |
Related to sparks-baird/CrabNet#70 Maybe related to #149
Hello @sgbaird so I tried running on Google Colab and there was no error but when I run on my local WSL ubuntu machine it gives this LLVM error. I tried many way as you suggested but still I could not ignore that. I think some library linkage is not set for running mat_discover on cpu. |
Hi @Asif-Iqbal-Bhatti, thanks for verifying the Google Colab script. This helps isolate the issue. I found a related issue numba/numba#6012. One of the quick-fix suggestions is to pin pip install numba<0.50 Can you give this a try and lmk? |
Is it possible to try this with Numba 0.57 (if that wasn't already the version in use)? The llvmlite / LLVM versions with Numba 0.57 are quite different to those with earlier versions (14 vs 11, and a change to avoid generating some inappropriate library calls) so I'm wondering if the problem is resolved in the latest version already. |
Hallo @sgbaird, so I tried now and it is working perfectly. Thanks for pointing out. Numba was causing de probleem. Dank u. |
I have so it works with this version. |
@Asif-Iqbal-Bhatti glad to hear it! Lmk if you need help with anything else |
Ok, I'll give this a look. Thanks! |
@Asif-Iqbal-Bhatti updating jaxlib seemed to fix it. I need to look into a more permanent fix #155. I think this is from adding m3gnet as a dependency #154. This should be working now: https://colab.research.google.com/drive/1MgV_ZewS6gLm1a3Vyhg33pFHi5uTld_2?usp=sharing |
@Asif-Iqbal-Bhatti were you able to resolve this? |
Hello,
After running the and training on my data set I keep on getting this error on my machine:
I don't have cuda. I am only using cpu version. I checked on Google but could not find a solution.
If you know how to resolve let me know. Thanks.
The text was updated successfully, but these errors were encountered: