Iterative reconstruction produces artifacts on both ends of the slice

[zezisme]

Expected Behavior

Hello ！ When using cone-beam CT reconstruction, no matter how I define the reconstruction parameters, using the iterative reconstruction algorithm (SART, OS-SART, ...) will cause serious artifacts on both ends of the slice image, while the FDK algorithm is normal. What may be the reason for this? I have tested many iterative reconstruction algorithms and all of them have this problem.

Actual Behavior

FDK

OS-SART

other example(OS-SART) MPR view

Code to reproduce the problem (If applicable)

Specifications

• MATLAB version:
• OS:
• CUDA version:

[AnderBiguri]

Yes, those are cone beam artifacts, natural in CBCT. They tend to be worse in iterative algorithms in the situation in where there was more object in the area you are not reconstructing, as iterative algorithms try to match the measured projections with the reconstruction, however as you don't have the whole image in the ROI, they put more values in the extrema to accomodate.

A standard way to mitigate these is to make the reconstruction volume (nVoxel and sVoxel) bigger in the Z direction. Then you can crop it out after recon if you want it the same size as FDK.

[zezisme]

Yes, those are cone beam artifacts, natural in CBCT. They tend to be worse in iterative algorithms in the situation in where there was more object in the area you are not reconstructing, as iterative algorithms try to match the measured projections with the reconstruction, however as you don't have the whole image in the ROI, they put more values in the extrema to accomodate.

A standard way to mitigate these is to make the reconstruction volume (nVoxel and sVoxel) bigger in the Z direction. Then you can crop it out after recon if you want it the same size as FDK.

Thank you for your clear explanation！I will try your suggestion