Glad to hear this ! So how should I specify high resolution structure using 
recon-all command?


> On Oct 17, 2015, at 10:09, Bruce Fischl <[email protected]> wrote:
> 
> High resolution fMRI has always been supported. V6 beta has better support 
> for high-resolution structurals. If your fMRI is higher than 1mm isotropic 
> then having higher res structurals (and hence denser cortical meshes) might 
> be useful
> 
> cheers
> Bruce
> 
> 
> 
> On Sat, 17 Oct 2015, Yun Wang wrote:
> 
>> Can the recon-all for high resolution fMRI data be used in V6 beta 
>> freesurfer now? If
>> so, how to use it?
>> 
>>      On Jun 25, 2015, at 13:36, Allison Moreau <[email protected]>
>>      wrote:
>> Hi Falk and Thomas,
>> We are actually working on testing the -hires flag now for the v6 release. We
>> intend to release it with v6.
>> -Allison 
>> On 06/25/2015 07:09 AM, Falk Lüsebrink wrote:
>>      Hi Thomas,
>>  
>> this looks like a really nice script and a lot better than my own. In the
>> upcoming release of FreeSurfer v.6 my work-around probably is not needed
>> anymore. However, I haven’t been able to have a look at the dev release yet
>> and whether the standard recon-all features a flag to process high
>> resolution data.
>>  
>> Best,
>> Falk
>>  
>> P.S. Following your instructions one will definitely become a coffee
>> junkie. :D
>>  
>> Von: [email protected] 
>> [mailto:[email protected]
>> .edu] Im Auftrag von Emmerling Thomas (PSYCHOLOGY)
>> Gesendet: Mittwoch, 24. Juni 2015 14:35
>> An: [email protected]
>> Betreff: [Freesurfer] recon-all pipeline for (sub-millimeter) 7T data
>>  
>> Hello!
>>  
>> I wrote a bash script some time ago to process data acquired at a
>> sub-millimeter resolution following the nice wiki entry of Falk Lüsebrink
>> (https://surfer.nmr.mgh.harvard.edu/fswiki/HiResRecon). I thought it might
>> be helpful for others, too, as there are some questions about it in the
>> mailing list archives, so here it
>> is: https://github.com/thomastweets/freesurfer-7t-pipeline. I am happy
>> about any comments!
>>  
>> Best,
>> Thomas
>> _______________________________________________
>> Freesurfer mailing list
>> [email protected]
>> https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer
>> _______________________________________________
>> Freesurfer mailing list
>> [email protected]
>> https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer
>> The information in this e-mail is intended only for the person to whom it is
>> addressed. If you believe this e-mail was sent to you in error and the e-mail
>> contains patient information, please contact the Partners Compliance 
>> HelpLine at
>> http://www.partners.org/complianceline . If the e-mail was sent to you in 
>> error
>> but does not contain patient information, please contact the sender and 
>> properly
>> dispose of the e-mail.
> _______________________________________________
> Freesurfer mailing list
> [email protected]
> https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer
> 
> 
> The information in this e-mail is intended only for the person to whom it is
> addressed. If you believe this e-mail was sent to you in error and the e-mail
> contains patient information, please contact the Partners Compliance HelpLine 
> at
> http://www.partners.org/complianceline . If the e-mail was sent to you in 
> error
> but does not contain patient information, please contact the sender and 
> properly
> dispose of the e-mail.


_______________________________________________
Freesurfer mailing list
[email protected]
https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer

Reply via email to