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  

|
Anonymous User
June 20, 2012 02:02PM
Dear AFNI experts,

I have a question about the purpose of demeaning motion parameters in 3dDeconvolve step.

I have 6 runs (they are 3 different tasks), therefore, I preprocess them using afni_proc.py without regress block. So I need to feed in appropriate motion parameters in writing 3dDeconvolve script for each task type. In the earlier version of afni_proc.py, I found that it used actual motion file (dfile.rall.1D), but the later version seemed to be using demean_motion file (demeaned by each run). Since it's been demeaned at each run, the values would be different from using raw dfile.rall.1D.

So I am wondering whether using demean motion file vs. raw motion file make much difference? Is there a difference in terms of interpreting beta values of regressors of interest (output from 3dDeconvolve)?

Thanks in advance!
SJ
Subject Author Posted

motion demean vs raw motion parameters

Anonymous User June 20, 2012 02:02PM

Re: motion demean vs raw motion parameters

rick reynolds June 20, 2012 03:04PM

Re: motion demean vs raw motion parameters

Anonymous User June 20, 2012 04:30PM

Re: motion demean vs raw motion parameters

rick reynolds June 20, 2012 04:36PM

Re: motion demean vs raw motion parameters

Anonymous User June 20, 2012 06:34PM