Hi Aziz
freeview is the tool for visualizing the data, so use it to examine the
outputs of recon-all and figure out what is causing the big defect
cheers
Bruce
On Thu,
12 Jan 2017, Aziz Nanthaamornphong wrote:
Hi Bruce,
So, I should run the freeview after got those error messages. I will
Hi Bruce,
So, I should run the freeview after got those error messages. I will try.
Thank you,
Aziz.
On Thu, Jan 12, 2017 at 10:32 PM, Bruce Fischl
wrote:
> Hi Aziz
>
> it will be in the subject's surf dir. You can visualize it via:
>
> freeview -f $SUBJECTS_DIR//surf/lh.inflated.nofix
>
>
>
Hi Aziz
it will be in the subject's surf dir. You can visualize it via:
freeview -f $SUBJECTS_DIR//surf/lh.inflated.nofix
cheers
Bruce
On Thu, 12
Jan 2017, Aziz Nanthaamornphong wrote:
Hi Bruce,
How can I look at inflated.nofix as you mentioned? I think I ran recon-all
for the 001.mgz wi
Hi Bruce,
How can I look at inflated.nofix as you mentioned? I think I ran recon-all
for the 001.mgz without other files.
Best Regards,
Aziz.
On Thu, Jan 12, 2017 at 8:55 PM, Bruce Fischl
wrote:
> Hi Aziz
>
> yes, you ran out of RAM. That said, a defect with 66K vertices is pretty
> big - more
Hi Aziz
yes, you ran out of RAM. That said, a defect with 66K vertices is pretty
big - more than 1/3 of a typical surface. You should check to make sure
nothing big is wrong (hemis attached, skull left around, etc). Look
at the inflated.nofix surface and it should be obvious what the defec
Hi experts,
I ran the command
$recon-all -all -subjid 0696
I have got these error messages
*CORRECTING DEFECT 46 (vertices=66623, convex hull=8931)*
*Excessive topologic defect encountered: could not allocate 322592700 edges
for retessellation*
*Cannot allocate memory*
*Linux xubuntu-VirtualB
