fMRIPrep is a robust and easy-to-use pipeline for preprocessing of diverse fMRI data. The transparent workflow dispenses of manual intervention, thereby ensuring the reproducibility of the results.
As far as I can tell, running fMRIPrep v1.5.0 with --output-spaces fsaverage:den-41k does not yield the expected GIfTI outputs with 40,962 vertices. It yields files named sub-*_task-*_space-fsaverage_hemi-*.func.gii, which appear to have the 163,842 vertices expected for "fsaverage" (rather than "fsaverage6"). The HTML outputs for fMRIPrep only list "fsaverage" as a standard output space. Note that I did not include the high-density fsaverage option in --output-spaces, only fsaverage:den-41k. Has anyone else encountered this yet? (I assume den-41k should also be specified in the output filename?) I'll try explicitly including fsaverage6 in --output-spaces for now.
As far as I can tell, running fMRIPrep v1.5.0 with
--output-spaces fsaverage:den-41k
does not yield the expected GIfTI outputs with 40,962 vertices. It yields files namedsub-*_task-*_space-fsaverage_hemi-*.func.gii
, which appear to have the 163,842 vertices expected for "fsaverage" (rather than "fsaverage6"). The HTML outputs for fMRIPrep only list "fsaverage" as a standard output space. Note that I did not include the high-densityfsaverage
option in--output-spaces
, onlyfsaverage:den-41k
. Has anyone else encountered this yet? (I assumeden-41k
should also be specified in the output filename?) I'll try explicitly includingfsaverage6
in--output-spaces
for now.