Changes between Version 45 and Version 46 of cypress/about

Timestamp:

08/21/18 12:26:00 (6 years ago)

Author:

fuji

Comment:

—

cypress/about

@@ -104 +104 @@
 The "'''interactive'''" QOS is intended to be used for testing SLURM script submission, and is limited to 1 job per user.  See [https://wiki.hpc.tulane.edu/trac/wiki/cypress/using#interactiveQOS interactiveQOS]
 
+See below for details:
+
+* [https://wiki.hpc.tulane.edu/trac/wiki/cypress/using#UsingSLURMonCypress  Slurm Scripts]
+
+* [https://wiki.hpc.tulane.edu/trac/wiki/cypress/using#RunningMannySerialJobs  Job-Array]
+
+* [https://wiki.hpc.tulane.edu/trac/wiki/cypress/using#SubmittingInteractiveJobs  Interactive Jobs]
+
 === Job scheduling and priority ===
 
@@ -131 +139 @@
 SLURM calculates each priority component as a fraction (value between 0 and 1), which is then multiplied by a weight.  The current weights are:  Fair-share:  100,000; Age:  10,000;  Job Size:  1,000.  That is, Fair-share is the major contributor to priority.  The weighted components are added to give the final priority.
 
-=== Running serial jobs ===
-
-If you are running a large number of serial jobs, it is recommended to submit them as a job array to make the best use of your allocated resources.  For example, suppose you are running 100 serial jobs using scripts located in a "scripts" folder, each of which does a serial calculation:  scripts/run1.sh, scripts/run2.sh, ..., scripts/run100.sh.  You would create an sbatch script named "run100scripts.srun" with contents:
-
-{{{
-#!/bin/bash 
-#SBATCH -J array_example
-#SBATCH --array=0-4
-#SBATCH -N 1
-#SBATCH -n 20
-#SBATCH --time=01:00:00
-
-srun ./runscript.sh
-}}}
-
-The contents of the script "runscript.sh" would be:
-
-{{{
-#!/bin/bash
-
-RUNNUMBER=$((SLURM_ARRAY_TASK_ID*SLURM_NTASKS + SLURM_PROCID + 1))
-./scripts/run$RUNNUMBER.sh
-}}}
-
-Make sure your scripts have executable permissions.  Then, submitting with:
-
-{{{
-sbatch run100scripts.srun
-}}}
-
-will run the 100 scripts as a 5 job array, with 20 tasks each.