[MINC-users] MINC to DICOM

[Andrew Janke]

> The root of the issue seems to be one of expectation: If all you
> expect is a set of DICOM files each containing one slice with the
> header containing only the most basic of coordinate space definition
> info, then this conversion is relatively simple and you can hack it
> together with a combination of minctoraw and your DICOM package of
> choice (dicom3tools, dcmtk, etc...).  However, in my experience people
> seem to have this interesting notion that they should be able to take
> some DICOM data off a scanner, run it through dcm2mnc and then back
> through a fictional mnc2dcm and that the resultant files will be
> identical to the input files

Amen brother Jon.

And it is quite simply a pandoras box that I am not all that
interested in for the reasons pointed out above. Just by simply
writing mcn2ana (the logical reverse of ana2mnc) I increased my
workload significantly a while back. :)  As such I am very
trepidatious to do it again.


a