Dear All,
We recently implemented pial correction using T2 space FLAIR with freesurfer v 5.3, mostly successfully. We use 2-3 MPRAGE (sagittal + axial and/or coronal) volumes as 001.mgz, 002/003.mgz for the motion correction step in recon-all pipeline. The typical times for acquiring space FLAIR in our settings vary from 2.5 to 6 min, depending on the resolution/NSA no. I was wondering how freesurfer deals with motion artifacts in the space FLAIR sequence (especially with longer acquisition times), and if there is a strategy to minimize motion distortion with these (such as getting second runs for averaging, etc). Please advise,
Octavian.
Hi Octaviaan no, not really. You should motion correct and average them using something like mri_motion_correct*
We do typically bandwidth/readout match them to the memprages so that there is no differential distortion
cheers Bruce
On Wed, 1 Jan 2014, Octavian Lie wrote:
Dear All,
We recently implemented pial correction using T2 space FLAIR with freesurfer v 5.3, mostly successfully. We use 2-3 MPRAGE (sagittal + axial and/or coronal) volumes as 001.mgz, 002/003.mgz for the motion correction step in recon-all pipeline. The typical times for acquiring space FLAIR in our settings vary from 2.5 to 6 min, depending on the resolution/NSA no. I was wondering how freesurfer deals with motion artifacts in the space FLAIR sequence (especially with longer acquisition times), and if there is a strategy to minimize motion distortion with these (such as getting second runs for averaging, etc). Please advise,
Octavian.
freesurfer@nmr.mgh.harvard.edu
-
Bruce Fischl -
Octavian Lie