Changes between Version 49 and Version 50 of cypress/using


Ignore:
Timestamp:
Aug 25, 2016 1:08:32 PM (6 years ago)
Author:
fuji
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • cypress/using

    v49 v50  
    6060
    6161Notice that the SLURM script begins with #!/bin/bash. This tells the Linux shell what flavor shell interpreter to run. In this example we use BASh (Bourne Again Shell). The choice of interpreter (and subsequent syntax) is up to the user, but every SLURM script should begin this way. This is followed by a collection of #SBATCH script directives telling the manager about the resources needed by our code and where to put the codes output. Lastly, we have the executable we wish the manager to run (note: this script assumes it is located in the same directory as the executable).
     62
     63'''For Workshop''' :
     64If you use a temporary workshop account, modify the script like:
     65{{{#!bash
     66#!/bin/bash
     67#SBATCH --job-name=HiWorld    ### Job Name
     68#SBATCH --output=Hi.out       ### File in which to store job output
     69#SBATCH --error=Hi.err        ### File in which to store job error messages
     70#SBATCH --partition=workshop    # Partition
     71#SBATCH --qos=workshop          # Quality of Service
     72##SBATCH --qos=normal          ### Quality of Service (like a queue in PBS)
     73#SBATCH --time=0-00:01:00     ### Wall clock time limit in Days-HH:MM:SS
     74#SBATCH --nodes=1             ### Node count required for the job
     75#SBATCH --ntasks-per-node=1   ### Nuber of tasks to be launched per Node
     76
     77./helloworld
     78}}}
     79
    6280
    6381With 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:
     
    287305`idev` transfers the environmental variables to computing node. Therefore, if you have loaded some modules on the login node, you don't have to load the same module again.
    288306
     307==== For Workshop ====
     308If you use a temporary workshop account, do this.
     309{{{
     310export MY_PARTITION=workshop
     311export MY_QUEUE=workshop
     312}}}
    289313
    290314==== Options ====