User Tools

Site Tools


pbs-dummies

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Last revisionBoth sides next revision
pbs-dummies [2011/08/25 16:18] damirpbs-dummies [2011/11/01 13:03] damir
Line 10: Line 10:
  
 The mandatory directives that you must **always** include in the scripts are: The mandatory directives that you must **always** include in the scripts are:
-  - Your email address. the official epfl address or something else, but must be a valid (worldwide) email address. This address mus be always present, no matter if you instruct the system to send or not the email messages.+  - Your email address. the official epfl address or something else, but must be a valid (worldwide) email address. **This address mus be always present, no matter if you instruct the system to send or not the email messages**.
   - How much time your job must run (if the job runs over this limit the cluster manager will kill it). the minimum is 1 minute and there's no maximum limit.   - How much time your job must run (if the job runs over this limit the cluster manager will kill it). the minimum is 1 minute and there's no maximum limit.
   - How much memory (RAM) your job will use. Please remember that if your job use more memory than the limit you put here the cluster manager will kill the job. the minimum is 512 Mbyte, currently (as for Dec 2010) the maximum is ~64 Gbyte.   - How much memory (RAM) your job will use. Please remember that if your job use more memory than the limit you put here the cluster manager will kill the job. the minimum is 512 Mbyte, currently (as for Dec 2010) the maximum is ~64 Gbyte.
Line 24: Line 24:
 </code> </code>
  
-After this then you can add directives for instructing the system about the messages you+After this //prolog// you can add directives for instructing the system about the messages you
 want to receive: want to receive:
  
Line 35: Line 35:
 </code> </code>
  
-Also you can tell the PBS where you want to put the output and errors messages. By default the cluster will put the output and errors messages in 2 separate files (<name of the job>.e<jobID> and <name of the job>.o<jobID>), but maybe you prefer to have all these messages in one single file (<name of the job>.o<jobID>)+Also you can tell the PBS where you want to put the output and errors messages. By default the cluster will put the output and errors messages in 2 separate files (<name of the job>.e<jobID> for errors and <name of the job>.o<jobID> for the output), but maybe you prefer to have all these messages in one single file (<name of the job>.o<jobID>)
  
 <code> <code>
Line 42: Line 42:
 </code> </code>
  
-And then you want to assign a name to your job, so you can know what the cluster is doing for you when you look at the list of running jobs (using the command ''qstat -an1'').+And then you want to assign a name to your job, so you will know what the cluster is doing for you when you look at the list of running jobs (using the command ''qstat -an1'').
  
 <code> <code>
Line 66: Line 66:
 </code> </code>
  
-Another thing to remember is that the output files (the ...o<jobID> and ....e<jobID>) created by the PBS system are placed inside the directory **from where you submitted the job**, not inside the directory from where the program is launched by the script (in other words all the "cd ..." directives inside the script doesn'matter for the queue manager).+Another thing to remember is that the output files (the ...o<jobID> and ....e<jobID>) created by the PBS system are placed inside the directory **from where you submitted the job**, not inside the directory from where the program is launched by the script (in other words all the "cd ..." directives inside the script aren'considered by the queue manager).
  
 Once we attach all the lines from above we'll have a script that will look like this: Once we attach all the lines from above we'll have a script that will look like this:
Line 99: Line 99:
  
 <note> <note>
-If you like, you can use the absolute path to indicate the script to launch, but **remember** that the output files will be written inside the directory from where you executed the qsub program.+If you like, you can use the absolute path to indicate the script to launch, but **remember** that the output files will be written inside the directory from **where** you executed the qsub program.
 </note> </note>
  
-After all this work, you just need to relax and wait until you receive the email messages from the queuing manager. At this point you return to the directory where the output files are saved and you can check the results.\\ +After all this work, you just need to relax and wait until you receive the email messages from the queuing manager. At this point you return to the directory where the output files are saved and check the results.\\ 
-If you browse the the documentation we have on [[sge|Batch Queuing System]] you'll find examples on how to use Matlab or Mathematicasome explanation about the directives and the commands available for use the queuing system.+If you browse the the documentation we have on [[sge|Batch Queuing System]] you'll find examples on how to use Matlab or Mathematica and some explanation about the directives and the commands available for the queuing system.
  
pbs-dummies.txt · Last modified: 2015/11/16 10:33 by 127.0.0.1