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  

|
May 24, 2017 08:17AM
Hi, Ajay--

Re. flipping gradients: different softwares and scanner systems just have different ways of referring to positive/negative x,y,z directions. I don't know why it's not standard, but many things in MRI like this aren't (very unfortunately!). I have usually found dcm2nii/dcm2niix to be reliable and low maintenance: I always check, though, to be sure, esp. when I get data from a new scanner, protocol, center, etc.

Basically, +/- differences don't affect magnitude values of DTI fitting, but they do affect the relative orientations in space (which itself is pretty important). I use tractography to help me feel confident that the system is consistent, and the tool in AFNI-FATCAT for this is @GradFlipTest-- I'd recommend using that. It basically tests out WB tractographic results for each flip (including no flip), and counts tracts to guess a winner: usually, then difference is quite large and clear, and you also get prompted to look at each result to verify.

Note that moving to/from software tools will change the flipping, likely: for example, TORTOISE internally does use a different system than AFNI (such is life), but one can always fix this pretty straightforwardly with @GradFlipTest and 1dDW_Grad_o_Mat++.

--pt
Subject Author Posted

1dDW_Grad_O_Mat++ and missing -proc_dset flag

AjaySK April 13, 2017 02:06AM

Re: 1dDW_Grad_O_Mat++ and missing -proc_dset flag

ptaylor April 13, 2017 09:22AM

Re: 1dDW_Grad_O_Mat++ and missing -proc_dset flag

AjaySK April 13, 2017 05:28PM

Re: 1dDW_Grad_O_Mat++ and missing -proc_dset flag

ptaylor April 13, 2017 09:04PM

Re: 1dDW_Grad_O_Mat++ and missing -proc_dset flag

AjaySK May 23, 2017 05:53PM

Re: 1dDW_Grad_O_Mat++ and missing -proc_dset flag

AjaySK May 23, 2017 06:16PM

Re: 1dDW_Grad_O_Mat++ and missing -proc_dset flag

ptaylor May 23, 2017 07:03PM

Re: 1dDW_Grad_O_Mat++ and missing -proc_dset flag

AjaySK May 24, 2017 01:39AM

Re: 1dDW_Grad_O_Mat++ and missing -proc_dset flag

ptaylor May 24, 2017 08:17AM

Re: 1dDW_Grad_O_Mat++ and missing -proc_dset flag

ptaylor May 23, 2017 06:57PM

Re: 1dDW_Grad_O_Mat++ and missing -proc_dset flag

Peter Molfese May 24, 2017 11:10AM

Re: 1dDW_Grad_O_Mat++ and missing -proc_dset flag

AjaySK May 24, 2017 06:47PM

Re: 1dDW_Grad_O_Mat++ and missing -proc_dset flag

AjaySK May 26, 2017 03:56PM

Re: 1dDW_Grad_O_Mat++ and missing -proc_dset flag

Peter Molfese May 26, 2017 04:50PM

Re: 1dDW_Grad_O_Mat++ and missing -proc_dset flag

AjaySK July 28, 2017 10:15AM