Hello Rick,

Thanks a lot for your super prompt response. Definately very helpful.

So it seems that different siemens scanners can adopt different ways of storing the Image position tag? (Since some siemens datasets match very well with the raw dicom co-ods and the last sag slice upper left hand afni co-ods)
OR
Is there something wrong with this dataset?

The co-ordinates in the first raw dicom image are:
-87.2/-135.7/97.9

The following is the output of 3dinfo on the reconstructed afni dset

++ 3dinfo: AFNI version=AFNI_2007_05_29_1644 (Aug 27 2007) [32-bit]

Dataset File: OutBrick_run_006+orig
Identifier Code: XYZ_yN-4DOij7MsidabMCp6uvA Creation Date: Tue Sep 4 12:02:51 2007
Dataset Type: Spoiled GRASS (-spgr)
Byte Order: LSB_FIRST [this CPU native = LSB_FIRST]
Storage Mode: BRIK file
Data Axes Orientation:
first (x) = Anterior-to-Posterior
second (y) = Superior-to-Inferior
third (z) = Left-to-Right [-orient ASL]
R-to-L extent: -102.926 [R] -to- 56.074 [L] -step- 1.000 mm [160 voxels]A-to-P extent: -148.035 [A] -to- 91.028 [P] -step- 0.938 mm [256 voxels]I-to-S extent: -134.397 -to- 104.665 [S] -step- 0.938 mm [256 voxels]Number of values stored at each pixel = 1
-- At sub-brick #0 \'#0\' datum type is short: 0 to 800


Is there a way to cross check between the raw coods and the afni coods for this dataset?

Thanks again..
aparna