Scientific analysis servers

This article describes the scientific analysis servers. It covers:

• Scientific Analysis (sci) servers 
• Purpose 
• Software installed 
• Access to storage 

Once you have logged on to one of the login servers you can then ssh to the shared analysis servers that you have been given access to. 

Scientific analysis servers 

Access to the scientific analysis (sci) servers is restricted to ssh login from hosts inside the RAL firewall, so access from outside needs to be achieved via one of the login servers.

Note 1:  sci[3,6,8].jasmin.ac.uk are physical servers with IP addresses on a private internal network, so outbound internet access (via NAT) is only for HTTP(S). This means that outbound SSH will not work (to hosts outside of JASMIN) on these particular machines e.g. pull/clone from Github remote repositories will NOT work on these particular machines and the following error message is triggered:   fatal: Could not read from remote repository. 

Note 2: The local /tmp of the virtual VMs is not available (NA) for users as this is used by the VM system

Note 3: A new monitoring utility "Arbiter" was implemented across all Sci machines to control CPU and memory usage. This utility "Arbiter" records the activity on the node, automatically sets limits on the resources available to each user, and notifies JASMIN admin when resources quota are changed. From the user's perspective, his/her process will be capped from using any extra resources and the process can be slowed or run out of memory. 

Note 4: Users are not permitted to execute commands which require administrative privileges. This applies to all hosts in the managed part of JASMIN where users have SSH login access (for example login, nx-login, sci, xfer and hpxfer machines). In other words, the use of  su or sudo is not permitted. Please be careful when typing commands, particularly if you have multiple terminal windows open on your own computer, that you do not accidentally attempt sudoon a JASMIN machine: expect some follow-up from the JASMIN team if you do!

Further information on using the software provided on JASMIN can be found here.

Purpose 

Scientific analysis servers are designed for interactive and ad-hoc analysis of data in group workspaces, the CEDA archives, and users' home directories.   For long-running and resource-intensive jobs, users are required to use the LOTUS cluster which offers better I/O performance, parallelism, and scheduling.

The following guide should be considered when using the scientific analysis servers:

• Be aware of resources available at the time before your process starts and choose the scientific server that is suitable ( check the average load on the scientific server from the message of the day on login server for example or using any of Linux monitoring command: top, free -h )
• Execution/processing time should be less than 1 hour;
• Serial jobs only 
• High memory jobs should be executed on the high memory scientific servers with 1000 GB of RAM sci[3,6].jasmin.ac.uk (see above Table )
• Monitor your process on a scientific server using top or ps Linux command 
• Report if there is a user's process affecting the performance of a scientific server 

Software installed

Each analysis server has the following features:

• Default Redhat Enterprise Linux development environment.
• The software packages that make up the Jaspy software environment are all installed - providing commonly-used open-source analysis tools.  These packages include NCO, CDO, Python3.x (with netCDF4, matplotlib, numpy etc.,) and R.
• Access to proprietary tools, e.g. IDL and Intel Fortran, through the Module System.
• Ability to run X11/X-Windows applications (use the NX graphical desktop service to view X11 graphics output efficiently on your remote machine).

Access to storage 

Each analysis server has:

• Access to the LOTUS /work/scratch-pw*and /work/scratch-nopw2 volumes.
• <li>Read access to the <a href="http://help.jasmin.ac.uk/article/3838-ceda-archive">CEDA
• Archives</a> according to user permissions.</li> <li>Read/Write access to Group Workspaces according to user permissions.</li>