-
Notifications
You must be signed in to change notification settings - Fork 10
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
Getting a "!!Error occurred: CUFFT plan creation failed" #27
Comments
How big is your image volume and how much GPU ram do you have available? |
My I have 80GB VRAM (running on A100). Thank you! |
oh ok, should definitely be more than sufficient. |
Thanks, @tlambert03. We can confirm that the test data is working ok. The problem might be with the data construction. I will talk to the data owners to see what we can share about the data reconstruction. Thank you! :) |
I am @walidabualafia colleague. The test data did run successfully but the resultant image does not look correct. This was ran using the following command cudasirecon --config cudasirecon/test_data/config-tiff --otf-file cudasirecon/test_data/otf.tif --input-file cudasirecon/test_data/ --output-file raw Cudasirecon was installed via conda. |
Hi dan, Did you scroll to Z slices 4 or 5 and see if it makes more sense? Slice #1 usually doesn't show anything useful because it's out of focus, especially when the contrast is stretched between min and max intensities. -lin |
@linshaova Here are screenshots from 4 & 5 |
I could duplicate what you got, @dan-alford. @tlambert03, sorry I never tested this test_data before. In cudarecon's log printout, the "modamp" numbers are suspiciously large (~8 for order 2, and ~18 for order 1 except for dir 0). See attached log. Has anything changed? -lin |
Ah, I know what's going on now. You should change the line @tlambert03 could you make that change in the git? thanks! |
Argh, will have to check the git history and repeat locally |
See my last comment just as your comment came out. I just created a PR for the updated |
truly baffled as to how that was wrong. but don't have time at the moment to sleuth it out at the moment. you can confirm that switching to fastSI=0 gives the expected output? |
Yes (sorry I forgot to mention that!) |
|
looks like lattice SIM data probably right? sorry to hear there's been a breaking change in there @dan-alford, that wasn't the intention of course. Can you help narrow down exactly what the older version was? can you run |
Hi @dan-alford , when you say "old version", how old are you talking about? If it was really old (~10 years), then there was a major change in how an OTF TIFF file is organized (related to how complex numbers are represented) since about 8 years ago. If you were using OTF created long time ago, then it may be the reason it doesn't work with the latest version. In that case, you would need to re-generate the OTF file. |
the --version flag was not recognized. the --help gave the following. --input-file arg input file (or data folder in TIFF mode) |
At least in the past, even in LLSM-SIM mode Could you share the printout cudasirecon produced when processing the above dataset you showed? |
@linshaova - which version ? the old or the new? or both? |
both please (with the command line included) |
new version omero@nodegpu234 ~]$ cudasirecon --input-file ~/unit/ --output-file unit --otf-file 488OTFTHEORY.tif --ls 0.501500 --ndirs 1 --bessel --zoomfact 1.500000 --na 1.100000 --nimm 1.330000 --angle0 -1.570000 --otfRA --wiener 0 k0guess[direction 0] = (0.053502, -53.088722) pixels Old Version Calling Sim Reconstruction with
wiener=0.001 deskew_GPU(): no error |
Hi @dan-alford (sorry for the late response), these two instances seem to be both example of failure (neither |
@linshaova apologies for the delays. I can provide them, but I can't see to attach them as tiffs |
Hi all,
Thank you so much for your work on this package.
I just pulled the package and installed, and I am trying to run the following line, but it keeps running into an error:
Whenever I run this line, execution halts when the code gets to cuFFT section. When my teammate traced it with GDB, and found that there is a segmentation fault.
The error that gets written to stdout is:
Has anyone seen this error? Could the code be trying to access illegal memory regions?
Any help is appreciated! :)
Thank you,
Walid
The text was updated successfully, but these errors were encountered: