.. index::
      pair: Running Jobs; Index

.. _running-jobs: 

======================
Running jobs on midway
======================

This section of the RCC User Guide is about running computations on
the RCC cluster, Midway. All jobs running on compute nodes consume
Service Units (SUs); see `RCC Service Units`_ for more information.

Login nodes vs. compute nodes
=============================

Once you have connected to Midway (see :ref:`connecting`), you may
work on one of the login nodes. Login nodes may be used for compiling
and debugging code, installing software, editing and managing files,
submitting jobs, or any other work that is not long-running or
computationally intensive. *Login nodes should not be used for
computionally intensive work.*

All intensive computations should be performed on compute
nodes. Access to compute nodes can be obtained by submitting a job
through the Slurm scheduler, or by requesting an interactive session
(see :ref:`using-midway`). If you are unsure whether your computations
will be intensive, please request an interactive session and continue
your work once you have connected to the compute node.

.. note::

   Running computationally intensive jobs on the Midway login nodes
   prevents other users from efficiently using the cluster. RCC System
   Administrators may terminate your processes without warning if your
   processes disrupt other users' work on the RCC cluster.

For more information on how to interact with Midway through the Slurm
resource manager, see :ref:`using-midway`.

Illustrative examples
=====================

Below are a number of example submission scripts that you can adapt to
run your jobs on Midway. See also the materials from the
`RCC Slurm workshop <https://github.com/rcc-uchicago/SLURM_WORKSHOP>`_ 
for additional examples.

.. toctree::
   :maxdepth: 1
   :glob:

   bigmem/index
   array/index
   gpu/index
   mpi/index
   hybrid/index
   srun-parallel/index 
   cron/index