I have sent the attachment mentioned in the mail below via mail drop.
On Thu, Feb 28, 2013 at 4:28 PM, Blessy M wrote:
> The skull stripped image using FS did not look very good, I am not sure if
> this was the result of skullt stripping or the fact that the volume was
> more than 2
) :
difference with theory (-53) = -51
CORRECTING DEFECT 22 (vertices=39536, convex hull=7215)
Help!
On Wed, Feb 27, 2013 at 11:37 AM, Blessy M wrote:
>
> 1. It is not contrast enhanced.
>
> 2. I am rerunning recon-all after giving it a manually skull stripped
> image. Hopefully
sed them in the past.
>
> 2. I think the skull stripping removed some brain tissue, which may be the
> source of your large defects. Can you please check it and get back to us?
> This also might be due to the contrast enhancement.
>
> cheers
>
> Bruce
>
>
> On Tue,
I should have send it with an extension. But it is tiff, just as you asked.
On Tue, Feb 26, 2013 at 3:03 PM, Bruce Fischl wrote:
> Hi Blessy
>
> what format is this? If you don't send it with an extension there is no
> way to know
> Bruce
>
> On Tue, 26 Feb 2013, B
e, 26 Feb 2013, Blessy M wrote:
>
> Yes it is still at defect 32.
>>
>> The tail of the recon-all.log is as follows:
>>
>> CORRECTING DEFECT 30 (vertices=18, convex hull=22)
>> After retessellation of defect 30, euler #=-7 (59491,172395,112897) :
>> difference
on defect 32? What does the tail of the recon-all.log say? And
> can you send us an image of the lh.inflated.nofix (if it is the lh that is
> running)?
>
>
> On Tue, 26 Feb 2013, Blessy M wrote:
>
> I verified lh.orig.nofix, and it looks fine. But, there has been no ne
ing is dramatically wrong (like skull
> attached to brain, or hemis connected, etc)
>
> On Mon, 25 Feb 2013, Blessy M wrote:
>
> Recon is still running. I started the process on 2/21/2013. Its been 4
>> days.
>>
>> I ran this command, and viewed the aseg fil
ngs that occur
> pretty frequently and I don't think should impact the results. Does the
> recon finish? Do the results look ok?
>
>
> On Fri, 22 Feb 2013, Blessy M wrote:
>
>
>> I am getting the bottom two sets of errors while doing a simple recon-all.
>>
&
I am getting the bottom two sets of errors while doing a simple recon-all.
More specifically while running this command:
recon-all -subjid . -noskullstrip -autorecon1 -notal-check -autorecon2
-autorecon3
Has someone encountered this kind of errors? Is there a fix?
1)
Computing MAP estimate using
ect (vertices=27939). Can you check the
> ?h.orig.nofix and see if anything is dramatically wrong with it? Is the
> skull attached? The cerebellum? If you upload it we can certainly take a
> look
>
> cheers
> Bruce
>
> On Mon, 17 Sep 2012, Blessy M wrote:
>
> Does any
Does anyone have any suggestions on what might have gone wrong here? Should
I send the image?
On Fri, Sep 14, 2012 at 3:14 PM, Blessy M wrote:
> No, the cerebellum is not attached.
>
> On Fri, Sep 14, 2012 at 1:42 PM, Blessy M wrote:
>
>> I have a MPRAGE scan, with slight atr
No, the cerebellum is not attached.
On Fri, Sep 14, 2012 at 1:42 PM, Blessy M wrote:
> I have a MPRAGE scan, with slight atrophy on right side of brain.
> Recon-all is crashing (see error below). Can anyone help me with this, so I
> can get a reasonably parcellated brain?
>
>
I have a MPRAGE scan, with slight atrophy on right side of brain. Recon-all
is crashing (see error below). Can anyone help me with this, so I can get a
reasonably parcellated brain?
*CORRECTING DEFECT 6 (vertices=151, convex hull=90)
After retessellation of defect 6, euler #=-52 (54998,159712,104
13 matches
Mail list logo
