Issues with using ChangeInformationImageFilter on CudaImage about rtk HOT 5 CLOSED

What if in itk::CudaImage::SetPixelContainer, besides passing the pixel container, also pass the cuda data manager and retain the CPU/GPU dirty flags of the manager? Maybe this works for the case of itk::ChangeInformationImageFilter but I don't know if it is generic for all cases that calls itk::CudaImage::SetPixelContainer.

from rtk.

Well, this seems more complicated than what I thought... it needs a method to obtain the data manager from the pixel container...

from rtk.

I see two solutions at this stage:

• modifying itk::ChangeInformationImageFilter to make sure that the CPU buffer is up-to-date. I think the same problem will occur with itk::GPUImage (for OpenCL) so it's worth posting a patch to ITK.
• create a CudaImage specific ChangeInformationImageFilter.

from rtk.

I've done a little bit more investigation and the previous thought may be wrong.
itk::ChangeInformationImageFilter::GenerateData() calls nonConstInput->GetPixelContainer() to get the pixel container of the input, which does a force update of CPU buffer.

I am thinking if it is because although itk::ChangeInformationImageFilter does update the input CPU buffer but it doesn't point the CudaDataManager::m_CPUBuffer of the output to the updated CPU buffer of the input (or, this may be done by SetPixelContainer of CudaImage, like once the pixel container has been reassigned, take care of the m_CPUBuffer as well).

from rtk.

Problem fixed by commit 82ba699.

from rtk.