From 39ebd238cf2fd7f382bb431b7a5bc22bf92b27de Mon Sep 17 00:00:00 2001 From: Michael Zingale Date: Sun, 17 Sep 2023 12:13:04 -0400 Subject: [PATCH] add chainslurm links --- sphinx_docs/source/conf.py | 2 +- sphinx_docs/source/nersc-workflow.rst | 2 +- sphinx_docs/source/olcf-workflow.rst | 15 +++++++++------ 3 files changed, 11 insertions(+), 8 deletions(-) diff --git a/sphinx_docs/source/conf.py b/sphinx_docs/source/conf.py index c11996c..5497268 100644 --- a/sphinx_docs/source/conf.py +++ b/sphinx_docs/source/conf.py @@ -76,7 +76,7 @@ # # This is also used if you do content translation via gettext catalogs. # Usually you set "language" from the command line for these cases. -language = None +language = "en" # List of patterns, relative to source directory, that match files and # directories to ignore when looking for source files. diff --git a/sphinx_docs/source/nersc-workflow.rst b/sphinx_docs/source/nersc-workflow.rst index db131dc..b495623 100644 --- a/sphinx_docs/source/nersc-workflow.rst +++ b/sphinx_docs/source/nersc-workflow.rst @@ -67,7 +67,7 @@ Chaining ^^^^^^^^ To chain jobs, such that one queues up after the previous job -finished, use the ``chainslurm.sh`` script in that same directory: +finished, use the `chainslurm.sh `_ script in that same directory: .. prompt:: bash diff --git a/sphinx_docs/source/olcf-workflow.rst b/sphinx_docs/source/olcf-workflow.rst index cc346d4..c6343ed 100644 --- a/sphinx_docs/source/olcf-workflow.rst +++ b/sphinx_docs/source/olcf-workflow.rst @@ -179,12 +179,15 @@ from the 480 resources available, 398 resources will remain idle until the two w Writting a Job Script: ^^^^^^^^^^^^^^^^^^^^^^ -In order to make our life easier, instead of submitting an allocation command line, loading the modules, setting the threads/MPI process, and writing -another command line to submit our jobs, we can make an script to pack all these command into one executable ``.sh`` file, that can be submitted - via ``bsub`` just once. +In order to make our life easier, instead of submitting an allocation +command line, loading the modules, setting the threads/MPI process, +and writing another command line to submit our jobs, we can make an +script to pack all these command into one executable ``.sh`` file, +that can be submitted via ``bsub`` just once. -We start our job script, summoning the shell with the statement ``!/bin/bash``. Then we add the ``bsub`` allocations flags, starting with ``#BSUB`` -as follows: +We start our job script, summoning the shell with the statement +``!/bin/bash``. Then we add the ``bsub`` allocations flags, starting +with ``#BSUB`` as follows: .. code-block:: bash @@ -482,7 +485,7 @@ and get an estimated start time via: Job Chaining ^^^^^^^^^^^^ -The script `chainslurm.sh `_ can be used to start +The script `chainslurm.sh `_ can be used to start a job chain, with each job depending on the previous. For example, to start up 10 jobs: