...
| Code Block |
|---|
| language | bash |
|---|
| title | Create batch submission script for simple commands |
|---|
|
launcher_creator.py -j simple.cmds -n simple -t 00:01:00 -a OTH21164TRA23004 -q development |
You should see output something like the following, and you should see a simple.slurm batch submission file in the current directory.
| Code Block |
|---|
Project simple.
Using job file simple.cmds.
Using development queue.
For 00:01:00 time.
Using OTH21164TRA23004 allocation.
Not sending start/stop email.
Launcher successfully created. Type "sbatch simple.slurm" to queue your job. |
...
| Code Block |
|---|
| language | bash |
|---|
| title | Submit simple job to batch queue |
|---|
|
sbatch simple.slurm
showq -u
# Output looks something like this:
-------------------------------------------------------------
Welcome to the Lonestar6 Supercomputer
-------------------------------------------------------------
--> Verifying valid submit host (login2)...OK
--> Verifying valid jobname...OK
--> Verifying valid ssh keys...OK
--> Verifying access to desired queue (normal)...OK
--> Checking available allocation (OTH21164TRA23004)...OK
Submitted batch job 1722779
|
...
| Code Block |
|---|
| language | bash |
|---|
| title | Create batch submission script for simple commands |
|---|
|
launcher_creator.py -j simple.cmds -n simple -t 00:01:00 -a OTH21164TRA23004 -q development |
- The name of your commands file is given with the -j simple.cmds option.
- Your desired job name is given with the -n simple option.
- The <job_name> (here simple) is the job name you will see in your queue.
- By default a corresponding <job_name>.slurm batch file is created for you.
- It contains the name of the commands file that the batch system will execute.
...
| Expand |
|---|
| title | Our class ALLOCATION was set in .bashrc |
|---|
|
The .bashrc login script you've installed for this course specifies the class's allocation as shown below. Note that this allocation will expire after the course, so you should change that setting appropriately at some point. | Code Block |
|---|
| language | bash |
|---|
| title | ALLOCATION setting in .bashrc |
|---|
| # This sets the default project allocation for launcher_creator.py
export ALLOCATION=OTH21164TRA23004 |
|
- When you run a batch job, your project allocation gets "charged" for the time your job runs, in the currency of SUs (System Units).
- SUs are related in some way to node hours, usually 1 SU = 1 "standard" node hour.
...
| Code Block |
|---|
| language | bash |
|---|
| title | Create batch submission script for wayness example |
|---|
|
launcher_creator.py -j wayness.cmds -n wayness -w 4 -t 00:02:00 -a OTH21164TRA23004 -q development
sbatch wayness.slurm
showq -u |
...
| Code Block |
|---|
| language | bash |
|---|
| title | Start an idev session |
|---|
|
idev -m 60 -N 1 -A OTH21164TRA23004 -p normal -r CoreNGS-Tue |
Notes:
- -p normal requests nodes on the normal queue
- this is the default for our reservation, while the development queue is the normal default
- -m 60 asks for a 60 minute session
- -A OTH21164 TRA23004 specifies the TACC allocation/project to use
- -N 1 asks for 1 node
- --reservation=CoreNGS-Tue gives us priority access to TACC nodes for the class. You normally won't use this option.
...
| Code Block |
|---|
-> Checking on the status of development queue. OK
-> Defaults file : ~/.idevrc
-> System : ls6
-> Queue : development (cmd line: -p )
-> Nodes : 1 (cmd line: -N )
-> Tasks per Node : 128 (Queue default )
-> Time (minutes) : 60 (cmd line: -m )
-> Project : OTH21164TRA23004 (cmd line: -A )
-----------------------------------------------------------------
Welcome to the Lonestar6 Supercomputer
-----------------------------------------------------------------
--> Verifying valid submit host (login1)...OK
--> Verifying valid jobname...OK
--> Verifying valid ssh keys...OK
--> Verifying access to desired queue (development)...OK
--> Checking available allocation (OTH21164TRA23004)...OK
Submitted batch job 235465
-> After your idev job begins to run, a command prompt will appear,
-> and you can begin your interactive development session.
-> We will report the job status every 4 seconds: (PD=pending, R=running).
-> job status: PD
-> job status: R
-> Job is now running on masternode= c302-005...OK
-> Sleeping for 7 seconds...OK
-> Checking to make sure your job has initialized an env for you....OK
-> Creating interactive terminal session (login) on master node c302-005.
-> ssh -Y -o "StrictHostKeyChecking no" c302-005 |
...