[MINC-users] mincaverage bug

[Andrew Janke]

Hi Alex,

On 14 December 2011 06:42, Alex Zijdenbos <zijdenbos at gmail.com> wrote:
> I just stumbled across a bug in mincaverage. If you try to average a
> list of volumes that have a small range for the data type (e.g., byte
> 0-3), the average (correctly) inherits that data type- and range. But
> obviously a 4-valued average is hardly useful; so I thought the output
> type options would come to the rescue. Alas, they only seem to affect
> the sd volume, not the average. In other words, running something like
> this:
>
>   mincaverage -short -range 0 1000 in1.mnc in2.mnc avg.mnc -sdfile sd.mnc
>
> will give sd.mnc a short type and the advertised range; but not avg.mnc.

I can't seem to reproduce this behavior you speak of?

$ mincaverage -double bp-native.mnc a.mnc
$ mincaverage -double bp-native.mnc d.mnc
$ mincaverage -short -range 0 1000 bp-native.mnc s.mnc

cai-harold:~$ mincinfo a.mnc d.mnc s.mnc
file: a.mnc
image: unsigned byte 0 to 255
image dimensions: zspace yspace xspace
    dimension name         length         step        start
    --------------         ------         ----        -----
    zspace                    267      1.01563     -135.079
    yspace                    217      1.01563     -109.688
    xspace                    267      1.01563     -135.079


file: d.mnc
image: signed__ double 0 to 5.4909507159588706315
image dimensions: zspace yspace xspace
    dimension name         length         step        start
    --------------         ------         ----        -----
    zspace                    267      1.01563     -135.079
    yspace                    217      1.01563     -109.688
    xspace                    267      1.01563     -135.079


file: s.mnc
image: unsigned short 0 to 1000
image dimensions: zspace yspace xspace
    dimension name         length         step        start
    --------------         ------         ----        -----
    zspace                    267      1.01563     -135.079
    yspace                    217      1.01563     -109.688
    xspace                    267      1.01563     -135.079

?

mincaverage uses voxel_loop so if there is a bug in there it will
affect a number other minc tools as well.


ta


a