A follow up, in case anyone else encounters thread-related bugs: It
*appears* that this error was resolved by adding the line
maxNumCompThreads(4);
to *startup.m*
stephen
*stephen v. shepherd phd*
The Rockefeller University / 1230 York Avenue / New York NY 10065-6307 USA
// 212.327.7699
On
sorry, I have no idea
On 05/19/2016 11:35 AM, S.V.Shepherd [work] wrote:
> It happens when I run more than 3-4 analyses at once. It appears to be
> sensitive to other instances of Matlab being open. however, I don't
> see clear evidence I'm memory limited. for example, I'm currently
> running
It happens when I run more than 3-4 analyses at once. It appears to be
sensitive to other instances of Matlab being open. however, I don't see
clear evidence I'm memory limited. for example, I'm currently running four
selxavg in parallel, along with a separate melodic analysis. One more would
Does it always die like that? It may be out of memory.
On 05/18/2016 01:50 PM, S.V.Shepherd [work] wrote:
> Hello,
>
> When running more than 3 analyses in parallel in FreeSurfer 5.3, I am
> getting matlab crashes. Mathworks has politely declined to provide
> support unless I can replicate
sounds like you are running out of memory, no?
On Wed, 18 May 2016,
S.V.Shepherd [work] wrote:
Hello,
When running more than 3 analyses in parallel in FreeSurfer 5.3, I am
getting matlab crashes. Mathworks has politely declined to provide support
unless I can replicate outside FsFAST.
The
