hi bruce,
thanks. from the reading of "recon-all" it looks like this is a failure is
occurring in the latter part of autorecon3 so I'm just rerunning that set
and skipping autorecon2 on the subjects that failed.
correct?
best,
-robert
On 6/4/13 9:38 AM, "Bruce Fischl" wrote:
p.s. you can ch
p.s. you can check to see if those labels exist in your fsaverage/label
dir
On Tue, 4 Jun 2013, Welsh, Robert wrote:
> ah, that probably got there from the 5.2 recon-all. I'll go in and
> manually change those.
>
> thanks
>
> -robert
>
>
> On 6/4/13 8:59 AM, "Bruce Fischl" wrote:
>
> Hi Robert
>
ok, let us know if it fixes your problem
Bruce
On Tue, 4 Jun 2013, Welsh, Robert
wrote:
> ah, that probably got there from the 5.2 recon-all. I'll go in and
> manually change those.
>
> thanks
>
> -robert
>
>
> On 6/4/13 8:59 AM, "Bruce Fischl" wrote:
>
> Hi Robert
>
> I think you need to symlin
ah, that probably got there from the 5.2 recon-all. I'll go in and
manually change those.
thanks
-robert
On 6/4/13 8:59 AM, "Bruce Fischl" wrote:
Hi Robert
I think you need to symlink the fsaverage dir to the 5.3 fsaverage
instead of 5.2
cheers
Bruce
On Tue, 4 Jun 2013, Welsh, Robert wrote:
Hi Robert
I think you need to symlink the fsaverage dir to the 5.3 fsaverage
instead of 5.2
cheers
Bruce
On Tue, 4 Jun 2013, Welsh, Robert wrote:
Hi,
We were re-processing a subject to test the fix for 5.2 to 5.3. The initial
recon-all and subsequent autrecon2
and autorecon3 were run a few
Hi,
We were re-processing a subject to test the fix for 5.2 to 5.3. The initial
recon-all and subsequent autrecon2 and autorecon3 were run a few days ago under
5.2. Yesterday I installed 5.3 and we ran the following:
export SUBJECTS_DIR=/net/data4/FreeSurferDaze/FreeSurfer
recon-all -s s_ALS51
