User Tools

Site Tools


using_perun

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
using_perun [2019/09/30 10:14] 129.173.90.41using_perun [2021/09/08 13:29] (current) 134.190.232.139
Line 139: Line 139:
 **qsub -q 144G-batch name_of_script** (nodes with 144 GB RAM, 24 slots per node (1)) **qsub -q 144G-batch name_of_script** (nodes with 144 GB RAM, 24 slots per node (1))
 **qsub -q 16G-batch name_of_script** (nodes with 16 GB RAM, 8 slots per node (12)) **qsub -q 16G-batch name_of_script** (nodes with 16 GB RAM, 8 slots per node (12))
-**qsub -q 256G0batch name_of _script**  (nodes with 256 GB RAM, 48 slots per node (2))+**qsub -q 256G-batch name_of _script**  (nodes with 256 GB RAM, 48 slots per node (2))
  
  
Line 154: Line 154:
 This will list all the jobs currently being run on perun as well as who is logged in. To just see your jobs This will list all the jobs currently being run on perun as well as who is logged in. To just see your jobs
  
 +you would normally do qstat -u username but for some reason that doesn't work on perun so do
  
 **qstat | grep username** **qstat | grep username**
 +
 +or 
 +
 +**watch qstat** (control c to exit).
 +
 +
  
  
Line 239: Line 246:
  eg blastn -help  eg blastn -help
 4. If all else fails you can try and read the program code (if it is in perl or python as opposed to  C or C++) and try and figure out what the authors want. 4. If all else fails you can try and read the program code (if it is in perl or python as opposed to  C or C++) and try and figure out what the authors want.
- 
using_perun.1569849296.txt.gz · Last modified: by 129.173.90.41