Hello CONN people,
We have multi-echo fmri data that’s been processed with fmriprep (motion/slice timing corrected), then put through tedana to denoise it. The data remains in native space.
We now want to put this through the CONN toolbox for estimating a gPPI model. However, when run the “Default Preprocessing Pipeline volume based analyses (direct normalization to MNI space)” we are encountering misregistration. FYI we deselect ART and STC, but left everything else in there (so effectively motion correcting twice). It also fails when omitting functional realignment i.e. “subject motion estimation and correction”.
When looking at the output we find that the structural image has been well registered to the MNI, but the functional is way off. See below.
Under Functional Data Tools in CONN, we select ‘Display coregistration with anatomical data’ and get the following:
https://neurostars.org/uploads/default/o... 1.5x,
https://neurostars.org/uploads/default/o... 2x"
alt="conn" width="349" height="500" loading="lazy"
data-base62-sha1="scSJapyYBLihcz01cXQz8EQGGRz"
data-dominant-color="B1B1B3">
Is this a failure of setting the origin, something else? Really stuck with this.
If anyone has a suggestion for how to take our native-space fmriprep/tedana output into MNI space using CONN I’d be most grateful to hear it.
Best wishes,
Eszter&Jon