Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 14 Next »

Getting Help

Support staff may be contacted via:
Griffith Library and IT help 3735 5555 or X55555
email support: eresearch-services@griffith.edu.au
You can log cases on service desk (category: eResearch services.HPC)
https://conf-ers.griffith.edu.au/display/GHCD/Submit+a+Question+to+the+HPC+Support+Team?src=contextnavpagetreemode

eResearch Services, Griffith University
Email: eresearch-support@griffith.edu.au
Web: https://www.griffith.edu.au/eresearch-services

Getting Started

Logging in.

To log in to the cluster, ssh to

10.250.250.3

gc-prd-hpclogin1.rcs.griffith.edu.au

What is ssh

SSH Secure Shell provides users with a secure, encrypted mechanism to log into systems and transfer files

ssh clients

windows platform

To install a ssh client e.g. putty, please follow this instruction

Linux platform and mac platform

ssh -Y snumber@gc-prd-hpclogin1.rcs.griffith.edu.au OR

ssh snumber@gowonda2.rcs.griffith.edu.au (old cluster)

Transferring files between your desktop and gowonda cluster

Transferring files between your desktop and gowonda cluster


Once you are on the system, have a look around. Your home directory is stored in:
/exports/home/<SNumber>

where you have 50GB of allocated space.

Work space is available at:

/scratch/<snumber>

which is a "scratch" area for short lived data. All data older than one week is deleted from this folder.
You should not read or write directly into your home directory with submitted jobs - they should always use the "/scratch/<snumber>" filesystem

Running Jobs

We provide modules that set up the environments you need to use for specific packages. You can see what modules are available with the command:

module available

and you can load them with the command:

module load MODULENAME

See sample pbs scripts here.

If you don't specify a maximum runtime, you will end up with a maximum runtime as short as 30 minutes, depending on which node your job runs on.

Job Stats

when you run qstat from the command line, you will see your job's state within the queue. The following form lists the possible states and their descriptions

state code

State description

q

queued

r

running

Cluster Status

(When done, you can press "Q" to quit from the below text-based browsers

Use the commands to check the cluster status: pbsnodes, pbsjobs, and pbsqueues

elinks http://localhost:3000/nodes

elinks http://localhost:3000/jobs

elinks http://localhost:3000/queues

Reference:

1. ECDF. 20 July 2011. U of Edinburgh. 7 Oct. 2008 <www.ecdf.ed.ac.uk>

  • No labels