Terra Usage Policies
Access to Terra is granted with the condition that you will understand and adhere to all TAMU HPRC and Terra-specific policies.
General policies can be found on the HPRC Policies page.
Terra-specific policies, which are similar to Ada, can be found on the Terra Policies page.
Submitting a Job
In order to properly run a program on Terra, you will need to submit a job.
The simple example below request 1 core on 1 node with 5GB of RAM for 1 hour. The example also loads "ExampleModule", which should be replaced or omitted based on your software needs.
#!/bin/bash #SBATCH --export=NONE #SBATCH --get-user-env=L #SBATCH -t 01:00:00 #SBATCH -J ExampleJob #SBATCH -N 1 #SBATCH -n 1 #SBATCH --mem=5G #SBATCH -o ExJobOut.%j module load ExampleModule ./myprogram
The hardware on Terra differs than that on Ada. There are fewer nodes and cores overall, but more cores per node.
There are also more GPU nodes are available on Terra than Ada, but each GPU node only has a single GPU.
-Link to hardware page
The software available on Terra is similar to that on Ada.
The Terra environment is much different than Ada. While much of the software is still implemented with modules, the filepaths for HOME, SCRATCH, ... have been changed. User-created scripts may need to be adjusted when transitioning between Ada and Terra.
Terra uses Slurm instead of LSF as a batch system facilitator. All job files for Terra will need to be written in Slurm in order to run properly.
The Terra Batch System page contains information on writing, submitting, and monitoring Slurm jobs on Terra.
The HPRC Batch Translation page contains information on converting between LSF, PBS, and Slurm.
Some LSF-Slurm translation examples have also been made available on the ADA-TERRA JOBS TRANSLATION PAGE. Our staff has also written some example jobs for specific software. These software-specific examples can be seen on the INDIVIDUAL SOFTWARE PAGES where available.