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  

|
March 30, 2019 03:58PM
Hi pt,

I really appreciate your help. The below is what I got for the command you suggested for Stim I vs Stim F

hlhp-105:Proc_results_con-fix titus$ 3dinfo -nv stats.subject1.Condition1+tlrc.
10
hlhp-105:Proc_results_con-fix titus$ 3dinfo -nvi stats.subject1.Condition1+tlrc.
9


The below is what I got from Stim I vs Stim C
hlhp-105:Proc_results_con-fix titus$ 3dinfo -nv stats.subject1.Condition1+tlrc.
13
hlhp-105:Proc_results_con-fix titus$ 3dinfo -nvi stats.subject1.Condition1+tlrc.
2


Could you please let me know why these are different even the proc py script was completely the same except stim files? Also, would that be okay to use sub-brick 9 for Stim I vs Stim F for 3dttest++?

Thanks again,
Jun
Subject Author Posted

AFNI proc py bad sub-brick selector

Junyeon March 30, 2019 01:32PM

Re: AFNI proc py bad sub-brick selector

ptaylor March 30, 2019 01:43PM

Re: AFNI proc py bad sub-brick selector

Junyeon March 30, 2019 03:58PM

Re: AFNI proc py bad sub-brick selector

rick reynolds March 30, 2019 09:56PM

Re: AFNI proc py bad sub-brick selector

Junyeon March 31, 2019 10:07AM

Re: AFNI proc py bad sub-brick selector

rick reynolds April 01, 2019 02:08PM

Re: AFNI proc py bad sub-brick selector

Junyeon April 03, 2019 10:57AM