However, I am facing issues with the inhomogeneity correction done during autorecon1. In fact, the rescaling step between orig.mgz -> orig_nu.mgz
AND the '-nuintensitycorr' step between orig.mgz -> nu.mgz completely destroys the homogeneity gained from the SPM12 BiasField Correction applied beforehand.
The exact command line I'm using is:
$ recon-all -all -s P7T_020_001bc -hires -i BC_MPRAGE_iPat2.nii -expert expert-file.opts
- where BC_MPRAGE_iPat2.nii is the output of SPM12 BiasField Correction (i.e., the bias field corrected MPRAGE image) and expert-file.opts the
file containing ''mris_inflate -n 100".
I am using FS version 7.2.0 (freesurfer-linux-ubuntu18_x86_64-7.2.0-20210721-aa8f76b) on Linux Ubuntu 18.04 bionic (Linux mrphys-gpu1 4.15.0-180-generic #189-Ubuntu SMP Wed May 18 14:13:57 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux).
The whole recon-all runs properly without errors, but the homogeneity is worse after the NU intensity correction...
See screenshots in attachments (orig.mgz VS nu.mgz). I have also attached the recon-all.log file.
I am currently testing the '-nonuintensitycor' flag, but it exited WITH errors (not the recon-all.log file attached).
In addition, I tried the exact same pipeline but without passing the data through SPM12 beforehand. It still did the same thing of destroying the small amount of homogeneity in the image to an even worst level of inhomogeneity.
On another matter, this part in the link I provided above is quite unclear:
"""
Recommended bias-correction parameters:
- Bias FWHM = 18
- Sampling distance = 2
"""
A Bias FWHM of 18 mm is not possible with SPM12 (minimum being 30 mm). So, is it for SPM12 or something as part of recon-all? For the sampling distance, it's fine with the 2 mm in SPM12.
Have a great day! 🙂
Marc-Antoine