[MINC-users] mincreshape segfault and general behavior
Soren Christensen
sorench at gmail.com
Tue Oct 1 15:08:35 EDT 2013
Hi,
I was hoping someone could explain the below mincreshape behavior.
Basically I get segfaults for certain choices of dimsizes.
When I leave Z unmodified, the file is written, but with padding.
1) I assume the segfault is a bug? (or am I feeding illegal input)
2) Why is padding introduced? Is it padded to achieve volume averaging of
whole voxels only (as opposed to fractions).
3) Is it correctly understood that mincreshape does volume averaging for
downsizing as opposed to mincreshape that will just use the specified
interpolation method?
Thanks
Soren
MNC$ mi A.mnc
file: A.mnc
image: signed__ float -2048.041015625 to 3123.968017578125
image dimensions: time zspace yspace xspace
dimension name length step start
-------------- ------ ---- -----
time 19 1 0
zspace 312 0.5 -585.268
yspace 420 -0.43 70.4
xspace 342 -0.43 80.112
MNC$ mincreshape -clobber -dimsize xspace=100 -dimsize yspace=100 -dimsize
zspace=100 A.mnc B.mnc
Copying chunks:......Segmentation fault (core dumped)
s at s-IdeaCentre-K450:/data2/TOSH_DATA/DATA/MNC$ mincreshape -clobber
-dimsize xspace=100 -dimsize yspace=100 -dimsize zspace=312 A.mnc B.mnc
Copying
chunks:..................................................................................................................................................................
[works]
More information about the MINC-users
mailing list