This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
archive:computer_resources:campusrocks [2015/04/13 18:55] ceisenhart |
archive:computer_resources:campusrocks [2015/04/18 20:29] charles |
||
---|---|---|---|
Line 90: | Line 90: | ||
#$ -l mem_free=15g\\ | #$ -l mem_free=15g\\ | ||
Your job goes to a node with at least 15g of free memory. There is probably something like '-l mem_avail' that works if you would like to schedule your job on a node with a certain amount of max memory available, even if some of it is currently in use. | Your job goes to a node with at least 15g of free memory. There is probably something like '-l mem_avail' that works if you would like to schedule your job on a node with a certain amount of max memory available, even if some of it is currently in use. | ||
+ | |||
+ | #$ -pe mpi 4\\ | ||
+ | Your job goes to a set of nodes with a combined total of a least 4 cores available. | ||
+ | |||
+ | #$ -cwd\\ | ||
+ | Your job will be launched at the directory where the qsub command was given. Useful for setting predictable bash commands. Though not recommended for portability as other users of the script would need to also know where to launch the qsub command. | ||