Open tlambert03 opened 7 years ago
not a fix, but a better error message introduced in b19c9bb15d589464df666cbc8537f91ee35c2456 and 0.2.3, with the option to disable spimagine (which fixes the problem, but ... obviously... disables spimagine)
Would it be possible to pin the gpuTools to one gpu, and use another for decon? This would be nice for our system since we have regularly turn uncheck our Quadro for decon since it has a smaller memory size, and just use the tesla
i'll try to look in to that. If the main issue is just that it's annoying to have to uncheck the quadro every time you start the program, it would relatively easy for me to just add that to settings that get saved automatically (so that it remembered your setting from session to session)... but i fear that the problem with gputools playing poorly with the libcudaDeconv library goes deeper than that (in the past, if I even imported them together, stuff broke on some Win10 systems), so you might still not be able to use the spimagine viewer if you're having this annoying WinError problem
that said, I don't think I ever really looked into an approach where gputools and libcudadeconv got their own GPU, so I'll try to see how hard it will be (first I need to remember some things about how it works!)
Thanks. I was just thinking of a way to get the preview to work with spimagine, it's not an issue of keeping the box checked.
Using the new cudaDeconv that Lin had provided back in june, I made some modifications in a forked repo to utilize that version correctly for the bleach correction and rotation, since some of the flags had changed or were added.
tracking a bug seen on some windows computers (definitely seen on win10, maybe win7) in which importing gputools causes a crash when trying to access shared functions in libcudaDeconv.
On the other hand, if gputools is imported after the first call to libcudaDeconv, then gputools fails to get resources
running CUDA DeviceQuery shows that the GPU does not seem to be running in exclusive mode:
but nonetheless, the two don't work together well... Not sure where to find the equivalent setting in opencl/clinfo
doesn't seem to be a problem on mac or linux...