Changes between Version 27 and Version 28 of cypress/using


Ignore:
Timestamp:
08/19/15 11:50:33 (9 years ago)
Author:
cmaggio
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • cypress/using

    v27 v28  
    6363With our SLURM script complete, we’re ready to run our program on the cluster. To submit our script to SLURM, we invoke the '''sbatch''' command. Suppose we saved our script in the file helloworld.srun (the extension is not important). Then our submission would look like:
    6464
     65{{{#!comment
    6566[[Image(sbatch.png, 50%, center)]]
     67}}}
     68
     69{{{
     70[tulaneID@cypress1 ~]$ sbatch helloworld.srun
     71Submitted batch job 6041
     72[tulaneID@cypress1 ~]$
     73}}}
    6674
    6775Our job was successfully submitted and was assigned the job number 6041. We can check the output of our job by examining the contents of our output and error files. Referring back to the helloworld.srun SLURM script, notice the lines
    … …  
    7482These specify files in which to store the output written to standard out and standard error, respectively. If our code ran without issue, then the Hi.err file should be empty and the Hi.out file should contain our greeting.
    7583
     84{{{#!comment
    7685[[Image(Hi_output.png, 50%, center)]]
     86}}}
     87{{{
     88[tulaneID@cypress1 ~]$ cat Hi.err
     89[tulaneID@cypress1 ~]$ cat Hi.out
     90Hello World
     91[tulaneID@cypress1 ~]$
     92}}}
    7793
    7894There are two more commands we should familiarize ourselves with before we begin. The first is the “squeue” command. This shows us the list of jobs that have been submitted to SLURM that are either currently running or are in the queue waiting to run. The last is the “scancel” command. This allows us to terminate a job that is currently in the queue. To see these commands in action, let's simulate a one hour job by using the sleep command at the end of a new submission script.