-
Notifications
You must be signed in to change notification settings - Fork 141
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
Issues with using ChangeInformationImageFilter on CudaImage #201
Comments
What if in |
Well, this seems more complicated than what I thought... it needs a method to obtain the data manager from the pixel container... |
I see two solutions at this stage:
|
I've done a little bit more investigation and the previous thought may be wrong. I am thinking if it is because although |
…(...) In CudaImage<...>::SetPixelContainer(...), after setting a new pixel container, the CPU buffer pointer of the CudaImage's CudaDataManager shall also be updated. This is a fix for Issue RTKConsortium#201.
Problem fixed by commit 82ba699. |
There seems to be a CPU-GPU synchronization issue if an
itk::ChangeInformationImageFilter<itk::CudaImage<...>>
is inserted before a Cuda filter. It works if the ChangeInformationImageFilter is inserted before a CPU filter.The issue can be reproduced with the rtkSartCudaTest and the following patch:
Results from the rtkSartCudaTest:
See also the discussion in the thread here.
The text was updated successfully, but these errors were encountered: