Parcellation in native or standard space

Hi all,

I currently try to figure out whether it´s better to perform (atlas-based; Schaefer2018) parcellation in native (T1w) space or standard ( MNI152NLin2009cAsym) space, as provided by fmriprep for connectivity / network analyses.

It seems most of the studies transform their atlas to native space (accounting for individual differences, avoiding interpolation etc.), but some also used fmriprep resampled bold to MNI152 and do the parcellation e.g., in nilearn.

My thoughts so far:

  • (subject space) given the MNI152NLin2009cAsym Schaefer2018 version @Tensorflow it should be possible to use an inverse transformation matrix to transform the atlas to subject space, however I wonder whether it´d a problem that epis are currently not resampled to T1 in fmriprep, but keep their original resolution (e.g. 3x3x3 vs 1x1x1 in T1)

  • (standard space) nilearn functionality is neat when it comes to extracting signal from parcels, however nilearns Schaefer2018 refers to MNI152FSL, which seems not to be equal to MNI152 as provided by fmriprep? However, using Tensorflow Schaefer 2018 would solve this issue.

I would appreciate any thoughts, idea, readings whether native space is superior to standard space because of … , or vice versa!

Best,
Dominik

2 Likes

templateflow and not tensorflow of course :grimacing:

Hi,

I am currently facing the same issue and thought about doing transforming the atlas to subject space.
Do you have some experience with it? I’m a bit unsure what the best practice for this would be with fmriprep outputs.

Edit: Or to be more exact: Which transformation(s) do I need, where do I find them and what’s the best tool to use (AFNI? ANTs?)

Thanks!

Hi Mibur,

the critical transformation is the first one below:

sub-<subject_label>/
anat/
sub-<subject_label>_from-MNI152NLin2009cAsym_to-T1w_mode-image_xfm.h5
sub-<subject_label>_from-T1w_to-MNI152NLin2009cAsym_mode-image_xfm.h5

I am not 100% sure whether you need to set both T1w and MNI as --output space to get both transformations in fmriprep (its been a while … :smiley: ) - but maybe someone can jump in here?

But if you got this, you can e.g., use ANTs apply transform (man antsApplyTransforms (1): part of ANTS registration suite) to transform your atlas from MNI to subject space. I used GitHub - PennLINC/xcpEngine: Official public repository for the XCP Engine for denoising my FC data - and very conveniently the transformation described above is integrated within the pipeline.

Hope this helps,

Best
Dominik

1 Like

Thanks for the reply! I have the MNI to T1w .h5 file available, so that should be fine. Can I pass it it directly to e.g. ApplyTransform without any further processing/extraction of data?

yes! In my case, XCP did this (no guarantee, that this is the only/best way!):

antsApplyTransforms -e 3 -d 3 -i /dir_to/schaefer100x7MNI.nii.gz -r /dir_to_reference_image/sub-YYYY.nii.gz -o /outpur_dir/sub-YYYY_schaefer100x7.nii.gz -n MultiLabel -t /dir_to_transform/sub-YYYY_from-MNI152NLin2009cAsym_to-T1w_mode-image_xfm.h5

Best,
Dominik

1 Like