clij / clij2

GPU-accelerated image processing for everyone
https://clij.github.io/clij2
Other
48 stars 14 forks source link

Switching the CL-Device while the assistant is running makes it crash. #32

Closed piango closed 3 years ago

piango commented 3 years ago

Hi

Great tool, clij. Just getting used to it. Amazing

I started using it, but I get these error messages when I via the 'clij assistant':

Attached is an example of error I get for 'Gaussian Blur3D(CLIJ2)' .

clij_error

I am using the graphics card of my windows laptop

GPU

Hope its something easy. And not so silly from my side. :) :)

haesleinhuepf commented 3 years ago

Hey @piango ,

great to see you here! Not so great that you get this error message :-)

I'm a tiny bit confused: The 1050 Ti GPU should be absolutely be able to process this 23 MB image. However, the error message says in the top right corner, that the image is stored on an "Intel(R)... " GPU.

Could you just try again? Please start the GPU memory display before starting the assistant and watch what's happening. You can also switch between different GPUs by clicking the menu Plugins > ImageJ on GPU (CLIJx) > Change Default CL Device

Also: How is the pixel-size of your data set? That could be relevant when using the makeIsotropic function.

Cheers, Robert

piango commented 3 years ago

Hey @haesleinhuepf

Great.. thanks for your advice. So it works with your advice of choosing the GPU before running the clij assistant. So basically, can't these errors I get if I change to GPU with the assistant already running. and Some features of Clij don't work with Intel Graphics card. I guess.

Thanks.

:)

piango commented 3 years ago

I will close this issue as a satisfied customer ;)

haesleinhuepf commented 3 years ago

Some features of Clij don't work with Intel Graphics card. I guess.

No! Everything works fine on Intel. But if you push images to the Intel GPU and then change the GPU used, the images are not pulled over. I reopen and rename this issue to take care of it. Thanks for reporting this bug!

haesleinhuepf commented 3 years ago

I've added a warning message to the dialog to prevent that happening again :-) image