Wednesday, October 1, 2014 7:07 PM
- If doing something that does not require much CPU time or memory, you can work on the login node. Otherwise, you should work on a compute node (see below).
- If anything you're running involves a lot of input/output, you should use your
/scratch/YourNetIdHeredirectory to store files rather than your
From Applications Menu
Several software packages with graphical user interfaces are available from the Applications Menu when you connect to BlueHive using X2Go. If the one you want to use is among them,
- Select the package you want from the menu. A JobLauncher window will come up.
- You can run on the login node by checking
Run on Bluehive.Otherwise, leave unchecked to run on a compute node.
- Optional: select options for duration, number of nodes, etc.
Submit Interactive job. If on a compute node you might have to wait for your job to start.
From an interactive session at the command line
- Open a terminal from the Applications menu (
Applications -> System Tools -> Terminal)
- Commands typed in the new terminal window will run on the login node. To run on a compute node, type
interactive. You might have to wait for your job to start. After it starts you will get a command prompt on a compute node.
- Find the software package you want to use from the Software Index. Then select the module name corresponding to the particular version you want. For example, for the R software package used for statistical analysis, you could select
r/3.1.0/b2. If the package or version you need is not installed, email us and we will install it.
- Find the name of the executable or command to run. You might need to look at the documentation for the software package to find this.
- In the terminal window, type
module load YourModuleNameHere YourCommandHere
For example, for R,
On a compute node, non-interactively, using an
First, make sure you know the command for running your software non-interactively (using an input file, etc.) It's a good idea to first run a small test case on the login node. For example, for R, a very simple input file is just the line
1+1. Say this line is saved in a file called
test.R(to create the file you can use
Applications -> Accessoriesmenu). The command to run R using that input file is then
R --no-save < test.R.
Create another file containing the lines
#!/bin/bash #SBATCH --time=00:05:00 --output=test.out module load YourModuleNameHere YourCommandHere
Again, for R,
R --no-save < test.R. Say these lines are saved in a file called
Submit the job by typing
sbatch test.sbatch. You can look at the status of this job (and all the jobs you are running) by typing
squeue -u YourNetIdHere. In particular the fourth column with heading
STgives the status of the job:
Rfor running, or
CDfor completed (these are the most common but there are others). After the job has completed the file
test.outwill contain the output.
- There are many options to customize how your job is run. See Running Jobs or type
man sbatchin a terminal for more information.