Path: news.mathworks.com!not-for-mail
From: Edric M Ellis <eellis@mathworks.com>
Newsgroups: comp.soft-sys.matlab
Subject: Re: Creating and Running Jobs with a Local Scheduler
Date: 09 Oct 2008 15:39:01 +0100
Organization: The Mathworks, Ltd.
Lines: 37
Sender: eellis@uk-eellis-deb4-64.mathworks.co.uk
Message-ID: <ytwd4i9hlyy.fsf@uk-eellis-deb4-64.mathworks.co.uk>
References: <gcl2cg$nh$1@fred.mathworks.com>
NNTP-Posting-Host: uk-eellis-deb4-64.mathworks.co.uk
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: fred.mathworks.com 1223563141 4069 172.16.27.249 (9 Oct 2008 14:39:01 GMT)
X-Complaints-To: news@mathworks.com
NNTP-Posting-Date: Thu, 9 Oct 2008 14:39:01 +0000 (UTC)
X-Face: $Ahg}Iylezql"r1WV1Me5&)ng"a4v%D>==KMs-elCfj"o}$bh-VOt7lVXgLWsC?9mZ`mINT
 G6PDvca;nrgs$lfcr0l1ew'N]>nXKl}m|Zpg>,6*gLp~-N0N2*+b.iwv=u>@R$L4SEG&NYUU;lSR@u
 IHphdAy
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.4
Xref: news.mathworks.com comp.soft-sys.matlab:494358


"Mr. CFD" <s2108860@student.rmit.edu.au> writes:

> I am in the process of setting up my machine to eventually submit jobs to a
> cluster through MATLABs Parallel Computing toolbox.
> 
> At the first stage, just to familiarize myself to the process, I have
> attempted to run a job on my local machine through the local scheduler.
> 
> A tutorial is set-up to produce five tasks, where each job generates a 3-by-3 matrix of random numbers.
> ==========================================================
> sched = findResource('scheduler','type','local');
> obj = createJob();

the above line creates a job called "obj" on whatever happens to be your default
scheduler - you should force it to use the scheduler "sched" by doing

obj = createJob( sched );

Other than that, your code looks fine.

> Unfortunately, the simulation continues to display a 'failed' state run, when
> checking the status though: get(obj,'Tasks')

If you still get the problems, one way of getting more information is to check
the "debug log" for a task, like so:

sched.getDebugLog( obj.Tasks(1) )

Posting that output here may help - preferably after executing

setenv( 'MDCE_DEBUG', 'true' );

to give more debug information.

Cheers,

Edric.