Quick Start Guide

1. Obtain LANTA access

In short, there 3 steps as follows

1. Obtaining ThaiSC user account at http://www.thaisc.io [ThaiSC user account registration]

2. Submitting a proposal for your project (For PI only) [Proposal submission ]

3. Joining a project [Joining a project]

Please see Get Access to LANTA for more detail. Please note that, LANTA account will be sent you to via email 1-3 business days after you join the project.

2. Login to LANTA

Please see Login to LANTA for detail instruction. In short, you must have

1. Google authenticator application for two factor authentication (2FA)

2. SSH client (e.g. PuTTY, MobaXterm for Windows or terminal for macOS,Linux)

To login to LANTA, please follow steps below.

1. (Only required for the first time) Setting up Google authenticator for 2FA by either using provided Q code or manually enter secret key.

2. Using SSH client to login to LANTA with following detail.

   1. Remote host: lanta.nstda.or.th

   2. username: your LANTA username received in step 1 Obtain LANTA access.

3. Entering your password.

4. Entering 6 digits 2FA.

5. For some circumstance (e.g. first logging in), you will be forced to change your password.

6. The connection between SSH session and LANTA is now established. You are in the LANTA frontend node, please carefully read frontend usage policy (LANTA Frontend Usage Policy ) to avoid any policy violation.

3. Working space on LANTA

There are 3 working spaces on LANTA, see Storage quota for more detail.

To list all your main working space details, using myquota command.

 hpcuser@x3002c0s15b0n0:~> myquota
                             Block Quota Limits          Inode Quota Limits
                                Used       Size         IUsed        Inodes
                          ---------------------  --------------------------
/home/hpcuser                 31.57G       100G        172925        600000
/project/lt200199-espre       61.81G         5T        192973      50000000

The first one (line 5) is your user home directory with a limit of 100 GB. This is your landing location when logging in. The second one (line 6) is your project directory with a limit of 5 TB. If you are the member of more than one project, all of project details will be listed as well.

4. Resource credit

To check remaining HPC resources, use sbalance command. On LANTA, SHr (service unit hour) is a unit that we use for HPC resource credit. SHr is equivalent to 1 hour of a compute node (128 CPU cores), see Checking remaining resources for more details.

hpcuser@x3002c0s9b0n0:~> sbalance
Account    Descr   Remaining(%)  Allocation(SHr)   Remaining(SHr)        Used(SHr)
----------------------------------------------------------------------------------
lt123456  myproj        98.94%         26041.67         25764.53           277.14

5. File transfer

Using data transfer node (transfer.lanta.nstda.or.th) instead of frontend node (lanta.nstda.or.th) and follow instructions in File transfers.

6. Compiler and Software

In LANTA, there are preinstalled software that manage by Environment module system (Lmod), see Software management system for more detail. In short, you can use the following command to load a specify software.

### to list all preinstalled software/libraries
hpcuser@x3002c0s9b0n0:~>module avail
### to load a given software
hpcuser@x3002c0s9b0n0:~>module load [software]

To install software/library by your own, please see Software installation guideline. Most of major compilers are available on LANTA.

6. Running your job

LANTA queueing system is managed by Slurm. In general, there are 6 major steps for running a job.

1. Preparing input file(s) and script(s)

2. Checking available resources

   • using sinfo command to check LANTA status, see Checking LANTA HPC Status.

3. Preparing Slurm submission script (submit.sh), see Application software for example scripts of each application.

4. Submitting job

   • using sbatch submit.sh

5. Checking job status

   • using myqueue , see Checking Job status for more detail.

6. Checking job output(s)

For a simple test job, you can try Running your first job.