Hi all,
Can't say enough thanks for your great suite of programs which I swear by!
1) problem with to3d:
I am encountering an error with a certain dicom DTI dataset from a Siemens Trio:
to3d -prefix test.nii /path/ser008img*
++ to3d: AFNI version=AFNI_2008_07_18_1710 (Jan 29 2009) [64-bit]
++ Authored by: RW Cox
++ Counting images: total=3120 2D slices
++ DICOM WARNING: bad Siemens Mosaic params: nx=18 ny=18 ix=7 iy=7 imx=128 imy=128
++ Data detected to be oblique
++ Each 2D slice is 128 X 128 pixels
++ Voxel dimensions: 1.7188 X 1.7188 X 3.0000 mm
++ Image data type = short
++ Reading images: ++ DICOM WARNING: bad Siemens Mosaic params: nx=18 ny=18 ix=7 iy=7 imx=128 imy=128
.++ DICOM NOTICE: no more Siemens Mosaic param messages will be printed
.........................................
Fatal Signal 11 (SIGSEGV) received
mri_read_file
T3D_read_images
to3d:main
Bottom of Debug Stack
** AFNI version = AFNI_2008_07_18_1710 Compile date = Jan 29 2009
** [[Precompiled binary linux_gcc33_64: Jan 29 2009]]
** Program Abort **
So I have 78 timepoints, each timepoint is a single mosaiced image of 7 rows x 7 cols, each slice is 128x128 for a total of 40 slices (first 9 slices are blank)
The warning prints: nx=18 ny=18 ix=7 iy=7 imx=128 imy=128
does that mean to3d thinks I have 18x18 images instead of 128x128?
Have you encountered this problem before?
2) problem with 3dcalc
Thought I should post this as well: When I try to mask a DTI image using 3dcalc -expr 'a*step(b)', if a is the tensor and b is a mask, the resulting volume has an intent code of 0 instead of 1005 which is the diffusion tensor intent code. Is this a bug?
Thanks for all your help, keep up the wonderful work you're doing!
