[MINC-users] dicom to minc converter

[Alexandre CARMEL-VEILLEUX]

On Tue, Nov 29, 2005 at 10:18:47AM -0700, Teodor Stanescu wrote:
> 
> 3) Yes, the encoding is little endian.

	You can get the exact encoding by the following method:

strings <file.dcm> | grep 1.2.840.10008.1.

	The output will be a UID starting by the numeric string above.
It's meaning can be derived from Section 6 of the DICOM standard
( http://medical.nema.org/dicom/2004/04_06PU.PDF Table A-1, Page 83.)

1.2.840.10008.1.2.1	(Little Endian, native encoding)

and 

1.2.840.10008.1.2.2	(Big Endian, native encoding)

are the only ones accepted by the dicom_to_minc tools. Any UID starting
with 1.2.840.10008.1.2.4. is for a compressed image and it would need to
be processed through a decompresser ( dcmdjpeg for example).

	Otherwise, a pair of sample slices (contiguous) could be useful.

Alex

>  
> Thanks.
>  
> Teo
>  
>  
> > If I can drop in, there's a few questions I'd have:
> >
> > 1) Did you try dicom_to_minc (Peter neelin's version) ?
> >
> > 2) Did you try dicom_to_minc3.pl (Jonathan Harlap's version using the
> >   DICOMperl library) ?
> >
> > 3) What is the encoding used? I assume that it's native little endian.
> >
> > I also have some bits of codes to reorder dicom files to fix
> > a very similar issue with dicom_to_minc. However that code requires
> > a modified DICOMperl lib to run.
> > 
> > I have the "chance" of having dealt with tricky conversions
> > from probably every scanner model made in the last 15 yeas ;-).
> >
> > Alex
> 
> 
> This e-mail and any attachments may contain confidential and
> privileged information. If you are not the intended recipient,
> please notify the sender immediately by return e-mail, delete this
> e-mail and destroy any copies. Any dissemination or use of this
> information by a person other than the intended recipient is
> unauthorized and may be illegal.
> _______________________________________________
> MINC-users at bic.mni.mcgill.ca
> http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-users