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  

|
December 02, 2022 10:01AM
Assuming the oblique warning above is fine (since it's there, and the same, already for anat_final vs vr_min_outlier, I assume it's fine)...

Then the goal is to get the live nii file to overlap well with the vr_base_min_outlier (or I guess anat_final is also fine).

Now I have done nothing to obliquess in any dataset.
I only do this:
3dcopy ../../data/nii_1/1.nii 1
Generating 1+orig.

If I only do:
3dvolreg -zpad 1 -base  ../localizer_results/ref.results/vr_base_min_outlier+orig. \
          -1Dfile dfile.1D -prefix 1.volreg \
          -cubic 1+orig
The 1.volreg+orig file is shifted compared to vr_min_outlier (attached image)

If I add -two-pass:
3dvolreg -zpad 1 -base  ../localizer_results/ref.results/vr_base_min_outlier+orig. -twopass \
          -1Dfile dfile.1D -prefix 1.volreg_twopass \
          -cubic 1+orig.
There is absolutely no difference. Values are identical.

I can make it better by first running:
@Align_Centers \
:
mkdir TR$i
cp ../../../data/live_DICOMS/$name TR$i/
dcm2niix TR$i/
cd TR$i
mv *.nii TR$i.nii
3dcopy TR$i.nii TR$i

@Align_Centers \
   -cm \
   -base /home/rtfMRI/rtfMRI_engine/final_eval/basic/localizer_results/ref.results/vr_base_min_outlier+orig.  \
   -dset TR$i+orig. \


3dvolreg -zpad 1 -base  /home/rtfMRI/rtfMRI_engine/final_eval/basic/localizer_results/ref.results/vr_base_min_outlier+orig. -twopass \
          -1Dfile dfile.1D -prefix TR$i.volreg \
          -cubic TR${i}_shft+orig.

mni_mask=/home/rtfMRI/rtfMRI_engine/final_eval/basic/localizer_results/mask_original_space+orig.
cd ..
3dmaskave -q -mask $mni_mask TR$i/TR$i.volreg+orig >> tc_ACC.1D
Then the overlap is pretty good: attached.

This signal looks good. But it takes longer to process it when adding @Align centers. I really should not need to do it.
But it is possible that the the live EPI's are further away from the localizer EPI. Some time passes between them (FLAIR + resting state).



Edited 1 time(s). Last edit at 12/02/2022 10:04AM by Robin.
Attachments:
open | download - ulay_vr_base_olay_TR1_volreg.png (34.7 KB)
open | download - ulay_vr_base_olay_volreg_shft.png (36.2 KB)
Subject Author Posted

alignment in afni_proc.py during neurofeedback Attachments

Robin December 01, 2022 07:23AM

Re: alignment in afni_proc.py during neurofeedback

ptaylor December 01, 2022 09:27AM

Re: alignment in afni_proc.py during neurofeedback

Robin December 01, 2022 09:38AM

Re: alignment in afni_proc.py during neurofeedback

rick reynolds December 01, 2022 11:26AM

Re: alignment in afni_proc.py during neurofeedback

Robin December 02, 2022 07:35AM

Re: alignment in afni_proc.py during neurofeedback Attachments

Robin December 02, 2022 10:01AM

Re: alignment in afni_proc.py during neurofeedback

rick reynolds December 05, 2022 06:14PM