[ Skip to the content ]

Institute of Formal and Applied Linguistics Wiki

[ Back to the navigation ]

You are here: start » grid

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
Next revision Both sides next revision
grid [2017/09/27 21:16]
popel [Advanced usage] 		grid [2017/10/02 16:56]
popel [Advanced usage]
Line 70: Line 70:
   # We have used two handy qsub parameters:   # We have used two handy qsub parameters:
   #  -cwd  ... the script is executed in the current directory (the default is your home)   #  -cwd  ... the script is executed in the current directory (the default is your home)
-  #  -j y  ... stdout and stderr outputs are merged and redirected to a file (''script.sh.o*'')+  #  -j y  ... stdout and stderr outputs are merged and redirected to a file (''script.sh.o$JOB_ID'')
   # We have also provided two parameters for our script "Hello" and "World".   # We have also provided two parameters for our script "Hello" and "World".
   # The qsub prints something like   # The qsub prints something like
Line 148: Line 148:
 ''qsub **-p** -100'' ''qsub **-p** -100''
 Define a priority of your job as a number between -1024 and 0. Only SGE admins may use a number higher than 0. The default is 0, i.e. the highest possible priority. SGE uses the priority to decide when to start which pending job in the queue (it computes a real number called ''prior'', which is reported in ''qstat'', which grows as the job is waiting in the queue). Note that once a job is started, you cannot "unschedule" it, so from that moment on, it is irrelevant what was its priority. Define a priority of your job as a number between -1024 and 0. Only SGE admins may use a number higher than 0. The default is 0, i.e. the highest possible priority. SGE uses the priority to decide when to start which pending job in the queue (it computes a real number called ''prior'', which is reported in ''qstat'', which grows as the job is waiting in the queue). Note that once a job is started, you cannot "unschedule" it, so from that moment on, it is irrelevant what was its priority.
 +
 ''qsub **-o** LOG.stdout **-e** LOG.stderr'' ''qsub **-o** LOG.stdout **-e** LOG.stderr''
-redirect std{out,err} to separate files with given names+redirect std{out,err} to separate files with given names, instead of the defaults ''$JOB_NAME.o$JOB_ID'' and ''$JOB_NAME.e$JOB_ID''.
  
 ''qsub **-@** optionfile'' ''qsub **-@** optionfile''
Line 191: Line 192:
 You can change some properties of already submitted jobs, which are still waiting in the queue (//pending//). You can change some properties of already submitted jobs, which are still waiting in the queue (//pending//).
  
-''**man** qsub qstat qhold queue_conf sge_types complex''+''**man** qsub qstat qalter qhold queue_conf sge_types complex''
 Find out all the gory details which are missing here. You'll have to do it one day anyway:-). Find out all the gory details which are missing here. You'll have to do it one day anyway:-).
  
Line 200: Line 201:
 === qunhold === === qunhold ===
 ''~stepanek/bin/qunhold'' tries to keep the number of running SGE jobs under a given threshold: all jobs over the threshold are held. If the number of running jobs goes below the threshold (default: 100), 10 jobs (by default) are unheld. Beware: if your jobs submit new jobs, you can get far over the threshold! ''~stepanek/bin/qunhold'' tries to keep the number of running SGE jobs under a given threshold: all jobs over the threshold are held. If the number of running jobs goes below the threshold (default: 100), 10 jobs (by default) are unheld. Beware: if your jobs submit new jobs, you can get far over the threshold!
 +
 +=== sshcwd ===
 +This is useful not only when sshing to sol machines. Add the following lines to your ''~/.bashrc''.
 +
 +<code>
 +function sshcwd () {
 +  # save the current history so that it is available
 +  # immediately on the remote machine
 +  history -a;
 +  # setup the working directory by setting WD
 +  ssh -X -Y -C -t $@ "WD='$PWD' /bin/bash --login -i";
 +}
 +
 +# use WD to setup the working directory
 +if [ -n "$WD" ]; then
 +  echo "Autochanging dir to $WD" >&2
 +  cd $WD;
 +fi
 +
 +alias sol1="sshcwd sol1.ufal.hide.ms.mff.cuni.cz"
 +</code>
  
 === In-script options === === In-script options ===

[ Back to the navigation ] [ Back to the content ]