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  

Previous Message Next Message
Message List New Topic Print View
|
wo222
February 20, 2018 08:01AM
Dear AFNI experts,

I am using the same code for different datasets and for some datasets the results are in original space (files have the +orig extension), while for some datasets the results seem to be in Talairach space (there are the +tlrc extensions). I am using AFNI 16.2.02 and the code is:

afni_proc.py \
-subj_id $subject \
-script proc.$subject -scr_overwrite \
-regress_opts_3dD -force_TR $TR \
-tcat_remove_first_trs 0 \
-dsets ${path_data}/${subject}_${task}_bold.nii \
-volreg_align_to third \
-regress_polort 2 \
-regress_bandpass 0.01 10 \
-blur_size ${smoothing}.${zero_aux} \
-regress_stim_types AM1 \
-regress_stim_times $stim_times \
-regress_stim_labels activation_stimulus \
-regress_basis ${HRF} \
-regress_make_ideal_sum sum_ideal.1D \
-regress_run_clustsim no \
-regress_est_blur_epits \
-regress_est_blur_errts \
-regress_reml_exec \
-regress_opts_reml -Rwherr whitened_errts.${subject}_REML

Do you have any idea why there might be differences?

Sorry for bothering you!

Best,

Wiktor Olszowy



Edited 1 time(s). Last edit at 02/20/2018 08:02AM by wo222.
Reply Quote
RSS
Subject Author Posted

the same code run on different datasets -> +tlrc OR +orig produced

wo222 February 20, 2018 08:01AM

Re: the same code run on different datasets -> +tlrc OR +orig produced

Peter Molfese February 20, 2018 10:47AM

Re: the same code run on different datasets -> +tlrc OR +orig produced

wo222 February 21, 2018 09:09AM

Re: the same code run on different datasets -> +tlrc OR +orig produced

Peter Molfese February 21, 2018 10:29AM

Re: the same code run on different datasets -> +tlrc OR +orig produced

wo222 February 21, 2018 02:59PM