TAMU Launch

The batch system will charge SUs from either the account specified in the job parameters, or from your default account (if this parameter is omitted). To avoid errors in SU billing, you can view your active accounts, and set your default account using the myproject command.

Drona Workflow Engine, developed by HPRC, provides a 100% graphical interface to generate and submit Generic jobs without the need to write a Slurm script yourself or even be aware of Slurm syntax and Generic internals. The Drona app is available on all HPRC Portals under the Jobs tab (Screenshot) .

you will find Generic in the Environments Dropdown (Screenshot). NOTE: If you don't see Generic in the Environments Dropdown, you need to import it first. Click on the + sign next to the environments dropdown and select the Generic environment in the pop-up window. You only need to do this once. See the import section for more information about environments.

Once you select the Generic environment, the form will expand with Generic specific fields (Screenshot) to guide you in providing all the needed information. To generate the Generic job files, click the Generate or Preview button. This will first show a fully editable preview screen with the generated job scripts. In the preview window, you can enter all the commands you want to execute in the batch script. To submit the job, click on the submit button, and Drona will submit the generated job on your behalf. For detailed information about Drona Workflow Engine, checkout the Drona Workflow Engine Guide

If you experience any issues or have any suggestions, please get in touch with us at help [at] hprc.tamu.edu

Once you have your job script ready, it is time to submit the job. You can submit your job to the Slurm batch scheduler using the sbatch command. For example, suppose you you created a batch file named MyJob.slurm, the command to submit the job will as follows:

[username@launch ~]$ sbatch MyJob.slurm
Submitted batch job 3606

After a job has been submitted, you may want to check on its progress or cancel it. Below is a list of the most used job monitoring and control commands for jobs on Launch.

Here is an example of the information that the seff command provides for a completed job:

% seff 12345678
Job ID: 12345678
Cluster: Launch
User/Group: username/groupname
State: COMPLETED (exit code 0)
Nodes: 16
Cores per node: 28
CPU Utilized: 1-17:05:54
CPU Efficiency: 94.63% of 1-19:25:52 core-walltime
Job Wall-clock time: 00:05:49
Memory Utilized: 310.96 GB (estimated maximum)
Memory Efficiency: 34.70% of 896.00 GB (56.00 GB/node)

Example Job 1: A serial job (single core, single node)

#!/bin/bash

##NECESSARY JOB SPECIFICATIONS
#SBATCH --job-name=JobExample1       #Set the job name to "JobExample1"
#SBATCH --time=01:30:00              #Set the wall clock limit to 1hr and 30min
#SBATCH --ntasks=1                   #Request 1 task
#SBATCH --mem=2560M                  #Request 2560MB (2.5GB) per node
#SBATCH --output=Example1Out.%j      #Send stdout/err to "Example1Out.[jobID]"

##OPTIONAL JOB SPECIFICATIONS
##SBATCH --account=123456             #Set billing account to 123456
##SBATCH --mail-type=ALL              #Send email on all job events
##SBATCH --mail-user=email_address    #Send all emails to email_address

#First Executable Line

Further examples can be found at Job Script / Batch System Examples.