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

Need pytorch nightly? #5

Closed
agaldran opened this issue Jul 17, 2019 · 4 comments
Closed

Need pytorch nightly? #5

agaldran opened this issue Jul 17, 2019 · 4 comments

Comments

@agaldran
Copy link

agaldran commented Jul 17, 2019

Hi!
Thank you for making the Wasserstein loss extension available. Forgive me if this isn't an issue, I am not an expert user. I just wanted to comment that when I tried to run the extension in my computer (torch 1.1.0) I was getting this error in compilation time:

error: identifier "TORCH_CHECK" is undefined

After installing the latest pytorch-nightly everything seems to run smoothly, so I guess this may be a requirement?

@t-vi
Copy link
Owner

t-vi commented Jul 17, 2019

Thanks for raising this! I guess

#ifndef TORCH_CHECK
#define TORCH_CHECK AT_CHECK
#endif

would be a good idea, because that indeed changed after 1.1.

@Yozey
Copy link

Yozey commented Jul 19, 2019

Hello @t-vi ,

Thank you for sharing your awesome code for the Wassertein distance.

Could you please precise your CUDA version, pytorch version and CuDNN version please? I encountered 4 errors when I was compling the CUDA code and I suspected that it is due to the complier version.

  1. error: static assertion failed with "ArgumentInfo is to be a POD struct"
  2. error: no suitable constructor exists to convert from "c10::ScalarType" to "at::Type"
  3. error: identifier "__shfl_xor" is undefined
  4. error: identifier "TORCH_CHECK" is undefined (solved by your previous response)

I'm using CUDA8.0, CuDNN 7.1.1 and PyTorch 1.0.0.

@t-vi
Copy link
Owner

t-vi commented Jul 19, 2019

You need PyTorch 1.1 and the above hotfix or PyTorch nightlies. CuDNN should not matter at all, CUDA8 probably works.

@t-vi
Copy link
Owner

t-vi commented Feb 18, 2021

This is now all well with contemporary versions of PyTorch, so I'm closing it.

@t-vi t-vi closed this as completed Feb 18, 2021
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

3 participants