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  

|
April 10, 2023 05:47PM
Ok, I think that I found the problem.
What a mess, but let me explain, I now remember another detail that I did here.

I extracted the voxel-based time series with 3dmaskdump using the option "-no ijk" so that the resulting .1D files do NOT include the voxel coordinates.
Why? Because I wanted to run interpolation in Python, and it was easier for me to script it this way.

Subsequently, I also extracted the voxel coordinates from the atlas file that I created.
Now, comparing the voxel coordinates between the atlas and the 3dmaskdump extracted errts files shows me that the voxel coordinates are NOT the same.
Sorry! I feel like an idiot.

I thought that both voxel coordinates should match, since the preprocessed errts files used the MNI152 template.

I guess that is the core of the problem.


Edit: Paul, forget what I wrote above. If I extract all voxel coordinates from the preprocessed errts. file, of course I will get many voxels that do not match the atlas, since the errts file includes all voxels, whereas the atlas/mask/roi does not. Furthermore, 3dinfo showed that "Resample_Yeo7N_1000ribbon.nii" (my atlas file) an the errts file do match.I have no idea anymore where the problem comes from, I am fully lost now.



Edited 2 time(s). Last edit at 04/10/2023 11:43PM by Philipp.
Subject Author Posted

Extracting voxel-wise data with 3dmaskdump and recombing it with 3dUndump Attachments

Philipp April 10, 2023 07:59AM

Re: Extracting voxel-wise data with 3dmaskdump and recombing it with 3dUndump Attachments

Philipp April 10, 2023 08:13AM

Re: Extracting voxel-wise data with 3dmaskdump and recombing it with 3dUndump

ptaylor April 10, 2023 09:23AM

Re: Extracting voxel-wise data with 3dmaskdump and recombing it with 3dUndump Attachments

Philipp April 10, 2023 12:53PM

Re: Extracting voxel-wise data with 3dmaskdump and recombing it with 3dUndump

ptaylor April 10, 2023 03:18PM

Re: Extracting voxel-wise data with 3dmaskdump and recombing it with 3dUndump

Philipp April 10, 2023 03:20PM

Re: Extracting voxel-wise data with 3dmaskdump and recombing it with 3dUndump

Philipp April 10, 2023 03:31PM

Re: Extracting voxel-wise data with 3dmaskdump and recombing it with 3dUndump

ptaylor April 10, 2023 03:38PM

Re: Extracting voxel-wise data with 3dmaskdump and recombing it with 3dUndump

Philipp April 10, 2023 03:47PM

Re: Extracting voxel-wise data with 3dmaskdump and recombing it with 3dUndump

ptaylor April 10, 2023 04:56PM

Re: Extracting voxel-wise data with 3dmaskdump and recombing it with 3dUndump

Philipp April 10, 2023 05:11PM

Re: Extracting voxel-wise data with 3dmaskdump and recombing it with 3dUndump

ptaylor April 10, 2023 05:29PM

Re: Extracting voxel-wise data with 3dmaskdump and recombing it with 3dUndump

Philipp April 10, 2023 05:40PM

Re: Extracting voxel-wise data with 3dmaskdump and recombing it with 3dUndump

Philipp April 10, 2023 05:47PM

Re: Extracting voxel-wise data with 3dmaskdump and recombing it with 3dUndump

Philipp April 11, 2023 04:01AM

Re: Extracting voxel-wise data with 3dmaskdump and recombing it with 3dUndump

ptaylor April 11, 2023 09:54AM

Re: Extracting voxel-wise data with 3dmaskdump and recombing it with 3dUndump

Philipp April 11, 2023 02:14PM

Re: Extracting voxel-wise data with 3dmaskdump and recombing it with 3dUndump

rick reynolds April 18, 2023 04:12PM