| Literature DB >> 29764362 |
Claudia de Molina1,2, Estefania Serrano3, Javier Garcia-Blas3, Jesus Carretero3, Manuel Desco4,5,6,7, Monica Abella1,2,8.
Abstract
BACKGROUND: Standard cone-beam computed tomography (CBCT) involves the acquisition of at least 360 projections rotating through 360 degrees. Nevertheless, there are cases in which only a few projections can be taken in a limited angular span, such as during surgery, where rotation of the source-detector pair is limited to less than 180 degrees. Reconstruction of limited data with the conventional method proposed by Feldkamp, Davis and Kress (FDK) results in severe artifacts. Iterative methods may compensate for the lack of data by including additional prior information, although they imply a high computational burden and memory consumption.Entities:
Keywords: CBCT; GPU; Iterative reconstruction; Limited-data tomography; Memory management; Parallel processing; Split Bregman
Mesh:
Year: 2018 PMID: 29764362 PMCID: PMC5952580 DOI: 10.1186/s12859-018-2169-3
Source DB: PubMed Journal: BMC Bioinformatics ISSN: 1471-2105 Impact factor: 3.169
Fig. 1TV3D iterative reconstruction workflow
Fig. 2Workflow of the callback function for Krylov solver
Fig. 3From left to right: reference image and reconstructed image with the FDK-method and the proposed iterative method. Top panel corresponds to the case of 60 projections covering an angular span of 360 degrees and bottom panel to the case of 45 projections covering an angular span of 150 degrees. Yellow circle in the bottom left panel shows the ROI for the SNR measurement
SNR difference in dB between the FDK and the iterative reconstruction; RMSE between the iterative reconstruction and the reference image for different limited-data configurations
| Angular span | Projections | SNR Difference (dB) | RMSE |
|---|---|---|---|
| 135 | 45 | 20.79 | 0.268 |
| 150 | 45 | 23.20 | 0.220 |
| 360 | 45 | 28.27 | 0.154 |
| 360 | 90 | 26.17 | 0.153 |
| 360 | 120 | 25.98 | 0.151 |
Fig. 4RMSE vs. iterations for 60, 90 and 120 projections (full span) angular span of 135, 150 and 180 degrees (45 projections)
Fig. 5Execution time (in seconds) for different number of projections (NumProj)
Fig. 6Execution time (in seconds) for different angular span (degrees)
Fig. 7Execution time (in seconds) for different projection size (DimProj)
Fig. 8Execution time (in seconds) of the first iteration for both CPU and GPU implementations for different number of projections (NumProj)
Fig. 9Execution time (in seconds) of the first iteration for both CPU and GPU implementations for different angular span (degrees)