Skip to content
Snippets Groups Projects
Verified Commit 2aa945a0 authored by Adam Caprez's avatar Adam Caprez
Browse files

Update "Submitting an Interactive Job" page.

parent 3e679466
No related branches found
No related tags found
1 merge request!18Update Submitting Jobs section.
1. [HCC-DOCS](index.html)
2. [HCC-DOCS Home](HCC-DOCS-Home_327685.html)
3. [HCC Documentation](HCC-Documentation_332651.html)
4. [Submitting Jobs](Submitting-Jobs_332222.html)
<span id="title-text"> HCC-DOCS : Submitting an Interactive Job </span>
=======================================================================
Created by <span class="author"> Derek Weitzel</span>, last modified by
<span class="editor"> Adam Caprez</span> on Sep 14, 2018
<span
class="aui-icon aui-icon-small aui-iconfont-error confluence-information-macro-icon"></span>
+++
title = "Submitting an Interactive Job"
description = "How to run an interactive job on HCC resources."
+++
{{% notice info %}}
The `/home` directories are read-only on the worker nodes. You will need
to compile or run your processing in `/work`.
{{% /notice %}}
Submitting an interactive job is done with the command `srun`.
``` syntaxhighlighter-pre
{{< highlight bash >}}
$ srun --pty $SHELL
```
{{< /highlight >}}
or to allocate 4 cores per node:
``` syntaxhighlighter-pre
{{< highlight bash >}}
$ srun --nodes=1 --ntasks-per-node=4 --mem-per-cpu=1024 --pty $SHELL
```
{{< /highlight >}}
Submitting an interactive job is useful if you require extra resources
to run some processing by hand. It is also very useful to debug your
......@@ -35,34 +28,25 @@ And interactive job is scheduled onto a worker node just like a regular
job. You can provide options to the interactive job just as you would a
regular SLURM job.
Priority for short jobs
-----------------------
### Priority for short jobs
To run short jobs for testing and development work, a job can specify a
different quality of service (QoS). The *short* QoS increases a jobs
priority so it will run as soon as possible.
| <span style="color: rgb(0,51,102);">SLURM Specification</span> |
|----------------------------------------------------------------|
| `--qos=short` |
Limits per user for 'short' QoS
<span
class="aui-icon aui-icon-small aui-iconfont-warning confluence-information-macro-icon"></span>
| SLURM Specification |
|---------------------|
| `--qos=short` |
- 6 hour job run time
- 2 jobs of 16 CPUs or fewer
- No more than 256 CPUs in use for *short* jobs from all users
**Using the short QoS**
{{% panel theme="warning" header="Limits per user for 'short' QoS" %}}
- 6 hour job run time
- 2 jobs of 16 CPUs or fewer
- No more than 256 CPUs in use for *short* jobs from all users
{{% /panel %}}
``` syntaxhighlighter-pre
{{% panel theme="info" header="Using the short QoS" %}}
{{< highlight bash >}}
srun --qos=short --nodes=1 --ntasks-per-node=1 --mem-per-cpu=1024 --pty $SHELL
```
{{< /highlight >}}
{{% /panel %}}
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment