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  

Previous Message Next Message
Message List New Topic Print View
|
Ziad Saad
March 13, 2020 06:42PM
Dear Afni connoisseurs,

I hope this finds you healthy and operational.

Say I have three datasets: A.nii.gz, B.nii.gz, and C.nii.gz where
B.nii.gz is an anat in orig space
A.nii.gz is an MNI-space version of B.nii.gz created with 3dAllineate and 3drefit -view +tlrc -space MNI . AFNI recognizes it as such, so far so good.
C.nii.gz is a functional dset in orig space

The problem is that when viewing volume B in AFNI, whereami is disabled despite my efforts to set -wpar and -apar options. Can you advise as to what should be done to the three datasets so that AFNI recognizes the parentage properly and enables whereami when viewing data in orig space?

Sorry for the custom route there, but the xform to MNI space had to be derived by catenating multiple transformations so I could not go the @auto_tlrc route, say.

Cheers,
Z
Reply Quote
RSS
Subject Author Posted

Parentage for manually transformed data

Ziad Saad March 13, 2020 06:42PM

Re: Parentage for manually transformed data

Daniel Glen March 19, 2020 12:34PM

Re: Parentage for manually transformed data

Ziad Saad April 02, 2020 12:37PM