Great - thanks for clarifying!


From: freesurfer-bounces@nmr.mgh.harvard.edu <freesurfer-bounces@nmr.mgh.harvard.edu> on behalf of Andre van der Kouwe <andre@nmr.mgh.harvard.edu>
Sent: Tuesday, March 5, 2019 2:57:13 PM
To: Bruce Fischl
Cc: Freesurfer support list; Sevinc, Gunes; Lazar, Sara
Subject: Re: [Freesurfer] Processing MEMPRAGE
 
Yes, that's correct, it's the smaller RMS file. FreeSurfer will complain
if it's supplied with a multi-frame (4 echo) volume i.e. you should get a
warning if you use the wrong file.

On Tue, 5 Mar 2019, Bruce Fischl wrote:

> Hi Johann
>
> I believe that is the case, but Andre (ccd) can confirm
>
> cheers
> Bruce
>
> On Tue, 5 Mar 2019, Rusche, Johann wrote:
>
>>
>>  Dear Freesurfers,
>>
>>
>>  Reading through the mailing list I understood how to
>>  process our nmr MEPRAGEs and I would like to
>>  double-check we are using unpacksdcmdir correctly.
>>
>>
>>  Unpacking with unpacksdcmdir gives me two nifti files, a 4-echo nifti file
>>  (92MB) and a 1-echo nifti file
>>  (23MB). Am I correct to understand that the smaller 1-echo nifti file is
>>  the RMS created automatically? Can
>>  you confirm that this is the file that I want to send to recon-all
>>  vis-a-vis VBM processing? 
>>
>>
>>  From the unpacklog:
>>
>>    7 MEMPRAGE_tfl_mgh_multiecho_1mm_iso  ok  256 256 176   4
>>  MR.1.3.12.2.1107.5.2.19.45407.2014103021271096561867095
>>    8 MEMPRAGE_tfl_mgh_multiecho_1mm_iso  ok  256 256 176   1
>>  MR.1.3.12.2.1107.5.2.19.45407.2014103021271165037167199
>>
>>  Thanks for your time!
>>
>>  Johann
>>
>>
>>
>>
>>  __________________
>>  Johann Rusche
>>
>>  Graduate Research Student, Lazar Lab
>>  Department of Psychiatry – Neurosciences
>>  Massachusetts General Hospital
>>
>>
>