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  

|
siamak
February 13, 2009 01:56PM
Hi All,

I've done some processing on a dataset. The 3dinfo result of the dataset before processing is as follows:

LPI,
R to L extent: -239.531 [R] to -0.469 [R] Step: 0.938 mm [256]
A to P extent: -239.531 [A] to -0.469 [A] Step: 0.938 mm [256]
I to S extent: 0.750 [S] to 191.250[S] Step: 1.500 mm [128]

While the 3dinfo of the processed dataset is:
RPI
R to L extent: -120.000 [R] to 119.062 [L] Step: 0.938 mm [256]
A to P extent: -119.062 [A] to 120.000 [P] Step: 0.938 mm [256]
I to S extent: -96.000 to 94.500 [S] Step: 1.500 mm [128]

As you see the resolutions are the same. But, when I want to overlay them
and see the result of processing, they have not overlap. How can I fix this problem (change the processed image apace exactly to native image space)?

Best,
Siamak
Subject Author Posted

Problem with image native space after processing

siamak February 13, 2009 01:56PM

Re: Problem with image native space after processing

Daniel Glen February 13, 2009 03:12PM

Re: Problem with image native space after processing

siamak February 13, 2009 04:35PM