Hi Jenna,

The only special things to do for that are to pass the motion parameters via -regress_motion_file, and to pass any other (sets of?) regressors of no interest via -regress_extra_ortvec (and _labels). Beyond that, would you like to do blurring and/or scaling?

Just for a start, here is an example that processes like rest, but with no extra regressors of no interest for now.

It gives:
- processing blocks (mask blur scale regress)
- 3 sets of input files (EPI, anat, motion (task is ignored, but could be passed))
- processing options (here, blur size, motion regressor types and censor limits)
- if you want afni_proc.py to do the high-pass filtering with sinusoids, this includes such options
- then QC options (radial correlate, blur estimation and pythonic HTML)

# assuming shell-specific $ddir pointing to data:
afni_proc.py -subj_id Santa                                  \
   -blocks                   mask blur scale regress         \
   -dsets                    $ddir/pb02.FT.r0*.HEAD          \
   -copy_anat                $ddir/anat_final.FT+tlrc.HEAD   \
   -regress_motion_file      $ddir/dfile_rall.1D             \
   -blur_size                6                               \
   -regress_censor_outliers  0.05                            \
   -regress_motion_per_run                                   \
   -regress_apply_mot_types  demean deriv                    \
   -regress_censor_motion    0.2                             \
                                                             \
   -regress_bandpass         0.01 1                          \
   -regress_polort           2                               \
                                                             \
   -radial_correlate_blocks  tcat                            \
   -regress_est_blur_epits                                   \
   -regress_est_blur_errts                                   \
   -html_review_style        pythonic

If you would like this to be for task, add corresponding -regress_ options. I did not put any -regress_extra_ortvec options (e.g. squared motion terms and sinusoids, or other confounds if you want them), but they are simple to include. For example, you could pass that entire confounds file, but it might be better to separate at least the motion, so that afni_proc.py can do censoring and report on it with the QC.

Pre-steady state volumes are better off being removed before the the analysis (-tcat_remove_first_trs, for which timing files or the fmriprep regressors might need altering). Including them in any temporal computations is not a good idea, including those done by fmriprep.

Please feel free to adjust for your experiment and let me know.

- rick