You can run jobs at different sizes and durations on Launch. The following lists the different queues that you can submit to, describing how many nodes you get, how long you can run, the type of resources you get, and the average wait time.
Launch uses the Slurm scheduler. Submit resource-intensive work to the compute nodes; the two login nodes are for editing, compiling, file management, and other light work, where interactive processes are limited to one hour of CPU time and eight cores in total.
Submit a job script with sbatch, list your jobs with squeue -u $USER, cancel one with scancel, and check its efficiency after it finishes with seff. CPU jobs run on the default partition and need no partition flag; GPU jobs must request --partition=gpu with at least one GPU, for example --gres=gpu:a30:1 (up to two A30s per node). If you do not request memory, Slurm gives 1024 MB per CPU. Run sinfo to see the current partitions and their limits.
If you prefer not to write a Slurm script, the Drona Workflow Engine and the portal's Interactive Apps generate and submit jobs for you through a graphical form.
See the [Launch Batch System] guide, the [Drona Workflow Engine] guide, and the portal [Interactive Apps] guide for more information.