Prev: Error in ginput
Next: Level-2 m-file s-function - dynamic frame data setting
From: Martin Vester-Christensen on 10 Feb 2007 15:02
Hello.

I have recently experienced a problem when trying to submit a job in
the Distributed Toolbox. We are using Sun Grid Engine. Usually a
command like
sched = findResource('scheduler','type','generic') would yield
a MatlabCommandToRun property:

'matlab -dmlworker -nodisplay -r distcomp_evaluate_filetask'

but in the case of matlabr2006b it gives simply
'worker'

For matlab2006a there is no problem

Anyone got any ideas ? Is this a license issue ?

Martin
From: Gaurav Sharma on 10 Feb 2007 23:19

"Martin Vester-Christensen" <mvc(a)NOSPAM.imm.dtu.dk> wrote in message
news:ef4d776.-1(a)webcrossing.raydaftYaTP...
> Hello.
>
> I have recently experienced a problem when trying to submit a job in
> the Distributed Toolbox. We are using Sun Grid Engine. Usually a
> command like
> sched = findResource('scheduler','type','generic') would yield
> a MatlabCommandToRun property:
>
> 'matlab -dmlworker -nodisplay -r distcomp_evaluate_filetask'
>
> but in the case of matlabr2006b it gives simply
> 'worker'
>
> For matlab2006a there is no problem
>
> Anyone got any ideas ? Is this a license issue ?
>
> Martin

Martin:

Please contact our technical support group:
http://www.mathworks.com/support/contact_us/index.html

Thanks


From: Edric M Ellis on 12 Feb 2007 03:01
"Martin Vester-Christensen" <mvc(a)NOSPAM.imm.dtu.dk> writes:
> I have recently experienced a problem when trying to submit a job in
> the Distributed Toolbox. We are using Sun Grid Engine. Usually a
> command like
> sched = findResource('scheduler','type','generic') would yield
> a MatlabCommandToRun property:
>
> 'matlab -dmlworker -nodisplay -r distcomp_evaluate_filetask'
>
> but in the case of matlabr2006b it gives simply
> 'worker'
>
> For matlab2006a there is no problem
>
> Anyone got any ideas ? Is this a license issue ?

Hi Martin,

This was an intentional change - you should find the file "worker" in the
directory $MATLABROOT/bin.

Cheers,

Edric.
From: Martin Vester-Christensen on 12 Feb 2007 03:23
Edric M Ellis wrote:
>
>
> "Martin Vester-Christensen" <mvc(a)NOSPAM.imm.dtu.dk> writes:
>> I have recently experienced a problem when trying to submit a
job
> in
>> the Distributed Toolbox. We are using Sun Grid Engine. Usually
a
>> command like
>> sched = findResource('scheduler','type','generic') would yield
>> a MatlabCommandToRun property:
>>
>> 'matlab -dmlworker -nodisplay -r distcomp_evaluate_filetask'
>>
>> but in the case of matlabr2006b it gives simply
>> 'worker'
>>
>> For matlab2006a there is no problem
>>
>> Anyone got any ideas ? Is this a license issue ?
>
> Hi Martin,
>
> This was an intentional change - you should find the file "worker"
> in the
> directory $MATLABROOT/bin.
>
> Cheers,
>
> Edric.
>

Hi Edric.

Thanks, but there is no worker file in my installation, either linux,
windows or solaris.
Does it come with the Distributed Computing Engine or ?

Martin
From: Edric M Ellis on 12 Feb 2007 04:54
"Martin Vester-Christensen" <mvc(a)NOSPAM.imm.dtu.dk> writes:

> Edric M Ellis wrote:
>> This was an intentional change - you should find the file "worker"
>> in the
>> directory $MATLABROOT/bin.

> Thanks, but there is no worker file in my installation, either linux,
> windows or solaris.
> Does it come with the Distributed Computing Engine or ?

Hi Martin,

That file should be part of the MDCE installation (i.e. it should have been
installed on the cluster when you updated to R2006b there, but not on the client
where it isn't needed).

Cheers,

Edric.
 | 
Pages: 1
Prev: Error in ginput
Next: Level-2 m-file s-function - dynamic frame data setting