Re: [julia-users] early termination of @parallel for code

2014-07-10 Thread Thomas Covert
By the way, I think MATLAB does something like this by default in the parfor infrastructure, so I was kind of surprised @parallel didn't. On Thursday, July 10, 2014 4:18:56 PM UTC-5, Jutho wrote: > > Using random permutations of your original parameter set is a clever idea. > It never even occur

Re: [julia-users] early termination of @parallel for code

2014-07-10 Thread Jutho Haegeman
Using random permutations of your original parameter set is a clever idea. It never even occurred to me when I was trying to find a workaround :-). On 10 Jul 2014, at 23:03, Thomas Covert wrote: > Jutho, I was also worried about this. For that reason, “doset” is a random > permutation of the

Re: [julia-users] early termination of @parallel for code

2014-07-10 Thread Thomas Covert
Jutho, I was also worried about this. For that reason, “doset” is a random permutation of the range 1:nCols, where nCols is the number of columns in “fnmasks" and “dsmasks”. I did this because the workload on the “early” columns is much smaller than the workload on the “later” columns (the fun

[julia-users] early termination of @parallel for code

2014-07-09 Thread Thomas Covert
I'm having trouble debugging some @parallel for code, pasted below. In particular, Julia seems to execute the "saving to disk" code before all of the parallel workers have finished. Why is this? If the details are needed, "dsm" and "fnm" are bool arrays, (theta0,y,X,Ds,M,G,T,Xs) are data no