GradsPy...

How to use

You can check the versions installed in Gadi with a module query:

$ module avail gradspy

We normally recommend using the latest version available and always recommend to specify the version number with the module command:

$ module load gradspy/2.2.1

For more details on using modules see our software applications guide.

An example PBS job submission script named gradspy_job.sh is provided below.

It requests 1 CPU, 2 GiB memory, and 8 GiB local disk on a compute node on Gadi from the normal queue for 30 minutes against the project a00. It also requests the system to enter the working directory once the job is started. This script should be saved in the working directory from which the analysis will be done.

To change the number of CPU cores, memory, or jobfs required, simply modify the appropriate PBS resource requests at the top of this file according to the information in our queue structure guide.

Note that if your application does not work in parallel, setting the number of CPU cores to 1 and changing the memory and jobfs accordingly is required to prevent the compute resource waste.

#!/bin/bash
 
#PBS -P a00
#PBS -q normal
#PBS -l ncpus=1
#PBS -l mem=2GB
#PBS -l jobfs=8GB
#PBS -l walltime=00:30:00
#PBS -l wd
 
# Load module, always specify version number.
module load gradspy/2.2.1 # This also loads python2/2.7.17 module
 
# Must include `#PBS -l storage=scratch/ab12+gdata/yz98` if the job
# needs access to `/scratch/ab12/` and `/g/data/yz98/`
 
# Run GradsPy application
python gradspy_script.py

For more information about GradsPy syntax to be used in gradspy_script.py: http://cola.gmu.edu/grads/gadoc/python.html

To run the job you would use the PBS command:

$ qsub gradspy_job.sh

Authors: Mohsin Ali