-
Notifications
You must be signed in to change notification settings - Fork 909
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
odenet_mnist seems stuck, doesn't finish overnight #26
Comments
This might be because you're running on CPU. Being extremely slow on CPU is expected, as training requires evaluating a neural net multiple times. Does ode-demo work? |
Yes, |
I also let the code run for ~12 hours and it managed to finish 13 epochs (I would assume an epoch/hour). Does it mean that I have to stick to less epochs (from the default 160 if I am not mistaken) since I don't have a GPU? Thanks in advance. |
Hmm.. I'd suggest using a GPU as running neural nets on CPU is way too slow. Colaboratory (https://colab.research.google.com/) lets you use a free GPU. You'll be able to install torchdiffeq with the following command:
|
Thank you for the suggestion. I find the Jupyter Notebook terrible for debugging. I tried running the ode_demo.py and odenet_mnist.py with GPU and I get : SystemExit: 2 and for odenet_mnist.py: SystemExit: 2 Could you tell me why you use 160 epochs (I know the more the better)? Thanks in advance! |
The idea is you can just copy the Python code instead of running it as a script. Yeah, you should be able to get the same accuracy with much fewer number of epochs. |
Thank you! |
When I run it it prints out:
and uses 100% cpu for hours - checking in morning and nothing seems to have happened.
It doesn't finish - Ctrl+C stops it at this point:
The text was updated successfully, but these errors were encountered: