Running Jobs on Sapelo2 - Revision history

Shtsai: /* Environment Variables exported by batch jobs */

2026-04-05T02:45:15Z

Environment Variables exported by batch jobs

← Older revision		Revision as of 22:45, 4 April 2026
Line 349:		Line 349:

	{\| width="100%" border="1" cellspacing="0" cellpadding="2" align="center" class="wikitable unsortable"		{\| width="100%" border="1" cellspacing="0" cellpadding="2" align="center" class="wikitable unsortable"
			\|+ Environment variables exported by batch jobs
	\|-		\|-
	! scope="col" \| Variable		! scope="col" \| Variable
	! scope="col" \| Description		! scope="col" \| Description
	\|-		\|-
	\| SLURM_ARRAY_JOB_ID \|\| Job array's master job ID number, i.e., the first Slurm job id of a job array		! scope="row" \| SLURM_ARRAY_JOB_ID
			\| Job array's master job ID number, i.e., the first Slurm job id of a job array
	\|-		\|-
	\| SLURM_ARRAY_TASK_COUNT \|\| Total number of tasks (elements) in a job array		! scope="row" \| SLURM_ARRAY_TASK_COUNT
			\| Total number of tasks (elements) in a job array
	\|-		\|-
	\| SLURM_ARRAY_TASK_ID \|\| Job array ID (index) number		! scope="row" \| SLURM_ARRAY_TASK_ID
			\| Job array ID (index) number
	\|-		\|-
	\| SLURM_ARRAY_TASK_MAX \|\| Job array's maximum ID (index) number		! scope="row" \| SLURM_ARRAY_TASK_MAX
			\| Job array's maximum ID (index) number
	\|-		\|-
	\| SLURM_ARRAY_TASK_MIN \|\| Job array's minimum ID (index) number		! scope="row" \| SLURM_ARRAY_TASK_MIN
			\| Job array's minimum ID (index) number
	\|-		\|-
	\| SLURM_CPUS_ON_NODE \|\| Number of CPUS on the allocated node		! scope="row" \| SLURM_CPUS_ON_NODE
			\| Number of CPUS on the allocated node
	\|-		\|-
	\| SLURM_CPUS_PER_TASK \|\| Number of cpus requested per task. Only set if the --cpus-per-task option is specified		! scope="row" \| SLURM_CPUS_PER_TASK
			\| Number of cpus requested per task. Only set if the --cpus-per-task option is specified
	\|-		\|-
	\| SLURM_JOB_ID \|\| Unique Slurm job id		! scope="row" \| SLURM_JOB_ID
			\| Unique Slurm job id
	\|-		\|-
	\| SLURM_JOB_NAME \|\| Job name		! scope="row" \| SLURM_JOB_NAME
			\| Job name
	\|-		\|-
	\| SLURM_JOB_CPUS_PER_NODE \|\| Count of processors available to the job on this node		! scope="row" \| SLURM_JOB_CPUS_PER_NODE
			\| Count of processors available to the job on this node
	\|-		\|-
	\| SLURM_JOB_NODELIST \|\| List of nodes allocated to the job		! scope="row" \| SLURM_JOB_NODELIST
			\| List of nodes allocated to the job
	\|-		\|-
	\| SLURM_JOB_NUM_NODES \|\|Total number of nodes in the job's resource allocation		! scope="row" \| SLURM_JOB_NUM_NODES
			\|Total number of nodes in the job's resource allocation
	\|-		\|-
	\| SLURM_JOB_PARTITION \|\| Name of the partition (i.e. queue) in which the job is running		! scope="row" \| SLURM_JOB_PARTITION
			\| Name of the partition (i.e. queue) in which the job is running
	\|-		\|-
	\| SLURM_MEM_PER_NODE \|\| Same as --mem		! scope="row" \| SLURM_MEM_PER_NODE
			\| Same as --mem
	\|-		\|-
	\| SLURM_MEM_PER_CPU \|\| Same as --mem-per-cpu		! scope="row" \| SLURM_MEM_PER_CPU
			\| Same as --mem-per-cpu
	\|-		\|-
	\| SLURM_NTASKS \|\| Same as -n, --ntasks		! scope="row" \| SLURM_NTASKS
			\| Same as -n, --ntasks
	\|-		\|-
	\| SLURM_NTASKS_PER_NODE \|\| Number of tasks requested per node. Only set if the --ntasks-per-node option is specified		! scope="row" \| SLURM_NTASKS_PER_NODE
			\| Number of tasks requested per node. Only set if the --ntasks-per-node option is specified
	\|-		\|-
	\| SLURM_SUBMIT_DIR \|\| The directory from which sbatch was invoked		! scope="row" \| SLURM_SUBMIT_DIR
			\| The directory from which sbatch was invoked
	\|-		\|-
	\| SLURM_SUBMIT_HOST \|\| The hostname of the computer from which sbatch was invoked		! scope="row" \| SLURM_SUBMIT_HOST
			\| The hostname of the computer from which sbatch was invoked
	\|-		\|-
	\| SLURM_TASK_PID \|\| The process ID of the task being started		! scope="row" \| SLURM_TASK_PID
			\| The process ID of the task being started
	\|-		\|-
	\| SLURMD_NODENAME \|\| Name of the node running the job script		! scope="row" \| SLURMD_NODENAME
			\| Name of the node running the job script
	\|-		\|-
	\| CUDA_VISIBLE_DEVICES \|\| GPU devide ID that assigned to the job to use		! scope="row" \| CUDA_VISIBLE_DEVICES
			\| GPU devide ID that assigned to the job to use
	\|-		\|-
	\|}		\|}

Shtsai: /* Partitions (queues) defined on the Sapelo2 */

2026-04-05T02:40:53Z

Partitions (queues) defined on the Sapelo2

← Older revision		Revision as of 22:40, 4 April 2026
Line 90:		Line 90:
	! scope="col" \| Partition Name		! scope="col" \| Partition Name
	! scope="col" \| Node Features		! scope="col" \| Node Features
	~~! scope="col" \| Node Number~~
	! scope="col" \| Description		! scope="col" \| Description
	! scope="col" \| Memory for jobs		! scope="col" \| Memory for jobs
Line 98:		Line 97:
	! scope="row" \| batch, batch_30d		! scope="row" \| batch, batch_30d
	\| AMD, EPYC		\| AMD, EPYC
	\|
	\| 32-core, 128GB RAM, AMD EPYC Naples		\| 32-core, 128GB RAM, AMD EPYC Naples
	\| 120GB		\| 120GB
Line 105:		Line 103:
	! scope="row" \| batch, batch_30d		! scope="row" \| batch, batch_30d
	\| AMD, EPYC		\| AMD, EPYC
	\|
	\| 64-core, 128GB RAM, AMD EPYC Rome		\| 64-core, 128GB RAM, AMD EPYC Rome
	\| 120GB		\| 120GB
Line 112:		Line 109:
	! scope="row" \| batch, batch_30d		! scope="row" \| batch, batch_30d
	\| AMD, EPYC		\| AMD, EPYC
	\|
	\| 128-core, 512GB RAM, AMD EPYC Milan		\| 128-core, 512GB RAM, AMD EPYC Milan
	\| 490GB		\| 490GB
Line 119:		Line 115:
	! scope="row" \| batch, batch_30d		! scope="row" \| batch, batch_30d
	\| AMD, EPYC		\| AMD, EPYC
	\|
	\| 128-core, 764GB RAM, AMD EPYC Genoa		\| 128-core, 764GB RAM, AMD EPYC Genoa
	\| 750GB		\| 750GB
Line 126:		Line 121:
	! scope="row" \| batch, batch_30d		! scope="row" \| batch, batch_30d
	\| Intel, Skylake		\| Intel, Skylake
	\|
	\| 32-core, 192GB RAM, Intel Xeon Skylake		\| 32-core, 192GB RAM, Intel Xeon Skylake
	\| 180GB		\| 180GB
Line 133:		Line 127:
	! scope="row" \| highmem_p, highmem_30d_p		! scope="row" \| highmem_p, highmem_30d_p
	\| AMD, EPYC		\| AMD, EPYC
	\|
	\| 32-core, 512GB RAM, AMD EPYC Naples		\| 32-core, 512GB RAM, AMD EPYC Naples
	\| 490GB		\| 490GB
Line 139:		Line 132:
	\|-		\|-
	! scope="row" \| highmem_p, highmem_30d_p		! scope="row" \| highmem_p, highmem_30d_p
	\| Intel \|\| \|\| 28-core, 1TB RAM, Intel \|\| 950GB \|\| For high memory jobs		\| Intel \|\| 28-core, 1TB RAM, Intel \|\| 950GB \|\| For high memory jobs
	\|-		\|-
	! scope="row" \| highmem_p, highmem_30d_p		! scope="row" \| highmem_p, highmem_30d_p
	\| AMD, EPYC \|\| \|\| 32-core, 1TB RAM, AMD EPYC Milan \|\| 950GB \|\| For high memory jobs		\| AMD, EPYC \|\| 32-core, 1TB RAM, AMD EPYC Milan \|\| 950GB \|\| For high memory jobs
	\|-		\|-
	! scope="row" \| highmem_p, highmem_30d_p		! scope="row" \| highmem_p, highmem_30d_p
	\| AMD, EPYC \|\| \|\| 128-core, 1TB, AMD EPYC Milan \|\| 950GB \|\| For high memory jobs		\| AMD, EPYC \|\| 128-core, 1TB, AMD EPYC Milan \|\| 950GB \|\| For high memory jobs
	\|-		\|-
	! scope="row" \| hugemem_p, hugemem_30d_p		! scope="row" \| hugemem_p, hugemem_30d_p
	\| AMD, EPYC, EDR \|\| \|\| 32-core, 2TB RAM, AMD EPYC, IB EDR interconnect \|\| 2000GB \|\| For high memory jobs		\| AMD, EPYC, EDR \|\| 32-core, 2TB RAM, AMD EPYC, IB EDR interconnect \|\| 2000GB \|\| For high memory jobs
	\|-		\|-
	! scope="row" \|hugemem_p, hugemem_30d_p		! scope="row" \|hugemem_p, hugemem_30d_p
	\|AMD, EPYC, EDR		\|AMD, EPYC, EDR
	\|
	\|48-core, 3TB RAM, AMD EPYC, IB EDR interconnect		\|48-core, 3TB RAM, AMD EPYC, IB EDR interconnect
	\|3000GB		\|3000GB
Line 158:		Line 150:
	\|-		\|-
	! scope="row" \| gpu_p, gpu_30d_p		! scope="row" \| gpu_p, gpu_30d_p
	\| GPU, A100 \|\| \|\| 64-core, 1000GB RAM, AMD EPYC, 4 NVIDIA A100 GPUs\|\| 1000GB \|\| For GPU-enabled jobs.		\| GPU, A100 \|\| 64-core, 1000GB RAM, AMD EPYC, 4 NVIDIA A100 GPUs\|\| 1000GB \|\| For GPU-enabled jobs.
	\|-		\|-
	! scope="row" \| gpu_p, gpu_30d_p		! scope="row" \| gpu_p, gpu_30d_p
	\| GPU, P100 \|\| \|\| 32-core, 192GB RAM, Intel Xeon Skylake, 1 NVIDIA P100 GPUs \|\| 180GB \|\| For GPU-enabled jobs.		\| GPU, P100 \|\| 32-core, 192GB RAM, Intel Xeon Skylake, 1 NVIDIA P100 GPUs \|\| 180GB \|\| For GPU-enabled jobs.
	\|-		\|-
	! scope="row" \| gpu_p, gpu_30d_p		! scope="row" \| gpu_p, gpu_30d_p
	\| GPU, L4 \|\| \|\| 128-core, 1TB RAM, AMD EPYC Genoa , 4 NVIDIA L4 GPUs \|\| 1000GB \|\| For GPU-enabled jobs.		\| GPU, L4 \|\| 128-core, 1TB RAM, AMD EPYC Genoa , 4 NVIDIA L4 GPUs \|\| 1000GB \|\| For GPU-enabled jobs.
	\|-		\|-
	! scope="row" \| gpu_p, gpu_30d_p		! scope="row" \| gpu_p, gpu_30d_p
	\| GPU, H100 \|\| \|\| 64-core, 1TB RAM, Intel Xeon SapphireRapids, 4 NVIDIA H100 GPUs \|\| 1000GB \|\| For GPU-enabled jobs.		\| GPU, H100 \|\| 64-core, 1TB RAM, Intel Xeon SapphireRapids, 4 NVIDIA H100 GPUs \|\| 1000GB \|\| For GPU-enabled jobs.
	\|-		\|-

Shtsai: /* Partitions (queues) defined on the Sapelo2 */

2026-04-05T02:36:21Z

Partitions (queues) defined on the Sapelo2

← Older revision		Revision as of 22:36, 4 April 2026
Line 86:		Line 86:
	The table below summarizes the partitions (queues) defined and the compute nodes that they target:		The table below summarizes the partitions (queues) defined and the compute nodes that they target:
	{\| width="100%" border="1" cellspacing="0" cellpadding="2" align="center" class="wikitable unsortable"		{\| width="100%" border="1" cellspacing="0" cellpadding="2" align="center" class="wikitable unsortable"
	\|+ Partitions and the nodes they target		\|+ Partitions and the compute nodes they target
	\|-		\|-
	! scope="col" \| Partition Name		! scope="col" \| Partition Name

Shtsai: /* Partitions (queues) defined on the Sapelo2 */

2026-04-05T02:35:52Z

Partitions (queues) defined on the Sapelo2

← Older revision		Revision as of 22:35, 4 April 2026
Line 86:		Line 86:
	The table below summarizes the partitions (queues) defined and the compute nodes that they target:		The table below summarizes the partitions (queues) defined and the compute nodes that they target:
	{\| width="100%" border="1" cellspacing="0" cellpadding="2" align="center" class="wikitable unsortable"		{\| width="100%" border="1" cellspacing="0" cellpadding="2" align="center" class="wikitable unsortable"
			\|+ Partitions and the nodes they target
	\|-		\|-
	! scope="col" \| Partition Name		! scope="col" \| Partition Name
Line 95:		Line 96:
	\|-		\|-
	\|-		\|-
	\| batch, batch_30d \|\| AMD, EPYC \|\| \|\| 32-core, 128GB RAM, AMD EPYC Naples\|\| 120GB \|\| Regular nodes		! scope="row" \| batch, batch_30d
			\| AMD, EPYC
			\|
			\| 32-core, 128GB RAM, AMD EPYC Naples
			\| 120GB
			\| Regular nodes
	\|-		\|-
	\| batch, batch_30d \|\| AMD, EPYC \|\| \|\| 64-core, 128GB RAM, AMD EPYC Rome \|\| 120GB \|\| Regular nodes		! scope="row" \| batch, batch_30d
			\| AMD, EPYC
			\|
			\| 64-core, 128GB RAM, AMD EPYC Rome
			\| 120GB
			\| Regular nodes
	\|-		\|-
	\| batch, batch_30d \|\| AMD, EPYC \|\| \|\| 128-core, 512GB RAM, AMD EPYC Milan\|\| 490GB \|\| Regular nodes		! scope="row" \| batch, batch_30d
			\| AMD, EPYC
			\|
			\| 128-core, 512GB RAM, AMD EPYC Milan
			\| 490GB
			\| Regular nodes
	\|-		\|-
	\| batch, batch_30d \|\| AMD, EPYC \|\| \|\| 128-core, 764GB RAM, AMD EPYC Genoa \|\| 750GB \|\| Regular nodes.		! scope="row" \| batch, batch_30d
			\| AMD, EPYC
			\|
			\| 128-core, 764GB RAM, AMD EPYC Genoa
			\| 750GB
			\| Regular nodes.
	\|-		\|-
	\| batch, batch_30d \|\| Intel, Skylake \|\| \|\| 32-core, 192GB RAM, Intel Xeon Skylake \|\| 180GB \|\| Regular nodes		! scope="row" \| batch, batch_30d
			\| Intel, Skylake
			\|
			\| 32-core, 192GB RAM, Intel Xeon Skylake
			\| 180GB
			\| Regular nodes
	\|-		\|-
	\| highmem_p, highmem_30d_p \|\| AMD, EPYC \|\| \|\| 32-core, 512GB RAM, AMD EPYC Naples\|\| 490GB \|\| For high memory jobs		! scope="row" \| highmem_p, highmem_30d_p
			\| AMD, EPYC
			\|
			\| 32-core, 512GB RAM, AMD EPYC Naples
			\| 490GB
			\| For high memory jobs
	\|-		\|-
	\| highmem_p, highmem_30d_p \|\| Intel \|\| \|\| 28-core, 1TB RAM, Intel \|\| 950GB \|\| For high memory jobs		! scope="row" \| highmem_p, highmem_30d_p
			\| Intel \|\| \|\| 28-core, 1TB RAM, Intel \|\| 950GB \|\| For high memory jobs
	\|-		\|-
	\| highmem_p, highmem_30d_p \|\| AMD, EPYC \|\| \|\| 32-core, 1TB RAM, AMD EPYC Milan \|\| 950GB \|\| For high memory jobs		! scope="row" \| highmem_p, highmem_30d_p
			\| AMD, EPYC \|\| \|\| 32-core, 1TB RAM, AMD EPYC Milan \|\| 950GB \|\| For high memory jobs
	\|-		\|-
	\| highmem_p, highmem_30d_p \|\| AMD, EPYC \|\| \|\| 128-core, 1TB, AMD EPYC Milan \|\| 950GB \|\| For high memory jobs		! scope="row" \| highmem_p, highmem_30d_p
			\| AMD, EPYC \|\| \|\| 128-core, 1TB, AMD EPYC Milan \|\| 950GB \|\| For high memory jobs
	\|-		\|-
	\| hugemem_p, hugemem_30d_p \|\| AMD, EPYC, EDR \|\| \|\| 32-core, 2TB RAM, AMD EPYC, IB EDR interconnect \|\| 2000GB \|\| For high memory jobs		! scope="row" \| hugemem_p, hugemem_30d_p
			\| AMD, EPYC, EDR \|\| \|\| 32-core, 2TB RAM, AMD EPYC, IB EDR interconnect \|\| 2000GB \|\| For high memory jobs
	\|-		\|-
	\|hugemem_p, hugemem_30d_p		! scope="row" \|hugemem_p, hugemem_30d_p
	\|AMD, EPYC, EDR		\|AMD, EPYC, EDR
	\|		\|
Line 122:		Line 157:
	\|For high memory jobs		\|For high memory jobs
	\|-		\|-
	\| gpu_p, gpu_30d_p \|\| GPU, A100 \|\| \|\| 64-core, 1000GB RAM, AMD EPYC, 4 NVIDIA A100 GPUs\|\| 1000GB \|\| For GPU-enabled jobs.		! scope="row" \| gpu_p, gpu_30d_p
			\| GPU, A100 \|\| \|\| 64-core, 1000GB RAM, AMD EPYC, 4 NVIDIA A100 GPUs\|\| 1000GB \|\| For GPU-enabled jobs.
	\|-		\|-
	\| gpu_p, gpu_30d_p \|\| GPU, P100 \|\| \|\| 32-core, 192GB RAM, Intel Xeon Skylake, 1 NVIDIA P100 GPUs \|\| 180GB \|\| For GPU-enabled jobs.		! scope="row" \| gpu_p, gpu_30d_p
			\| GPU, P100 \|\| \|\| 32-core, 192GB RAM, Intel Xeon Skylake, 1 NVIDIA P100 GPUs \|\| 180GB \|\| For GPU-enabled jobs.
	\|-		\|-
	\| gpu_p, gpu_30d_p \|\| GPU, L4 \|\| \|\| 128-core, 1TB RAM, AMD EPYC Genoa , 4 NVIDIA L4 GPUs \|\| 1000GB \|\| For GPU-enabled jobs.		! scope="row" \| gpu_p, gpu_30d_p
			\| GPU, L4 \|\| \|\| 128-core, 1TB RAM, AMD EPYC Genoa , 4 NVIDIA L4 GPUs \|\| 1000GB \|\| For GPU-enabled jobs.
	\|-		\|-
	\| gpu_p, gpu_30d_p \|\| GPU, H100 \|\| \|\| 64-core, 1TB RAM, Intel Xeon SapphireRapids, 4 NVIDIA H100 GPUs \|\| 1000GB \|\| For GPU-enabled jobs.		! scope="row" \| gpu_p, gpu_30d_p
			\| GPU, H100 \|\| \|\| 64-core, 1TB RAM, Intel Xeon SapphireRapids, 4 NVIDIA H100 GPUs \|\| 1000GB \|\| For GPU-enabled jobs.
	\|-		\|-

Shtsai: /* Partitions (queues) defined on the Sapelo2 */

2026-04-05T02:30:21Z

Partitions (queues) defined on the Sapelo2

← Older revision		Revision as of 22:30, 4 April 2026
Line 17:		Line 17:

	{\| width="100%" border="1" cellspacing="0" cellpadding="2" align="center" class="wikitable unsortable"		{\| width="100%" border="1" cellspacing="0" cellpadding="2" align="center" class="wikitable unsortable"
			\|+ Partitions defined on Sapelo2
	\|-		\|-
	! scope="col" \| Partition Name		! scope="col" \| Partition Name
Line 24:		Line 25:
	\|-		\|-
	\|-		\|-
	\| batch \|\| 7 days \|\| \|\| Regular nodes.		! scope="row" \| batch
			\| 7 days
			\|
			\| Regular nodes.
	\|-		\|-
	\| batch-30d \|\| 30 days \|\| 2 \|\| Regular nodes. A given user can have up to one job running at a time here, plus one pending, or two pending and none running. A user's attempt to submit a third job into this partition will be rejected.		! scope="row" \| batch-30d
			\| 30 days
			\| 2
			\| Regular nodes. A given user can have up to one job running at a time here, plus one pending, or two pending and none running. A user's attempt to submit a third job into this partition will be rejected.
	\|-		\|-
	\| highmem_p \|\| 7 days \|\| \|\| For high memory jobs		! scope="row" \| highmem_p
			\| 7 days
			\|
			\| For high memory jobs
	\|-		\|-
	\| highmem_30d_p \|\| 30 days \|\| 2 \|\| For high memory jobs. A given user can have up to one job running at a time here, plus one pending, or two pending and none running. A user's attempt to submit a third job into this partition will be rejected.		! scope="row" \| highmem_30d_p
			\| 30 days
			\| 2
			\| For high memory jobs. A given user can have up to one job running at a time here, plus one pending, or two pending and none running. A user's attempt to submit a third job into this partition will be rejected.
	\|-		\|-
	\|hugemem_p \|\| 7 days \|\|4 \|\| For jobs needing up to 3TB of memory.		! scope="row" \|hugemem_p
			\| 7 days
			\|4
			\| For jobs needing up to 3TB of memory.
	\|-		\|-
	\|hugemem_30d_p \|\| 30 days \|\| 4 \|\| For jobs needing up to 3TB of memory.		! scope="row" \|hugemem_30d_p
			\| 30 days
			\| 4
			\| For jobs needing up to 3TB of memory.
	\|-		\|-
	\| gpu_p \|\| 7 days \|\| \|\| For GPU-enabled jobs.		! scope="row" \| gpu_p
			\| 7 days
			\|
			\| For GPU-enabled jobs.
	\|-		\|-
	\| gpu_30d_p \|\| 30 days \|\| 2 \|\| For GPU-enabled jobs. A given user can have up to one job running at a time here, plus one pending, or two pending and none running. A user's attempt to submit a third job into this partition will be rejected.		! scope="row" \| gpu_30d_p
			\| 30 days
			\| 2
			\| For GPU-enabled jobs. A given user can have up to one job running at a time here, plus one pending, or two pending and none running. A user's attempt to submit a third job into this partition will be rejected.
	\|-		\|-
	\| inter_p \|\| 2 days \|\| \|\| Regular nodes, for interactive jobs.		! scope="row" \| inter_p
			\| 2 days
			\|
			\| Regular nodes, for interactive jobs.
	\|-		\|-
	\| '''name'''_p \|\| variable \|\| \|\| Partitions that target different groups' buy-in nodes. The '''name''' string is specific to each group.		! scope="row" \| '''name'''_p
			\| variable
			\|
			\| Partitions that target different groups' buy-in nodes. The '''name''' string is specific to each group.
	\|-		\|-
	\| scavenge_p \|~~\| 2~~ hours \|\| \|\| Partition that targets the buy-in nodes. When there are no available resources in the batch partition, short jobs submitted there might be automatically transferred into scavenge_p, to run on idle buy-in resources. Jobs cannot be submitted directly to this partition.		! scope="row" \| scavenge_p
			\| 4 hours
			\|
			\| Partition that targets the buy-in nodes. When there are no available resources in the batch partition, short jobs submitted there might be automatically transferred into scavenge_p, to run on idle buy-in resources. Jobs cannot be submitted directly to this partition.
	\|-		\|-
	\|}		\|}

Shtsai at 21:05, 4 March 2026

2026-03-04T21:05:56Z

Show changes

Moses at 19:10, 11 February 2026

2026-02-11T19:10:16Z

← Older revision		Revision as of 15:10, 11 February 2026
Line 129:		Line 129:
	'''Header lines explained:'''		'''Header lines explained:'''

	* '''#!/bin/bash''': specify Linux default shell bash . '''Note for zsh users''': If your default shell is zsh, we recommend using '''#!/bin/bash -l''' . The<code>-l</code>option starts <code>bash</code> as a '''login shell''', which ensures that system login initialization files ~~(such as <code>/etc/profile</code> and <code>/etc/profile.d/*</code>)~~ are sourced. On Sapelo, this is where Lmod and other environment settings are initialized.		* '''#!/bin/bash''': specify Linux default shell bash . '''Note for zsh users''': If your default shell is zsh, we recommend using '''#!/bin/bash -l''' . The<code>-l</code>option starts <code>bash</code> as a '''login shell''', which ensures that system login initialization files are sourced. On Sapelo, this is where Lmod and other environment settings are initialized.
	* '''#SBATCH --partition=batch''' : specify the partition (queue) to run on, e.g. ''batch''		* '''#SBATCH --partition=batch''' : specify the partition (queue) to run on, e.g. ''batch''
	* '''#SBATCH --job-name=test''' : specify the job name, e.g. ''test''		* '''#SBATCH --job-name=test''' : specify the job name, e.g. ''test''

Moses: /* Header lines */

2026-02-11T18:36:55Z

Header lines

← Older revision		Revision as of 14:36, 11 February 2026
Line 129:		Line 129:
	'''Header lines explained:'''		'''Header lines explained:'''

	* '''#!/bin/bash''': specify Linux default shell bash		* '''#!/bin/bash''': specify Linux default shell bash . '''Note for zsh users''': If your default shell is zsh, we recommend using '''#!/bin/bash -l''' . The<code>-l</code>option starts <code>bash</code> as a '''login shell''', which ensures that system login initialization files (such as <code>/etc/profile</code> and <code>/etc/profile.d/*</code>) are sourced. On Sapelo, this is where Lmod and other environment settings are initialized.
	* '''#SBATCH --partition=batch''' : specify the partition (queue) to run on, e.g. ''batch''		* '''#SBATCH --partition=batch''' : specify the partition (queue) to run on, e.g. ''batch''
	* '''#SBATCH --job-name=test''' : specify the job name, e.g. ''test''		* '''#SBATCH --job-name=test''' : specify the job name, e.g. ''test''

Shtsai: /* Batch partitions (queues) defined on the Sapelo2 */

2026-01-09T17:49:34Z

Batch partitions (queues) defined on the Sapelo2

← Older revision		Revision as of 13:49, 9 January 2026
Line 10:		Line 10:
	[[#top\|Back to Top]]		[[#top\|Back to Top]]

	===~~Batch partitions~~ (queues) defined on the Sapelo2===		===Partitions (queues) defined on the Sapelo2===

	There are different partitions defined on Sapelo2. The Slurm queueing system refers to queues as partition. Users are required to specify, in the job submission script or as job submission command line arguments, the partition and the resources needed by the job in order for it to be assigned to compute node(s) that have enough available resources (such as number of cores, amount of memory, GPU cards, etc). Please note, Slurm will not allow a job to be submitted if there are no resources matching your request. Please refer to [[Migrating from Torque to Slurm]] for more info about Slurm queueing system.		There are different partitions defined on Sapelo2. The Slurm queueing system refers to queues as partition. Users are required to specify, in the job submission script or as job submission command line arguments, the partition and the resources needed by the job in order for it to be assigned to compute node(s) that have enough available resources (such as number of cores, amount of memory, GPU cards, etc). Please note, Slurm will not allow a job to be submitted if there are no resources matching your request. Please refer to [[Migrating from Torque to Slurm]] for more info about Slurm queueing system.

Shtsai: /* Discovering if a partition (queue) is busy */

2025-08-01T15:32:34Z

Discovering if a partition (queue) is busy

← Older revision		Revision as of 11:32, 1 August 2025
Line 709:		Line 709:
	batch a3-[21-22] idle 64 127223 magma,AMD,EPYC,Milan,EDR lscratch:890		batch a3-[21-22] idle 64 127223 magma,AMD,EPYC,Milan,EDR lscratch:890
	batch a4-[1-24] idle 128 510529 AMD,EPYC,Milan,x86_64-v3,XL225n,EDR lscratch:890		batch a4-[1-24] idle 128 510529 AMD,EPYC,Milan,x86_64-v3,XL225n,EDR lscratch:890
	batch b1-1 ~~idle~~ 64 127209 AMD,EPYC,Rome,EDR lscratch:890		batch b1-1 down 64 127209 AMD,EPYC,Rome,EDR lscratch:890
	batch b2-[21-23] idle 64 127209 magma,AMD,EPYC,Rome,x86_64-v3,R6515,EDR lscratch:890		batch b2-[21-23] idle 64 127209 magma,AMD,EPYC,Rome,x86_64-v3,R6515,EDR lscratch:890
	batch b2-24,d5-14 idle 64 127112 AMD,EPYC,Rome,x86_64-v3,R6515,EDR lscratch:890		batch b2-24,d5-14 idle 64 127112 AMD,EPYC,Rome,x86_64-v3,R6515,EDR lscratch:890