Skip to end of metadata
Go to start of metadata

Getting access to Viking is a simple two stage process. First research groups/projects apply for a Viking Project Account. The Project Account is assigned a Project Code. The PI passes this project code onto the other members of the project and they use this to apply for a user account. The PI is notified each time a user account is assigned to the project.

Project Application

In order to use the Viking cluster research groups/projects must apply for a Viking Project Account. The project accounts will be used to monitor the usage of Viking and attribute its use by researchers across the University.

We ask that the PI who applies for the account is a permanent member of staff, as this will allow us to have a permanent contact for project reporting purposes. You can also nominate a deputy who can deal with any project enquiries on your behalf.

The PI of the project should complete this project application form.

When completed a Viking Project Code will be supplied to you. The Project PI should then distribute the project code to all research team members before they apply for user accounts.

A PI may request more than one Viking Project Code for multiple projects.

The Project Application Form can be found here.

Viking User Application

Each user must apply for an individual user account. Your PI, or supervisor, will supply you with a Viking Project Code which you will need to complete this application for an account.

The User Application Form can be found here.

How to access the cluster

Once your account has been created you can access Viking through the login node:

Instructions for accessing Viking from Linux, Windows and MACs are here: Accessing YARCC.

The login servers are to be used for program/application development and job submission only. Please do not run your programs on the login nodes for long periods of time - this is what the cluster is for!

IMPORTANT - Run your jobs from the scratch filesystem.

In order to have reliable job execution and the best performance, you have to run your jobs from the scratch filestore:

A sub-directory in scratch , with your username as the directory name, has been created for you to use.

For example "scratch/abc123". This directory is accessible from all nodes.

This is not optional, running your jobs from your home directory will result in your jobs being killed when started by the grid engine.

Your directory in /scratch
abc123@login0$ cd scratch
abc123@login0$ who am i
abc123  pts/6        2015-04-21 09:08 (
abc123@login0$ ls
ab1209  awe502  csrv660  idf1    rc1135  sl561      zh107
abc123  bn506   ejb573   jb635   ma725   nw637      rg531   snsb500  zl837
abs4    bw841   em645    jg757   mjs510  pbk1       sa1170  so523    zn526
aes530  cb751   gp676    jhs503  ms1491  pjh503     sg778   tao500
agf501  cnap    hq524    km816   msn511  pz502      sjh518  yh546
abc123@login0$ cd abc123
abc123@login0$ pwd


Please do all you work in your scratch directory.

Note - editing files on a Windows PC:

If you still get this error and you are sure you are submitting your job from the scratch  directory, you may have edited your file on a Windows PC and transferred it to scratch

Editing text files on Windows has the bad effect of inserting additional characters into the file. After you have transferred the file to the login server, use the following command to remove these characters:

dos2unix <job-script>

We do not recommend that you edit your files on a Windows PC and transfer them to the cluster.

  • No labels