That's very strange, it sounds like nothing has changed. Can you please send 
your trac-all.log file?

________________________________
From: freesurfer-boun...@nmr.mgh.harvard.edu 
[freesurfer-boun...@nmr.mgh.harvard.edu] on behalf of Abigail Waters 
[awate...@suffolk.edu]
Sent: Monday, February 13, 2017 2:29 PM
To: Freesurfer support list
Subject: Re: [Freesurfer] -trac-all -prep FS 5.3 Memory Allocation Issue

It's the same. These are all subjects from the same research protocol.
________________________________
From: freesurfer-boun...@nmr.mgh.harvard.edu 
[freesurfer-boun...@nmr.mgh.harvard.edu] on behalf of Yendiki, Anastasia 
[ayend...@mgh.harvard.edu]
Sent: Sunday, February 12, 2017 9:39 PM
To: Freesurfer support list
Subject: Re: [Freesurfer] -trac-all -prep FS 5.3 Memory Allocation Issue

Is the data size different for the new subjects than the old subject? Is the 
spatial resolution or number of directions higher? Or is the acquisition 
exactly the same?

________________________________
From: freesurfer-boun...@nmr.mgh.harvard.edu 
[freesurfer-boun...@nmr.mgh.harvard.edu] on behalf of Abigail Waters 
[awate...@suffolk.edu]
Sent: Friday, February 10, 2017 8:37 PM
To: Freesurfer support list
Subject: Re: [Freesurfer] -trac-all -prep FS 5.3 Memory Allocation Issue

The successfully processed subject was completed using the same FS version 
(5.3) in December. We have not updated to FS 6. The only thing that was altered 
was the directory structure in the dmrirc text file, and the subjects.
Thanks!
Best
Abby
________________________________
From: freesurfer-boun...@nmr.mgh.harvard.edu 
[freesurfer-boun...@nmr.mgh.harvard.edu] on behalf of Yendiki, Anastasia 
[ayend...@mgh.harvard.edu]
Sent: Friday, February 10, 2017 4:34 PM
To: Freesurfer support list
Subject: Re: [Freesurfer] -trac-all -prep FS 5.3 Memory Allocation Issue

Hi Abby – When you say you have successfully processed a subject on that 
machine before, what FS version was that with? What has changed since then? The 
last I remember memory allocation issues, they were years ago in a very old 
version of OSX that we don’t even distribute binaries for any more, so I don’t 
think this is the same problem.

Best,
a.y

From: 
<freesurfer-boun...@nmr.mgh.harvard.edu<mailto:freesurfer-boun...@nmr.mgh.harvard.edu>>
 on behalf of Abigail Waters <awate...@suffolk.edu<mailto:awate...@suffolk.edu>>
Reply-To: Freesurfer support list 
<freesurfer@nmr.mgh.harvard.edu<mailto:freesurfer@nmr.mgh.harvard.edu>>
Date: Friday, February 10, 2017 at 3:05 PM
To: "freesurfer@nmr.mgh.harvard.edu<mailto:freesurfer@nmr.mgh.harvard.edu>" 
<freesurfer@nmr.mgh.harvard.edu<mailto:freesurfer@nmr.mgh.harvard.edu>>
Subject: [Freesurfer] -trac-all -prep FS 5.3 Memory Allocation Issue

Hello -
I'm attempting to run the -trac-all -prep command with FS 5.3. I am running 
into the same memory allocation issues on my Mac that were present in earlier 
versions of Freesurfer/Tracula. See below:

MRIallocSequence (218, 182, 1):could not allocate 158784 bytes for the 44th 
slice
Cannot allocate memory

I have attempted the pre-processing with multiple and single subjects. I have 
successfully processed a single subject on this machine before, and have not 
updated to the latest Freesurfer since that subject (as all MPRAGE scans were 
reconstructed is FS 5.3). There is sufficient memory available and the MPRAGE 
scans were reconstructed correctly.

Any thoughts on how to solve the issue would be appreciated. Please let me know 
if you need any additional information.
Thanks!
Abby

_______________________________________________
Freesurfer mailing list
Freesurfer@nmr.mgh.harvard.edu
https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer


The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.

Reply via email to