[Castor-users] Detector movement

[Simon Stute]

Hi Milan,

Thanks for your interest into CASToR !

The next release will not contain detector movements, only movements of 
the patient.

Anyway, whatever the movement we are talking about, it is always 
considered in a discrete sense (opposite to continuous).

There are no solutions yet in the iterative reconstruction world to 
implement a reconstruction with continuous time management, because 
everything is algebraic and is by definition discrete. In your case, you 
may consider the image as unique over the whole revolution of your 
detectors, but you will need the sensitivity image as a continuous 
function of the time, which is hardly computable.

However, this is a very interesting question that remains to be solved 
and would make an interesting area of research, but it is a stand-alone 
research project on its own, to my opinion.

Even Siemens with their continuous PET bed motion does not implement a 
continuous reconstruction and cut the acquisition into "chuncks" which 
roughly correspond to discrete bed positions.

All the best !
Simon


Le 27/06/2018 à 11:35, Milan Zvolsky a écrit :
> Dear CASToR developers & users,
>
> I just started using CASToR very recently, so maybe my questions are 
> ignorant.
>
> I am simulating a PET system with GATE, consisting of two opposite 
> modules on a cylindricalPET geometry. Now, I want to rotate the two 
> modules during the acquisition, both continuous rotation as well as 
> distinct rotation steps, and move them in z (or move the phantom along z).
> I want to reconstruct the data using MLEM (either list-mode or histogram).
>
> There will also be an experimental realisation of this setup, whose 
> data I would like to reconstruct with CASToR.
>
> In your 2.0 release notes, you already refer to a future release 
> including dynamic aspects, incl motion management.
>
> Does this comprise detector movement?
> Obviously, I could also translate the detector movement into a phantom 
> movement and static detectors, if this helps.
>
> If yes, could you give a rough estimate when this release can be 
> expected? Or would it be possible to get any non-released code (sth 
> like a development branch)?
>
>
> Or are there other possibilities already now, how to incorporate 
> detector movement?
> Ideally, I would like to give CASToR a tracking file which defines the 
> position of the modules (or of each crystal) for different time stamps.
>
>
> Best regards, and thanks for your support,
>
> Milan
>
> *
> Dr. Milan Zvolsk**ý*
>
> *
> *
> *Universität zu Lübeck*
> *Institut für Medizintechnik*
> Tel +49 451 3101 5466
> www.imt.uni-luebeck.de <http://www.imt.uni-luebeck.de>
> Bld. 64, 1st Floor, R. 24
> Ratzeburger Allee 160
> 23562 Lübeck
>
>
>
> _______________________________________________
> Castor-users mailing list
> Castor-users at lists.castor-project.org
> http://lists.castor-project.org/listinfo/castor-users


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.castor-project.org/pipermail/castor-users/attachments/20180627/1864d61e/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 7100 bytes
Desc: not available
URL: <http://lists.castor-project.org/pipermail/castor-users/attachments/20180627/1864d61e/attachment-0001.png>