[Rtk-users] Helical cone-beam reconstruction with RTK

[Robert Calließ]

Hello Vahid,

I think you need to add a new reconstruction filter for it. For the first projection the object usually is placed so that the

resulting projection image covers the upper half of the detector. And you will need some additional handling (z-increment).

I guess you could do a little work around with the current rtk. If you only reconstruct an rectangular roi around

the detector’s center where the perspective distortion (because of the cone) is minimal. And then you add these

seperate volumes to a final volume. This is just an idea. I do not know how the result will look like. Think of it like a TDI

but with a wider sensor array.

 

I do not know the code in detail, but if it were possible to have seperate geometry settings for every projection image it 

would be possible to model the helical trajectory by the changing geometry without changing /adding code.

 

But let’s see what grandmasters of RTK will suggest.

 

Best regards,

Robert

                

 

Von: Rtk-users [mailto:rtk-users-bounces at public.kitware.com] Im Auftrag von vahid ettehadi via Rtk-users
Gesendet: Donnerstag, 26. Februar 2015 20:35
An: rtk-users at public.kitware.com
Betreff: [Rtk-users] Helical cone-beam reconstruction with RTK

 

Dear RTK users,

 

 

I am using the RTK code to reconstruct the image for a bench-top micro-CT in a circular cone-beam geometry. It works well with FDK algo. Thanks RTK.

I would like to change the current source trajectory from circular to helical. I was wondering is it possible to use the RTK for helical reconstruction only with some simple modification?

I don't know well about reconstruction process and I don't know which type of modification is necessary to use RTK for a helical cone beam geometry. So, any suggestion and recommendation would be appreciated.

 

Sincerely,

Vahid

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.creatis.insa-lyon.fr/pipermail/rtk-users/attachments/20150226/0b7db6e2/attachment.htm>