Hi, just to make the problem a bit more transparent, I took a second screenshot of the slices with the pial surface from the -T2pial run in red and the pial surface from the normal run in cyan: https://dl.dropbox.com/s/jv8rcxnq50tdac6/bad_slice_both_pial.png


On Fri, Sep 27, 2013 at 10:37 AM, Michael Waskom <mwaskom@stanford.edu> wrote:
Hi,

I'm using FS 5.3 and trying to use hires T2-weighted scans to refine the pial mesh.

However, I've found that using the T2 is causing rather dramatic problems with the pial surface.

I processed the same subject's data with and without the -T2pial option. Here are links to a) pial surface image b) slices through the volume and c) the recon-all.log:

With -T2pial
----------------

Without -T2pial
--------------------

The release notes for 5.3 claim that the T2 is registered to the T1 before refining the surface, but I actually can't find any evidence of that sequence in the log file. For this subject, the T1 and T2 came from different scan sessions, although I have other data where they were acquired in the same session that have similar, if less dramatic, problems with the pial surface.

Any ideas?

Michael