9.3.4 Local submission

[D. King]

Hello,
I am currently trying to run the T0 test case using the following parameters in the input file:

10     : numParallelCalcs (how many parallel calculations shall be performed)
1     : whichCluster (0: no-job-script, 1: local submission, 2: remote submission)

I have edited the checkStatus_local.m and submitJob_local.m (attached).

The problem I am getting is that when I run USPEX.m from the command line on the head node.

octave <USPEX.m> log 2>error

It goes through one iteration and stops, the 10 structures are optimised for step 1 but do not continue. If I run the same command:

octave <USPEX.m>>log 2>>error

Uspex goes through a second iteration for step 2 and stops.

Is there a looping problem in the checkStatusC.m or is there a problem at my end?

I have tried for both matlab and octave as well as using a submission script to run USPEX on a node. Also, I can run T0 using "0 : whichCluster" to completion but I believe this method to be less efficient.

log and error files attached.

Regards,
D. King

[huy pham]

Hi,

You can find the thing in the manual,

You need to used the other script that running USPEX every 30 (or any other number you want) minutes

If USPEX found the job is finish, it will submit the new one :)

Try this:

#!/bin/sh
while true
do
  rm -rf still*
  date >> log
  matlab < USPEX.m >> log
  sleep 1200
done

Hope this helps

Huy

--
You received this message because you are subscribed to the Google Groups "USPEX" group.
To unsubscribe from this group and stop receiving emails from it, send an email to uspex+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
Pham Cong Huy
PhD student, Condensed Matter Section
SISSA International School for Advanced Studies
Via Bonomea 265, I- 34136, Trieste, Italy
E-mail:
pchu...@gmail.com
cp...@sissa.it

[D. King]

Thanks Huy, worked well. This seems like a clunky way of doing things though, I might look into a more efficient way.

[Qiang Zhu]

Hi,

You can also insert a crontab to perform the periodic calling matlab jobs, which allows you to switch on/off the job conveniently. But be careful about the configuration. Job in crontab needs to know the exact path for each command, You might need to do something like 'source ~/.bashrc'.

Qiang 

On Wed, Apr 17, 2013 at 2:38 AM, D. King <djm...@gmail.com> wrote:

Thanks Huy, worked well. This seems like a clunky way of doing things though, I might look into a more efficient way.

--
You received this message because you are subscribed to the Google Groups "USPEX" group.
To unsubscribe from this group and stop receiving emails from it, send an email to uspex+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--

Qiang Zhu (Ph.D)
ESS 365
Department of Geosciences
Stony Brook University
NY 11794-2100

USPEX download Page: http://uspex.stonybrook.edu/

[Maurits Boeije]

I know this is an old post, but maybe this is a more elegant way of working:

Append these lines in ev_alg
on line 447: status = 'Finished without errors.'
                  unix(['echo ' status ' >> finished.txt']);
on line 462: status2 = 'Finished with errors.'
                  unix(['echo ' status2 ' >> finished.txt']);

Then create this script:

#!/bin/bash

while [ ! -f finished.txt ]

do
  rm -rf still*
  date >> log

  matlab -nodisplay < USPEX.m >> log &
  sleep 60
done

Op woensdag 17 april 2013 16:20:39 UTC+2 schreef Qiang Zhu: