About the projection data of Mayo 2016 dataset

[mkxyz-123]

Hello! I wonder why the size of the projection data is 64x736? Some of the literature I found said that the size of the projection data should be 2304x736. Why does the projection data look so narrow, not like the general projected data that I've seen before.

[mkxyz-123]

The general projected data that I've seen before in a literature.

[qgao21]

Because Mayo 2016 provides spiral CT projection data, while the images you supplied are either fan beam or parallel beam CT projection data. A rebinning operation is necessary to convert the spiral CT data into fan beam geometry for reconstruction using the FBP algorithm.

Each DICOM-CT-PD folder contains a 'txt' file detailing the data specifics, with '64' and '736' representing the detector's rows and columns, respectively, and '2304' indicating the number of projections per rotation. To work with this projection data, you need to explore spiral CT reconstruction algorithms. If you only want to process fan beam projection data, consider utilizing the MIRT or ASTRA toolkits for forward projection.

[mkxyz-123]

Because Mayo 2016 provides spiral CT projection data, while the images you supplied are either fan beam or parallel beam CT projection data. A rebinning operation is necessary to convert the spiral CT data into fan beam geometry for reconstruction using the FBP algorithm.

Each DICOM-CT-PD folder contains a 'txt' file detailing the data specifics, with '64' and '736' representing the detector's rows and columns, respectively, and '2304' indicating the number of projections per rotation. To work with this projection data, you need to explore spiral CT reconstruction algorithms. If you only want to process fan beam projection data, consider utilizing the MIRT or ASTRA toolkits for forward projection.

Thank you soooooo much! You helped me a lot.