Child pages
  • Getting started on Prince
Skip to end of metadata
Go to start of metadata

Under Construction

This page is under construction


Logging in to Prince

Logging in to Prince is the same 2-stage process as logging into to any other NYU HPC cluster. The host name is ''.
The HPC cluster Prince is not directly visible to the internet (outside the NYU Network). If you are outside NYU's Network (off-campus) you must first login to a bastion host named
The diagram below illustrates the login path.


NOTE: The clusters can still access the internet directly. This may be useful when copying data from servers outside the NYU Network - see: How to copy files to and from the HPC clusters.
NOTE: Alternatively, instead of login to the bastion host, you can use VPN to get inside NYU's network and access the HPC clusters directly. Instructions on how to install and use the VPN client are available here.
NOTE: You can't do anything on the bastion host, except ssh to the HPC clusters.

Adding Prince to your SSH Tunnel

On a Mac:

# first we create the tunnel, with instructions to pass incoming
# packets on ports 8020, 8021 and 8022 through it and to specific
# locations
Host hpctunnel

User NetID
# Add a line like this: if you are already using 8023, choose another number:
LocalForward 8023 

# next we create an alias for incoming packets on port 8023. The
# alias corresponds to where the tunnel forwards these packets
# Add an entry like this. The port number must match the one used above:
Host prince
HostName localhost
Port 8023
ForwardX11 yes
User NetID

For Windows, the text you must add is indicated in bold on this page.

Filesystems on Prince

The table below shows the File Systems available on the Prince Cluster.  

File systems listed in green font will be available in the future.


Storage Capacity

(User Quota)

FS TypeBacked up?Flushed?AvailabilityVariableValue

43 TB

(20 GB / user)

ZFSYesNoAll Prince nodes (login, compute)

1.1 PB

(5 TB / user)



Files unused for 60 days are deleted

All Prince nodes (login, compute)


(2 TB / user)

BeeGFSNOTBDAll Prince nodes (login, compute)

700 TB

(2 TB / user)

ZFSYesNoOnly the login nodes
/state/partition1Varies, mostly >100GBext3NO


at the end of each job

Separate local filesystem on each compute node$SLURM_JOBTMP/state/partition1/$SLURM_JOBID

Transferring files to Prince

Your files on /scratch are visible on Prince as well as Mercer, and will remain such.

Moving many small files takes significantly longer than moving one large file. Therefore, to transfer source code with many small files from /home on another cluster, we recommend tarring up the source directory first.

We recommend rebuilding all models on Prince - this will ensure the best performance and also avoid any problems relating to mismatched OS and library versions between the clusters. Therefore, there is no need to transfer object files or executables.

How to migrate from another cluster to Prince

If you have a workflow on Mercer, and you wish to replicate it on Prince:

  1. Ensure the files you need are available on Prince
    Files on $SCRATCH are already available on Prince - there is nothing you need to do with these.

  2. You will need to rewrite your scripts to convert them from using PBS to using Slurm Job Scheduler. If you are having any questions or issues,  contact us for help.

  3. Check your .bashrc and .bash_profile files. If on the older cluster, you loaded certain modules in them, you may wish to add corresponding lines to those files on Prince. You may also wish to replicate your shell aliases.

  4. If you are running a model you compiled yourself, you will probably get improved performance by recompiling the model on Prince. See below for more about compiling code.


Compiling Code on Prince

We recommend using the Intel compiler suite (module load intel), and, for MPI programs, OpenMPI (module load openmpi/intel).

The GNU compiler suite is also available (module load gcc) and over time other compiler versions and MPI implementations will be installed. There will be instances in which an alternative compiler or MPI library performs better or avoids a bug in the recommended compilers, but in the long run the functionality and performance of compilers and MPI libraries is very similar, so for easiest maintenance, only use the alternatives if you really need to.

If you are building software to use for many or long-running jobs, testing for performance with a few MPI libraries and compile options can be very valuable since a specific model might run noticeably faster under one MPI implementation than another.

Submitting batch jobs on Prince

Unlike Mercer, Prince cluster uses Slurm Job Scheduler, a resource manager designed to allocate compute resources and schedule jobs. Due to the nature of HPC clusters we recommend writing a batch script, rather than running interactive commands.

There are two aspects to a batch job script:

  • A set of SBATCH directives describing the resources required and other information about the job 
  • The script itself, comprised of commands to setup and perform the computations without additional user interaction

Jobs are submitted with the sbatch command:


$ sbatch options job-script

The options tell SLURM information about the job, such as what resources will be needed. These can be specified in the job-script as SBATCH directives, or on the command line as options, or both (in which case the command line options take precedence should the two contradict each other). For each option there is a corresponding SBATCH directive with the syntax: #SBATCH option You can find a list of sbatch options here.


Interactive sessions

To start an interactive batch session, use:

If you need a GUI, you should use:

By default single CPU core and 2GB memory are allocated to your job for 1 hour. You can explicitly request more CPUs and more memory with the following options:

The above command requests 4 compute nodes for 2 hours with 4 Gb of memory.

Most nodes have either 64GB, 128GB, 192GB or 256GB of memory. However, some amount of memory is also needed by the operating system, so nodes have about 62GB, 124GB, 189GB and 250GB available for jobs. If you request 128GB, you restrict the job to the subset of nodes having more than 128GB of memory, and it will probably take longer to schedule.

GPU Jobs

In Prince cluster, there are currently 9 GPU nodes. Each of the nodes is equipped with 4 Tesla K80 cards.

| NVIDIA-SMI 367.48                 Driver Version: 367.48                    |
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|   0  Tesla K80           On   | 0000:04:00.0     Off |                    0 |
| N/A   22C    P8    26W / 149W |      0MiB / 11439MiB |      0%   E. Process |
|   1  Tesla K80           On   | 0000:05:00.0     Off |                    0 |
| N/A   28C    P8    30W / 149W |      0MiB / 11439MiB |      0%   E. Process |
|   2  Tesla K80           On   | 0000:84:00.0     Off |                    0 |
| N/A   20C    P8    26W / 149W |      0MiB / 11439MiB |      0%   E. Process |
|   3  Tesla K80           On   | 0000:85:00.0     Off |                    0 |
| N/A   29C    P8    30W / 149W |      0MiB / 11439MiB |      0%   E. Process |
To request one GPU card, use the Slurm directive:

#SBATCH --partition=gpu
#SBATCH --gres=gpu:1

Software on Prince

Prince uses the same Environment Modules setup as Mercer. Not all software from Mercer is on Prince yet. Please check the availability of the module you need with:

$ module avail

Different versions of software may give slightly different results, especially if your model is numerically sensitive! Please carefully check the results of simulations on Prince and compare them to results on the cluster you used previously!