Hi Octavian
it's not so easy to reduce the bandwidth in the T2-space sequences, but
certainly you can try. Geometry-matched just means that the FOV and
matrix sizes are the same.
cheers
Bruce
On Fri, 3 Jan 2014, Octavian Lie wrote:
Dear Bruce,
Best wishes for 2014!
I will heed your advice
Dear Bruce,
Best wishes for 2014!
I will heed your advice and cc to the list. Indeed, the MGH protocol I
obtained from Andre has one acquisition (NSA).
Related, I cc this post:
We have been trying adaptations of the T2spaceFLAIR MGH protocol on
our Phillips 3T scanners (sequences called VISTA).
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
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 i
