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
| January 27, 2009 05:19PM | |
Dear AFNI Community,
We're interested in estimating condition-specific IRF durations in an event-related paradigm. We've tried/conceived of two ways to do this:
1. Run 3dTstat with the -duration option on IRFs rendered from 3dDeconvolve with the -iresp option. This works okay.
2. We're considering - but have not yet tried - the new duration modulation feature in 3dDeconvolve. Perhaps something like...
3dDeconvolve -input 3dplustime+orig -num_stimts 2 \
-stim_times_AM 1 cond1.1D 'dmBLOCK' -stim_label 1 'cond1' \
-stim_times_AM 2 cond2.1D 'dmBLOCK' -stim_label 2 'cond2' \
-gltsym 'SYM: +cond1 -cond2' -glt_label 1 'cond1 - cond2' \
cond1.1D = 4:12 18:12 30:12 ...
cond2.1D = 12:12 40:12 56:12 ...
In this case, we've set the "modulating parameter" to a constant value of 12 since we're not interested in any condition-by-behavioral measure effects, only in condition effects on average IRF duration. Another, perhaps ridiculous, way to say what we're after is that we're looking for a way to rotate 3dDeconvolve 90 degrees and to estimate extent on the time dimension as opposed to the signal intensity dimension.
Please feel free to respond only with a "
" if I've misunderstood the basic intent the duration modulation option.
We're interested in estimating condition-specific IRF durations in an event-related paradigm. We've tried/conceived of two ways to do this:
1. Run 3dTstat with the -duration option on IRFs rendered from 3dDeconvolve with the -iresp option. This works okay.
2. We're considering - but have not yet tried - the new duration modulation feature in 3dDeconvolve. Perhaps something like...
3dDeconvolve -input 3dplustime+orig -num_stimts 2 \
-stim_times_AM 1 cond1.1D 'dmBLOCK' -stim_label 1 'cond1' \
-stim_times_AM 2 cond2.1D 'dmBLOCK' -stim_label 2 'cond2' \
-gltsym 'SYM: +cond1 -cond2' -glt_label 1 'cond1 - cond2' \
cond1.1D = 4:12 18:12 30:12 ...
cond2.1D = 12:12 40:12 56:12 ...
In this case, we've set the "modulating parameter" to a constant value of 12 since we're not interested in any condition-by-behavioral measure effects, only in condition effects on average IRF duration. Another, perhaps ridiculous, way to say what we're after is that we're looking for a way to rotate 3dDeconvolve 90 degrees and to estimate extent on the time dimension as opposed to the signal intensity dimension.
Please feel free to respond only with a "
" if I've misunderstood the basic intent the duration modulation option.
| Subject | Author | Posted |
|---|---|---|
|
Paul Hamilton | January 27, 2009 05:19PM |
|
Bob Cox | January 28, 2009 10:24AM |
|
Paul Hamilton | January 28, 2009 09:26PM |
|
Paul Hamilton | February 23, 2009 09:25PM |
