search

RTKConsortium / RTK

Reconstruction Toolkit
Apache License 2.0
245 stars 145 forks source link

why rtk::CudaFDKConeBeamReconstructionFilter's GetRampFilter()->SetTruncationCorrection() failed! #609

Closed jxhno1 closed 1 month ago

jxhno1 commented 4 months ago

Try to use this filter as title described to do the trunction correction but found that when using a projection data size is 768x768 per frame, SetTruncationCorrection(0.0013) is ok, but SetTruncationCorrection(0.0026) failed! when using a projection data size is 1294x952 per frame, SetTruncationCorrection(0.0026) is ok, but SetTruncationCorrection(0.0013) failed! why this happened? FOV is the difference between this case, and the double num should be calculated to follow some standard? Thank you for your help.

SimonRit commented 4 months ago

Can you please clarify what you mean by fail? 0.13% and 0.26% for the truncation correction, I typically use values closer to 1.

jxhno1 commented 4 months ago

0.13% means I want to correct the ratio 1/768 and 0.26% means the ratio 2/768 for the truncation correction but it did matter among the two case.

SimonRit commented 4 months ago

Please clarify what you mean by "failed" and "it did matter".

jxhno1 commented 4 months ago

Recon process is ok but final output 3d image is the zero value on all pixels. i said "it did matter" means i wonder why they both a parameter just using double as a input, but different in output image.