for Researchers & Teams

Run R Scripts on the Cluster

You can use SESYNC’s RStudio Server to submit jobs to our cluster and view the resulting output. In the following example, you will learn how to:

Once you are familiar with the process shown here, you may want to check our examples of the different ways to run code in parallel on the cluster:

1. Create a simple R script

Before you begin, download the example data file from Data Carpentry at . Place it in your current directory. The file contains observations on the weight of several species of small mamals across 24 survey plots.


Create a script to run some analyses on the data. The script below reads the data into R, calculates basic statistics on the observed weight of each species then creates a bar chart of the mean in a pdf. Only rows with complete data are used.

surveys <- read.csv('surveys.csv')
surveys_complete <- surveys[complete.cases(surveys), ]

surveys_complete$species <- factor(surveys_complete$species)
species_mean <- tapply(surveys_complete$wgt, surveys_complete$species, mean)
species_max <- tapply(surveys_complete$wgt, surveys_complete$species, max)
species_min <- tapply(surveys_complete$wgt, surveys_complete$species, min)
species_sd <- tapply(surveys_complete$wgt, surveys_complete$species, sd)
nlevels(surveys_complete$species) # or length(species_mean)
surveys_summary <- data.frame(species=levels(surveys_complete$species),

2. Create a job submission script

In addition to the R script you want to run, you need to create a seperate submission script that instructs the cluster how to run your R script.

Q. Why can’t you directly submit your R script?

A. The cluster is able to run many different types of code and doesn’t have an innate awareness of the specific language used in any particular analysis script that’s submitted. Therefore, you must tell the cluster how to run your code. The script we are about to create provides these instructions.

In the same folder you created your plot.R file, create a submission script called This submission script is a short shell script that instructs the scheduler which settings to use and lists the commands necessary to run your R script. The example below tells the scheduler that a single task will run and that it should process the plot.R script file using the Rscript command.


Rscript --vanilla plot.R

Here’s what the script is doing:

3. Run your job

In the RStudio “Console”, submit your job to the cluster by typing:


Note that the system will return a message with the job number for your submission. This is a unique number on the scheduler that can be used to track information about the status of your job. This is particularly useful for jobs that may take a long time to run.

> system("sbatch")
Submitted batch job 76

After you submit this job, it should finish in a few seconds. Click the refresh button in the RStudio “Files” window, and you should see a few new files.

4. Modify your scripts to run more than once

If you look at the script above, you’ll notice that a problem arises when you want to run this file multiple times. The way its currently written, it will overwrite the pdf output each time it is run. To prevent this, we can append the unique SLURM job number to the name of the file.

The scheduler provides environment variables you can use for this purpose. We will modify the pdf command (third to last line) of the plot.R script to read as follows:

pdf(paste0("mean_per_species_", Sys.getenv("SLURM_JOB_ID"),".pdf"))

Once you’re finished you can re-submit your script using sbatch as you did before. When the script finished, you’ll notice that the PDF file is now called “mean_per_species_XX.pdf”, where XX is the job number.


R 25