Because I am using data that was already preprocessed, I only need to do reconstruction. However, I realized that when I ran it, the error code, FreeSurfer data is required to make HSVS 5tt image. popped up.
Because I did not use FreeSurfer for preprocessing, I do not know what files freesurfer gives and hence do not know which files have to be inside of the freesurfer directory in order to make the reconstruction work… Does anyone know what kind of data I need and how I can get it?
Yes, there is very specific folder and file naming conventions. It would not be worth the effort trying to make it manually based on files you may or may not have.
Yes, you can add --do-reconall to your qsiprep command.
Our group usually runs freesurfer as part of fmriprep and then uses its output for the 5tt hsvs workflow in qsiprep. Almost any normal run of recon-all will produce everything you need for 5tt hsvs
Hi,
I‘d like to ask if it’s possible to use T1w images preprocessed by qsiprep directly with recon-all? Does the original qsiprep pipeline (with the --do-reconall parameter) operate this way? I’m a bit uncertain whether some of the overlapping preprocessing steps, like bias field correction, between recon-all and qsiprep might have a significant negative impact on the final 5tt file generated. Thank you very much in advance for your guidance.
No I would not recommend using the preprocessed qsiprep t1 in recon-all, because steps like bias correction would be repeated. Is there a reason you don’t want to use the raw T1?
Thank you for your response. The reason I was considering using the preprocessed QSIPrep T1 in recon-all is that my subsequent reconstruction work is not being performed with QSIRECON. Therefore, I need a 5TT image that is aligned with the DWI. If I were to use the raw T1, I would need to perform an additional registration step to align it with the DWI.
It seems that using the QSIPrep output T1 for recon-all is not recommended. In that case, I’ll proceed with manual registration instead. Alternatively, would it be feasible to specify the -nonuintensitycor option when calling recon-all to address this issue?