afni.nimh.nih.gov
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:
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
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
| October 26, 2017 03:15PM | |
Hi Rick,
Wouldn't "post_rest 9" give me the 9 seconds (i.e. 3 baseline trials) I need at the end of each run?
You had asked about what the GLT would look like for "all the conditions together vs baseline".
When trying to create these GLTs I got confused because I will need to code the baseline conditions as 'rest' as far as 3dDeconvolve in concerned, that is, not code for it at all. This is different from how I am coding the baseline condition in MRT.py because I am having to code it as a 'real' condition. So, any automated scripts that take the MRT.py and pipe them into the 3dDeconvolve -nodata will have to be modified to account for this.
Assuming we (
) can figure that trick out, I would code the 3dDeconvolve glts as follows:
Here I am trying to do the task (labels 1 through 8) vs baseline comparison.
gltsym 'SYM: +label1 +label2 +label3 +label4 +label5 +label6 +label7 +label8' -glt_label 1 "Task_vs_Baseline"
For area under the curve for each condition it would be
-gltsym 'label1'' -glt_label 'label1AUC'
etc, same for each label.
Christine
Wouldn't "post_rest 9" give me the 9 seconds (i.e. 3 baseline trials) I need at the end of each run?
You had asked about what the GLT would look like for "all the conditions together vs baseline".
When trying to create these GLTs I got confused because I will need to code the baseline conditions as 'rest' as far as 3dDeconvolve in concerned, that is, not code for it at all. This is different from how I am coding the baseline condition in MRT.py because I am having to code it as a 'real' condition. So, any automated scripts that take the MRT.py and pipe them into the 3dDeconvolve -nodata will have to be modified to account for this.
Assuming we (
) can figure that trick out, I would code the 3dDeconvolve glts as follows:
Here I am trying to do the task (labels 1 through 8) vs baseline comparison.
gltsym 'SYM: +label1 +label2 +label3 +label4 +label5 +label6 +label7 +label8' -glt_label 1 "Task_vs_Baseline"
For area under the curve for each condition it would be
-gltsym 'label1'' -glt_label 'label1AUC'
etc, same for each label.
Christine
