-
Notifications
You must be signed in to change notification settings - Fork 46
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
bug: MNIST classification tutorial not running #165
Comments
Hi! Are you running the example on CPU or GPU? If on GPU, how many devices do you have available? |
I'm running it on 1 GPU! |
I'm not managing to replicate the issue. Could you write me exactly any changes you made while running the example? In the example, the probabilistic model is using a Laplace approximation for posterior inference. I guess you changed something to use SWAG instead? If no changes were made, I guess you are right and it must be some versioning issue. |
I'm running the notebook exactly as is! I also run into the same error in the calibration step for Laplace as well. Is there documentation I can refer to for the exact versions of of jax, flax, etc, that I should install? I installed fortuna using pip and python 3.10, but not sure what else I should look for. |
Hi Yucen, I eventually manage to replicate the issue - thanks a lot for raising this! I fixed the small bug and pushed to Pypi, so you should be able to get a working version by upgrading Fortuna with pip, i.e. Please, let me know if it works now! Although it may be no longer needed, to answer your question, you can find the main dependencies in pyproject.toml, and all dependencies in poetry.lock. In fact, if installation with pip creates problems in the future, you may also try installing the repo using poetry. |
It works for me now! Thank you so much. |
Bug Report
Fortuna version: v0.1.42
Current behavior: When I run the MNIST classification tutorial, I run into a broadcasting error. I think the issue occurs during the calibration step of training for SWAG.
Here's the traceback:
Is this due to a versioning issue? Thanks!
The text was updated successfully, but these errors were encountered: