Skip to content
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

In some cases odeint works on GPU but fails on CPU #19

Closed
talesa opened this issue Jan 10, 2019 · 2 comments
Closed

In some cases odeint works on GPU but fails on CPU #19

talesa opened this issue Jan 10, 2019 · 2 comments

Comments

@talesa
Copy link
Contributor

talesa commented Jan 10, 2019

Hi!
I've came across an example that runs on the GPU but doesn't run on the CPU.
The cause seems to be x.norm() returning a nan when on CPU and a correct result on a GPU.
(https://github.com/rtqichen/torchdiffeq/blob/master/torchdiffeq/_impl/misc.py#L74)
This is happening when setting initial step at
https://github.com/rtqichen/torchdiffeq/blob/master/torchdiffeq/_impl/misc.py#L126

Don't have time to follow through on this at the moment, leaving it here for now.

@talesa talesa changed the title Works on GPU failure on CPU In some cases odeint works on GPU but fails on CPU Jan 11, 2019
@programmin1
Copy link

How did you set it to use GPU or CPU?

@mancunian1792
Copy link

I guess the adjoint method doesn't support GPU. odeint_adjoint is referred as odeint in the mnist example if you set the adjoint parameter to be true.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants