-
Notifications
You must be signed in to change notification settings - Fork 0
/
jobTemplate.sbatch
45 lines (45 loc) · 2.27 KB
/
jobTemplate.sbatch
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
#!/bin/bash
#
#all commands that start with SBATCH contain commands that are just used by SLURM for scheduling
#################
#set a job name
#SBATCH --job-name=experimentName-runId
#################
#a file for job output, you can check job progress, append the job ID with %j to make it unique
#SBATCH --output=qaExperiments/experimentName/experimentName-runId.out
#################
# a file for errors from the job
#SBATCH --error=qaExperiments/experimentName/experimentName-runId.err
#################
#time you think you need; default is 2 hours
#format could be dd-hh:mm:ss, hh:mm:ss, mm:ss, or mm
#SBATCH --time=48:00:00
#################
# Quality of Service (QOS); think of it as sending your job into a special queue; --qos=long for with a max job length of 7 days.
# uncomment #SBATCH -p "long" if you want your job to run longer than 48 hours, the default for normal partition,
# NOTE- in the hns partition the default max run time is 7 days , so you wont need to include qos
##SBATCH --qos=long
# We are submitting to the dev partition, there are several on sherlock: normal, gpu, bigmem (jobs requiring >64Gigs RAM)
#SBATCH -p normal
#################
#number of nodes you are requesting, the more you ask for the longer you wait
#SBATCH --nodes=1
#################
# --mem is memory per node; default is 4000 MB per CPU, remember to ask for enough mem to match your CPU request, since
# sherlock automatically allocates 8 Gigs of RAM/CPU, if you ask for 8 CPUs you will need 32 Gigs of RAM, so either
# leave --mem commented out or request >= to the RAM needed for your CPU request.
#SBATCH --mem=4000
#################
# Have SLURM send you an email when the job ends or fails, careful, the email could end up in your clutter folder
# Also, if you submit hundreds of jobs at once you will get hundreds of emails.
#SBATCH --mail-type=END,FAIL # notifications for job done & fail
# Remember to change this to your email
#SBATCH --mail-user=jasonf2@stanford.edu
#now run normal batch commands
# note the "CMD BATCH is an R specific command
# You can use srun if your job is parallel
#srun R CMD BATCH ./rtest.R
# or
# srun R --no-save < rtest.R
# otherwise:
webppl --require webppl-json --require webppl-fs --require webppl-csv --require . qaExperiments/experimentName/experimentName.wppl runId