AFNI Message Board

Dear AFNI users-

We are very pleased to announce that the new AFNI Message Board framework is up! Please join us at:

https://discuss.afni.nimh.nih.gov

Existing user accounts have been migrated, so returning users can login by requesting a password reset. New users can create accounts, as well, through a standard account creation process. Please note that these setup emails might initially go to spam folders (esp. for NIH users!), so please check those locations in the beginning.

The current Message Board discussion threads have been migrated to the new framework. The current Message Board will remain visible, but read-only, for a little while.

Sincerely, AFNI HQ

History of AFNI updates  

|
george he
September 09, 2003 06:27PM
Hi,

When I convert GE dicom files to AFNI brick, it seems that to3d gives incorrect
position information.

The command I used was

to3d -spgr -prefix anat "SerieMR-0013/SerieMR-0013-????.dcm"

where SerieMR-0013-????.dcm are the dicom files.

After the anat+orig files are generated, 3dinfo reports inconsistent image position
information than what reported by dicom3tools (dcdump)

Anybody knows which one is correct?

Thanks,

George

-------------------- here is the output of 3dinfo --------------------------
Data Axes Orientation:
first (x) = Right-to-Left
second (y) = Superior-to-Inferior
third (z) = Posterior-to-Anterior [-orient RSP]
R-to-L extent: -105.707 [R] -to- 113.434 [L] -step- 0.859 mm [256 voxels]
A-to-P extent: -90.100 [A] -to- 94.400 [P] -step- 1.500 mm [124 voxels]
I-to-S extent: -108.071 -to- 111.070 [S] -step- 0.859 mm [256 voxels]
Number of values stored at each pixel = 1
-- At sub-brick #0 '#0' datum type is short: 0 to 407

----------- here are a few lines copied from dcdump output -----------
dcdump SerieMR-0013/SerieMR-0013-0001.dcm
(0x0018,0x0050) DS Slice Thickness VR=<DS> VL=<0x0008> <1.500000>
(0x0018,0x0088) DS Spacing Between Slices VR=<DS> VL=<0x0004> <1.5 >
(0x0018,0x1100) DS Reconstruction Diameter VR=<DS> VL=<0x000a> <220.000000>
(0x0019,0x1018) LO First Scan RAS VR=<LO> VL=<0x0002> <P >
(0x0019,0x1019) DS First Scan Location VR=<DS> VL=<0x000c> <-94.399597 >
(0x0019,0x101a) LO Last Scan RAS VR=<LO> VL=<0x0002> <A >
(0x0019,0x101b) DS Last Scan Location VR=<DS> VL=<0x000a> <90.100403>
# note: 184.5=(124-1)*1.5, there are 124 2d slices in the directory
(0x0020,0x0032) DS Image Position (Patient) VR=<DS> VL=<0x0020> <-105.707\94.3996\111.07>
(0x0027,0x1048) FL R Coord Of Top Right Corner VR=<FL> VL=<0x0004> {-114.293}
(0x0027,0x1049) FL A Coord Of Top Right Corner VR=<FL> VL=<0x0004> {-94.3996}
(0x0027,0x104a) FL S Coord Of Top Right Corner VR=<FL> VL=<0x0004> {111.07}
(0x0027,0x104b) FL R Coord Of Bottom Right Corner VR=<FL> VL=<0x0004> {-114.293}
(0x0027,0x104c) FL A Coord Of Bottom Right Corner VR=<FL> VL=<0x0004> {-94.3996}
(0x0027,0x104d) FL S Coord Of Bottom Right Corner VR=<FL> VL=<0x0004> {-108.93}

(0x0028,0x0030) DS Pixel Spacing VR=<DS> VL=<0x0012> <0.859375\0.859375 >
# note: 220/0.859375=256
Subject Author Posted

to3d get incorrect position info?

george he September 09, 2003 06:27PM

Re: to3d get incorrect position info?

Rich Hammett September 10, 2003 11:04AM

Re: to3d get incorrect position info?

george he September 10, 2003 11:41AM

Re: to3d get incorrect position info?

Rich Hammett September 10, 2003 12:02PM

Re: to3d get incorrect position info?

george he September 10, 2003 12:43PM

Re: to3d get incorrect position info?

Rich Hammett September 10, 2003 12:55PM

Re: to3d get incorrect position info?

george he September 10, 2003 01:16PM