[Insight-users] RT-DOSE and CT image registration??
Andriy Fedorov
fedorov at bwh.harvard.edu
Wed Sep 4 23:16:24 EDT 2013
> Date: Tue, 3 Sep 2013 21:04:11 -0700 (PDT)
> From: abhishek <abhishek at meddiff.com>
> Subject: Re: [Insight-users] RT-DOSE and CT image registration??
> To: insight-users at itk.org
> Message-ID: <1378267451131-7583912.post at n2.nabble.com>
> Content-Type: text/plain; charset=us-ascii
>
> Hello Sureerat,
>
> Will, translating RT-DOSE to the center of target CT image help? Or there is
> something else, I need to consider?
>
FYI, you could consider looking at the tools developed by the SlicerRT project
https://www.assembla.com/spaces/slicerrt/wiki
> Regards,
> Abhishek.
>
>
>
> --
> View this message in context: http://itk-insight-users.2283740.n2.nabble.com/RT-DOSE-and-CT-image-registration-tp7583908p7583912.html
> Sent from the ITK Insight Users mailing list archive at Nabble.com.
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 4 Sep 2013 10:19:50 +0200
> From: Olivier Commowick <Olivier.Commowick at inria.fr>
> Subject: [Insight-users] ITK image file readers and memory consumption
> To: "insight-users at itk.org" <insight-users at itk.org>
> Message-ID: <8832B283-8CF5-48F0-A6C3-4751B2C7A220 at inria.fr>
> Content-Type: text/plain; charset=us-ascii
>
> Good morning,
>
> I am writing this email to you since I couldn't find the info on the list. Sorry if that topic was already brought up. We have been using ITK for quite a while and start only now to process large volumes of data (eg the diffusion images for the human connectome project). Therefore, we are facing memory consumption problems.
>
> I have been looking at how images are read and why it seemed to me that twice the size of the image being read was used by the image file reader. As far as I understand, an image is read in two steps :
>
> - first the appropriate imageio reads the data into a buffer (and also header data for image information)
> - then the image file reader converts if needed this buffer into a new buffer of the appropriate pixel type that is copied into the output image. If this is not needed the imageio buffer is just copied into the output image.
>
> This means if I understood well that potentially twice or even three times the image (in the case of conversion) is stored in memory. I was wondering if there would be any way to avoid these buffer copies or creations, at least for the case where no conversion is needed.
>
> Thanks in advance for your answer. Best,
>
> Olivier Commowick
>
>
>
>
>
>
>
> ------------------------------
>
> _______________________________________________
> Insight-users mailing list
> Insight-users at itk.org
> http://www.itk.org/mailman/listinfo/insight-users
>
>
> End of Insight-users Digest, Vol 113, Issue 5
> *********************************************
More information about the Insight-users
mailing list