mriconvert: Intended behaviour for multi-frame images?

[Jolinda Smith]

The intended behavior, of course, is that all frames be present. However, due to the rarity and variety of multiframe data we have not been able to ensure that it works in every case. Unfortunately we don't have the resources right now to address problems that primarily affect users outside of our own institution. I recommend trying the excellent "dcm2nii" converter instead, to see if that works with your data.

Jolinda

On Wed, 01 Jul 2015 18:47:25 -0700, Steve M. Robbins <steve at sumost.ca> wrote:

> Hi,
>
> What is the intended behaviour for multi-frame images?
>
> While updating the Debian package to 2.0.8, I ran across an old bug report [1]
> about this.  The example file [2] is 23 frames of 120x120 pixels, with 32-bit
> pixels.   The user expectation is that all frames would be output, but it
> seems that only one frame is present.  I tried just now with v2.0.8: I
> converted to MetaImage and obtained an image of size 57600 (120 x 120 x 4)
> instead of 1324800.
>
> Thanks,
> -Steve
>
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617342
> [2] http://gdcm.sourceforge.net/thingies/RTDose.dcm.gz
>


-- 
Jolinda Smith, Ph.D.
MR Physicist
Lewis Center for Neuroimaging
University of Oregon
Eugene, OR USA