You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After running the CIFTI pipeline with --project-goodvoxels, I tried to load the sub-###_ses-###_task-rest_space-fsLR_den-91k_bold.dtseries.nii on Left and right midthickness surface files inside Workbench View. I got this error:
The CIFTI file contains 32492 nodes for structure CortexLeft but the corresponding surface brain structure contains 232669 nodes.
It seems the surfaces are not in 91k resolution.
Also, an additional question:
Does that "den" indicate denoised? So, there is no need for further denoising (e.g., with XCP-D)?
Thanks for the reply. The only .surf.gii files with fsLR in the analyzed /anat folder are
sub-##_ses-001_hemi-L/R_space-fsLR_desc-reg_sphere.surf.gii,
sub-##_ses-001_hemi-L/R_space-fsLR_desc-msmsulc_sphere.surf.gii
There are no midthickness/pial/white surf.gii files in "fsLR". Even though loading fsLR.dtseries.nii on the above-mentioned sphere surfaces also results in the same previous error. Of note, fmriprep's log file has no errors.
What happened?
Hi,
After running the CIFTI pipeline with --project-goodvoxels, I tried to load the sub-###_ses-###_task-rest_space-fsLR_den-91k_bold.dtseries.nii on Left and right midthickness surface files inside Workbench View. I got this error:
The CIFTI file contains 32492 nodes for structure CortexLeft but the corresponding surface brain structure contains 232669 nodes.
It seems the surfaces are not in 91k resolution.
Also, an additional question:
Does that "den" indicate denoised? So, there is no need for further denoising (e.g., with XCP-D)?
What command did you use?
What version of fMRIPrep are you running?
23.2.0a3
How are you running fMRIPrep?
Singularity
Is your data BIDS valid?
Yes
Are you reusing any previously computed results?
No
Please copy and paste any relevant log output.
No response
Additional information / screenshots
No response
The text was updated successfully, but these errors were encountered: