INSTRUCTIONS
Description
of the task and the proper commands:
This should help users on the windows systems who are not conversant
with the unix language. It is understood that the user knows how to
launch the xwin32 program from his/her windows box. The user can launch
either the kde based version or the basic shell based version. For
speed and efficiency it is recommended to launch the shell
based version. When using large files and computational intensive jobs
there is a good chance the remote connection will lag or sometimes
hangup. For big jobs its recommended to ssh from a linux machine,
submit the job and log out. You should also check the load on the
current machine that you have logged into by using the top command. Check
the CPU% usage and then decide whether to submit the job or move to
another machine.
|
step1
Log into one of the servers
using the xwin 32 tool for windows users.
| <prompt>ssh
-l joeusr mercury.aere.iastate.edu |
step1b
Check to see if there is enough space in /remote/aere directory. This
directory gets filled up pretty often due to heavy load.
<prompt>df
storage.eng.iastate.edu:/export/scratch
88G 77G 6.6G 93%
/remote/scratch
|
|
step2
open
up a shell or from existing shell enter the proper directory. List the
contents of the directory using the ls command and make sure the matlab
code is in the dir.
<prompt>cd directory
<prompt>ls |
|
step4: Launching matlab and stay logged into the machine
launch
matlab without gui, however you will remain logged in while the job runs
launch matlab with gui and remain logged on
|
step5: Launching matlab, executing a code and log out
---> True Batch Process
If the user wishes to launch a matlab program and log out of the server
than a batch process has to inititiated. The matlab program shoud be
launched without the gui! The user should launch the matlab program
without the gui as a background process using the & at th end of
the command. The code is read in through the command as standard input
using the < sign. Any output that would ordinarily go to the screen
should be dumped into a file or into /dev/null where it disappears. If
the output is to be saved then output the file into the scratch dir.
<prompt>nohup
matlab -nojvm < code.m > /dev/null &
|
<prompt>nohup
matlab -nojvm < code.m > /remote/aere/joeuser/output.dat &
|
To check whether the
command has been successful logout of the machine and loh back in the
same way. Then on a prompt test the status of the processes on the
machine
The top command will list all the processes. Look for your user name on
the 2nd column and the coressponding matlab name on the last column
(keep pressing enter). The 1st column contains the process id
To exit the top utility press
CTRL C
|
ATTENTION
If you wish to run more than one batch process simultaneously and the
matlab .m file is saving the data to a file, then each case should save
the data to a new file. In other words each case should be given a new
output file name.
|
step6:Killing a backgroundJob or Process
Its important to know how and when to kill a job. If you decide that
the job submitted is wrong then kill it and resend the corrected case.
As a user you need to excercise this responsibility so that others are
not inconvenienced. See
link for details
<prompt>jobs
<prompt>kill
%[number coressponding to the job]
or
<prompt>top
<prompt>kill
process number |
|