-
Notifications
You must be signed in to change notification settings - Fork 86
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
'airsnal_run_pipeline' command fails to finish. #632
Comments
Hi @morialo3 , interesting - I haven't seen this before. I am guessing that Jax (which is used by numpyro in the points prediction) is somehow configured to try and use the GPU. I don't know why this would be, or if it might be possible (or even beneficial?) to run on the GPU, but a potential way to force it to use CPU could be to do something like:
in |
I patched |
Based on this my guess is this is something to do with multiprocessing and jax/GPUs not playing together nicely. I believe So We might just want to include the workaround to force jax to always use CPU by default in AIrsenal. |
Running
airsnal_run_pipeline
give an error when it reaches "point predictions":then the process just continues to just to stop and throw a trace without completing he task:
I'll attach the full result of
airsnal_run_pipeline
to this gist"https://gist.github.com/morialo3/cd7fde8e69027b69ac472427cf4986ee
The text was updated successfully, but these errors were encountered: