Embedded Files
Coming Soon
Queue Policy
List of HPC Queues
You will be using a queue system, in this case the PBS (portable batch system), to ask your code to execute on a compute node. Depending on the maximum time limit, your code can use. Our clusters offer a variety of Queues. According to PBS, script file must contain the queue name.
The command below can be used to obtain the list of available queues on the clusters, along with their specifics:
$ qstat -q
QUEUES AVAILABLE FOR CORE USERS
QUEUE NAME MAXIMUM WALLTIME RUN LIMIT/MAX. NODES RELATIVE PRIORITY
interactive 30 mins 4 jobs 1
debug 30 mins 4 jobs 1
short1 24 hours 90 node 2
short 48 hours 64 nodes 3
medium14-8 48 hours 32 nodes 3
medium24-8 72 hours 64 nodes 4
long11-3 72 hours 15 nodes 4
long21-4 120 hours 8 nodes 5
hmq (High M/M)1-4 72 hours 4 jobs 3
USAGE POLICY
Users will submit jobs only through the queue. Running long production runs interactively on any node without using the queue is strictly forbidden.
Chaining of jobs on the interactive and debug queues are strictly forbidden.
User will not place jobs on hold for more that 4 hours. Such jobs shall be deleted by the systems administrator beyond the allowed limit.
A single user can have no more than 3 jobs waiting in the queue at any point of time.
Users should (as far as possible) route all runtime I/O operations to the parallel file-system (scratch area).
STORAGE QUOTA
Every user will be allocated a home area 50 GB for all users, by default.
Additional space can be allocated based on adequate justification.
The location of this area will be e.g. /home/<userid>. and can also be accessed by the environmental variable $HOME
USER ACCOUNT PASSWORD POLICY:
Since the account is attached with your LDAP ID/Wifi ID. It is requested to you please use the strong password to avoid any possible breach of your data.
Recommendations:
Password must be at least [8] characters in length.
Minimum one UPPER case character.
Minimum one LOWER case character.
Minimum one DIGIT.
Report abuse