[Insight-users] NRRD to DICOM

[Luis Ibanez]

Hi Barry,


If your input NRRD image is a 3D image, then you probably want to
try the example:

     ITK/Examples/IO/ImageReadDicomSeriesWrite.cxx

This should create as output a series of 2D dicom files.


     Luis



------------------------------------
On Thu, Mar 10, 2011 at 5:27 PM, Barry Vuong <barry.vuong at gmail.com> wrote:
> Dear Luis,
>
> My name is Barry Vuong and I'm a graduate student at Ryerson University in
> Canada. I stumbled onto one of the forums which was discussing the topic of
> NRRD to DICOM conversion
> (http://old.nabble.com/Convert-NRRD-into-DICOM-td24148686.html#a31120270). I
> was partially successful in converting the NRRD file to DICOM using the
> Imagereadwrite.exe from ITK, however the result was a 2D image from a 3D
> dataset. You mentioned on your post that the file had to retouch the example
> in order for 3D operation. I was wondering if you could give a bit more
> insight to what you meant by this.
>
> Thank you for your time and help,
>
> Regards,
>
> Barry
>
> --
> Barry Vuong, B.Eng, M.A.Sc., Ph. D. Candidate, E.I.T.
> Vice Chair, IEEE Toronto Engineering in Medicine & Biology
>
> Vice President, Canadian Institute for Photonic Innovations - Student
> Network
>
> --------------------------------------------------------------------
> Department of Electrical & Computer Engineering
> Ryerson University
> 350 Victoria St., Toronto, ONT. M5B 2K3
> Phone: 416-979-5000 ext 2144
> E-mail: bvuong at ee.ryerson.ca
> IEEE Website: http://toronto.ieee.ca/chapters/embs/index.html
> CIPI-S Website: http://cipis.fsg.ulaval.ca/
> Website: http://bvuong.wikidot.com
> ------------------------------------
> This e-mail may contain confidential and/or privileged information for the
> sole use of the intended recipient. Any review or distribution by anyone
> other than the person for whom it was originally intended is strictly
> prohibited. If you have received this e-mail in error, please contact the
> sender and delete all copies. Opinions, conclusions or other information
> contained in this e-mail may not be that of the organization.
>