Hello all,

I was using the following command line to blur a time series dataset.

3dmerge -1blur_fwhm 6 -prefix ts.reg.despike.oral.blur.fwhm.6.011.test -doall ts.reg.despike.oral.011+orig

the output for some reason had every value ranging from a negative number to a positive.

I had used the same blurring command two months ago and I had a scale from 0 to the same positive numbers.

Results from 3dinfo from 2 months ago:

Dataset File: ts.reg.despike.oral.blur.fwhm.6.011+orig
Identifier Code: XYZ_JFYIHhoI9vOnXbRXpOEiiQ Creation Date: Thu Sep 1 12:13:10
2005
Dataset Type: Echo Planar (-epan)
Byte Order: LSB_FIRST [this CPU native = LSB_FIRST]
Storage Mode: BRIK file
Data Axes Orientation:
first (x) = Right-to-Left
second (y) = Anterior-to-Posterior
third (z) = Inferior-to-Superior [-orient RAI]
R-to-L extent: -118.125 [R] -to- 118.125 [L] -step- 3.750 mm [ 64 voxels]A-to-P extent: -118.125 [A] -to- 118.125 [P] -step- 3.750 mm [ 64 voxels]I-to-S extent: -58.100 -to- 81.900 [S] -step- 5.000 mm [ 29 voxels]Number of time steps = 212 Number of values at each pixel = 1
Time step = 1.500s Origin = 0.000s
-- At sub-brick #0 '#0' datum type is short: 0 to 5632
-- At sub-brick #1 '#1' datum type is short: 0 to 5865
-- At sub-brick #2 '#2' datum type is short: 0 to 5860
-- At sub-brick #3 '#3' datum type is short: 0 to 5910
-- At sub-brick #4 '#4' datum type is short: 0 to 5856
-- At sub-brick #5 '#5' datum type is short: 0 to 5720
-- At sub-brick #6 '#6' datum type is short: 0 to 5788


Results from 3dinfo for the same command line run on the same datset today:

Dataset File: ts.reg.despike.oral.blur.fwhm.6.011.test+orig
Identifier Code: XYZ_TVlp0Tw4oxNe-JVF_vftrQ Creation Date: Wed Nov 16 15:51:24
2005
Dataset Type: Echo Planar (-epan)
Byte Order: LSB_FIRST [this CPU native = LSB_FIRST]
Storage Mode: BRIK file
Data Axes Orientation:
first (x) = Right-to-Left
second (y) = Anterior-to-Posterior
third (z) = Inferior-to-Superior [-orient RAI]
R-to-L extent: -118.125 [R] -to- 118.125 [L] -step- 3.750 mm [ 64 voxels]A-to-P extent: -118.125 [A] -to- 118.125 [P] -step- 3.750 mm [ 64 voxels]I-to-S extent: -58.100 -to- 81.900 [S] -step- 5.000 mm [ 29 voxels]Number of time steps = 212 Number of values at each pixel = 1
Time step = 1.500s Origin = 0.000s
-- At sub-brick #0 '#0' datum type is short: -16 to 5632
-- At sub-brick #1 '#1' datum type is short: -19 to 5865
-- At sub-brick #2 '#2' datum type is short: -19 to 5860
-- At sub-brick #3 '#3' datum type is short: -20 to 5910
-- At sub-brick #4 '#4' datum type is short: -17 to 5856
-- At sub-brick #5 '#5' datum type is short: -17 to 5720
-- At sub-brick #6 '#6' datum type is short: -20 to 5788
:


I then used the following 3dcalc function to check for the negative values:

3dcalc -a ts.reg.despike.oral.blur.fwhm.6.011.test+orig. -expr 'a*step(-a)' -prefix ts.neg

. The image shows areas outside the time series data. So hopefully the time series data is not affected

Any ideas about this??????

thanks
nameeta