Re: [Freesurfer] Unpacking Philips scans work-around... should this work?

2018-06-04 Thread Patrycja Naumczyk
External Email - Use Caution I'm a Philips user as well. Creating a hierarchical directory tree is sufficient enough, but for one thing. Nifti files do not carry the information normally stored in DICOM header, and FS-Fast requires the f.nii to have embeded info about the

Re: [Freesurfer] Unpacking Philips scans work-around... should this work?

2018-06-02 Thread DeCross, Stephanie N.
Right, I can run recon-all for the structural run. But what about for a functional run where all I have is one nifti per subject? I meant for preprocessing etc. the functional things, if I manually create the hierarchy, is that one raw .nii per subject enough info to carry out the rest of the

Re: [Freesurfer] Unpacking Philips scans work-around... should this work?

2018-06-02 Thread Bruce Fischl
Hi Stephanie you shouldn't have to create the directory structure or anything. If you have nifti files you can give those to recon-all as input in the same way you would dicom (with -i directories and do it's thing cheers Bruce On Sat, 2 Jun 2018, DeCross, Stephanie N. wrote: Hi, I have

[Freesurfer] Unpacking Philips scans work-around... should this work?

2018-06-01 Thread DeCross, Stephanie N.
Hi, I have scans from a Philips scanner I want to process with FreeSurfer. Previously, the scans have been downloaded in the Philips PAR/REC format and converted into niftis, and those niftis have been used as the raw inputs in other imaging pipelines. Instead of dredging up the original