Currently, "recon-all" script can take the option of "-cm" (conform to min voxel size).
This may end up creating more slices than 256, but freesurfer should be able to handle
as long as there are enough memory left. Make sure that you have 2 Gbyte of
memory and 2 GByte of swap space. Here, we are approaching the 32 bit memory
address limit.
{snip}
This 2gig, 32 bit limit is something I'm starting to worry about. With resolutions of functional data ever increasing, we're getting to the point where it's likely we'll need to address more than 2 gigs of memory in the next year or two.
Are there any plans to address this? I'm not sure what you can do with FS-FAST, since it depends on Matlab and I don't know if there are 64-bit versions of matlab available (especially for affordable platforms like AMD64 and the G5).
<aside>
I'll insert my plug for moving FS-FAST to python here, as python natively works on 64 bit platforms.
</aside>
But with Freesurfer, how hard will it be to build a 64 bit version? If you need a testing machine, I'm working from a dual G5 that would be more than happy to build Freesurfer :-)
Nick
_______________________________________________ Freesurfer mailing list [EMAIL PROTECTED] http://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer
