-
Notifications
You must be signed in to change notification settings - Fork 114
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
A problem about nms #2
Comments
what GPU do you have? I think you might have to change the compilation flags; I hardcoded them for my Titan X setup. |
Thanks for your kind answering. |
Yeah, you'll need to change the LSTM compilation: https://github.com/rowanz/neural-motifs/blob/master/lib/lstm/highway_lstm_cuda/make.sh I believe that should be everything. Also, have you verified that pytorch usually runs on your machine? |
I use pytorch 0.3.1. Now I can run your code, thank you! |
Hi, I've met the same problem using Tesla P100. So did you solve your problem only changing from _61 to _60 in 3 files (nms, roi_align and highway_lstm_cuda)? |
For those who are still solving this issues, here are the steps you should consider to follow:
That's all you need to do to change your faulty SM setup to the correct one. |
Hi Rowan, thanks for your codes sharing. However, I find
nms.nms_apply(keep, boxes_sorted, nms_thresh)
in lib/fpn/nms/functions/nms.py would make pytorch break up. Before I execute that line, the operation ofTensor.cuda()+int()
is legal, but after I execute that line this operation will raise error:RuntimeError: cuda runtime error (48) : no kernel image is available for execution on the device at /pytorch/torch/lib/THC/generic/THCTensorMathPairwise.cu:21
when it goes onkeep_im + s
at line 24. Could you please help me? Thanks!The text was updated successfully, but these errors were encountered: