History of AFNI updates  

|
February 21, 2017 04:53PM
These are all quite different operations.

1. 3drefit is not changing the data at all, just removing information from the header. This shouldn't have any effect on the slice timing.
2. 3dresample -orient LPI. This also loses the oblique information, but more importantly changes the definition of what a slice is (the 3rd dimension 'k') and if you include voxel resolutions or grids potentially introduces interpolation. This will make slice timing correction wrong unless your data is LPI in the first place.
3. 3dWarp - either of the obliquity options will change the oblique angle of the dataset and alter the data. Again slice timing correction will not be possible and wrong if used.

For more info on oblique datasets, see this link:

[afni.nimh.nih.gov]
Subject Author Posted

3dresample/3drefit/3dWarp for oblique datasets and slice timing

AjaySK February 20, 2017 08:02AM

Re: 3dresample/3drefit/3dWarp for oblique datasets and slice timing

Daniel Glen February 21, 2017 04:53PM

Re: 3dresample/3drefit/3dWarp for oblique datasets and slice timing

AjaySK March 02, 2017 09:24AM

Re: 3dresample/3drefit/3dWarp for oblique datasets and slice timing

AjaySK March 15, 2017 12:29PM

Re: 3dresample/3drefit/3dWarp for oblique datasets and slice timing

rick reynolds March 18, 2017 08:14PM

Re: 3dresample/3drefit/3dWarp for oblique datasets and slice timing

AjaySK March 21, 2017 09:11AM

Re: 3dresample/3drefit/3dWarp for oblique datasets and slice timing

Daniel Glen March 21, 2017 12:46PM

Re: 3dresample/3drefit/3dWarp for oblique datasets and slice timing

AjaySK March 24, 2017 11:42AM