Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
docs.it4i.cz
Manage
Activity
Members
Labels
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
SCS
docs.it4i.cz
Commits
0a0a5bac
Commit
0a0a5bac
authored
1 year ago
by
Roman Sliva
Browse files
Options
Downloads
Patches
Plain Diff
Update slurm-job-submission-and-execution.md
parent
a12004e5
No related branches found
No related tags found
No related merge requests found
Pipeline
#33273
passed with warnings
1 year ago
Stage: test
Stage: build
Stage: deploy
Stage: after_test
Changes
1
Pipelines
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs.it4i/general/slurm-job-submission-and-execution.md
+5
-3
5 additions, 3 deletions
docs.it4i/general/slurm-job-submission-and-execution.md
with
5 additions
and
3 deletions
docs.it4i/general/slurm-job-submission-and-execution.md
+
5
−
3
View file @
0a0a5bac
...
...
@@ -69,7 +69,7 @@ Batch jobs is the standard way of running jobs and utilizing HPC clusters.
### Job Script
Create example
batch
script called script.sh with the following content:
Create example
job
script called script.sh with the following content:
```
shell
#!/usr/bin/bash
...
...
@@ -92,18 +92,20 @@ Script will:
*
use project PROJECT-ID for job access and accounting
*
use partition/queue qcpu
*
use four nodes
*
use 36 tasks per node
*
use 36 tasks per node
- value used by MPI
*
set job time limit to 12 hours
*
load appropriate module
*
run command, srun serves as Slurm's native way of executing MPI-enabled applications, hostname is used in the example just for sake of simplicity
Submit directory will be used as working directory for submitted job, so there is no need to change directory in the job script.
Alternatively you can specify job working directory using sbatch
`--chdir`
(or shortly
`-D`
) option.
### Job Submit
Submit batch job:
```
console
#
## submit directory my_work_dir will be also used as working directory for submitted job
$
cd
my_work_dir
$
sbatch script.sh
```
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment