NERSCPowering Scientific Discovery Since 1974

Running jobs

We are in the process of moving this page to its another location

However, all the contents under this page are still maintained and up to date. 


A brief overview of how to run jobs on Edison. Read More »

Interactive Jobs

Interactive jobs may be run on Edison by requesting resources from the batch system. "salloc -q debug -N " is the basic command to request interactive resources. Read More »

Batch Jobs

Batch script options. Read More »

Edison Queues and Policies

Users submit jobs to a QOS (Quality of Service) and wait in line until nodes become available to run a job. NERSC's queue structures are intended to be fair and to allow jobs of various sizes to run efficiently. Note that the intended use of each system differs. Edison's purpose is to run large jobs, so the queue policy significantly favors large jobs using more than 682 nodes. If your workload requires smaller jobs (using less than 682 nodes), we encourage you to run on Cori Phase I, which… Read More »

Using OpenMP with MPI

This page describes how to compile and rum hybrid MPI/OpenMP applications. Read More »

Memory Considerations

Here's what you can do if you run out of memory. Read More »

How Usage Is Charged

When a job runs on a NERSC MPP system charges accrue against one of the user's repository allocations. Read More »

Shared and Dynamic Libraries

By default the Edison system runs a limited OS kernel which does not support shared and dynamic libraries. However, users can enable shared libraries on be setting an environment variable. Read More »

Example Batch Scripts

Sample batch scripts for MPI, OpenMP, hybrid applications and various workflows. Read More »