You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've encountered an issue where cufinufft.nufft3d1 outputs wildly incorrect results for very specific inputs and only on certain GPUs. This can be reproduced by running the following code on an A100 GPU:
Here's an archive with points.pt and values.pt: inputs.zip
The value is many orders of magnitude greater than it should be. It also grows quickly with decreasing eps.
Notes:
We reproduced this both for cufinufft 2.2.0 and 2.3.0.
Reproduced on A100, but not on A10G. We haven't tried other GPUs.
The "blow-up" happens for specific grid sizes: from 61 to 64, while for 60, 65 and beyond it goes back to normal. This is for float32 inputs; for float64, we saw a "blow-up" for grid size 32.
We compiled cufinufft from sources to investigate further, but surprisingly couldn't reproduce the bug. We've tried compiling from master and v2.3.X as well as various compilation options. If you could point us to the compilation options with which the release version of libcufinufft.so is built, that would be helpful, and we can investigate further!
The text was updated successfully, but these errors were encountered:
We've encountered an issue where
cufinufft.nufft3d1
outputs wildly incorrect results for very specific inputs and only on certain GPUs. This can be reproduced by running the following code on an A100 GPU:Here's an archive with
points.pt
andvalues.pt
: inputs.zipThe value is many orders of magnitude greater than it should be. It also grows quickly with decreasing
eps
.Notes:
libcufinufft.so
is built, that would be helpful, and we can investigate further!The text was updated successfully, but these errors were encountered: