Use Projector in a Nerual Network

[spencer03172023]

Use Projector in a Nerual Network

[kylechampley]

Could you verify that your data (projections and volume) are all on GPU 0 and are contiguous float32 arrays?

[spencer03172023]

l on GPU 0 and are contiguous float32 arrays

Thanks for your reply, Kyle. I did check below in debug mode.
data.dtype is torch.float32, data.is_contiguous is true and all data is on GPU0

[kylechampley]

Thanks for checking. Next thing to check is the order of the data. Some CT software packages store their projection data in "sinogram order" while LEAP stores it in "projection order". In LEAP the order of the projections data is (numAngles, numRows, numCols). Is this consistent with your code?

[hws203]

@spencer03172023 How about checking the memory-alignment.
cudaMemcpy3D requires that the src and dst memory be aligned. The src or dst memory must therefore be allocated using cudaMallocPitch or cudaMalloc3D rather than cudaMalloc. Hope it helps you.

[spencer03172023]

Thanks for checking. Next thing to check is the order of the data. Some CT software packages store their projection data in "sinogram order" while LEAP stores it in "projection order". In LEAP the order of the projections data is (numAngles, numRows, numCols). Is this consistent with your code?

Thanks, Kyle. I did check the sinogram data structure, and make it same as LEAP requirement. It can work now.

[spencer03172023]

@spencer03172023 How about checking the memory-alignment. cudaMemcpy3D requires that the src and dst memory be aligned. The src or dst memory must therefore be allocated using cudaMallocPitch or cudaMalloc3D rather than cudaMalloc. Hope it helps you.

Thanks. Data array difference caused this. Thanks