Software

  • Requesting Software
  • Software Installation

In the first instance please contact your local helpdesk. Some software, typically compilers, MPI libraries, maths libraries and popular software applications are installed centrally and are listable by using

module avail

Key software applications will be built against the most recent compilers and MPI libraries. Some institutions may have experts in specific software and will take the lead in installing these applications. Some institutions will also install some software specifically for their users (e.g. due to licences). Both these sets of software will be installed in an institutional module. By loading

module york

for example, the software application modules for York will be loaded. Therefore some software applications will not reside in a central location. We provide an extension

module find name

to search all the modulefiles for the application name. Alternatively, users can search the "A-Z Listings". Users may also install software in their own user filestore and use UNIX permissions to share with their research group.

Software A-Z

Please see our Software A-Z for a list of available Software and Compilers.

Institutional Software Installation Instructions

Software installation on N8 HPC is devolved to its members. Each local institution can give its local experts sufficient privileges to install software themselves, as well as install it themselves. This page outlines how this happens. Note that the process is essentially the same for local N8 HPC technical support as it is for their local experts.

  1. The local expert agrees with their local support helpdesk on software for them to install.
  2. Their local support will create an application directory for installation in that institution's module tree (e.g. /apps/york) and give the local expert appropriate UNIX permissions
  3. The local expert installs the software in the named directory
    • If the software is to be installed for a variety of (say) optimisations or (say) MPI libraries, then each installation is performed in a distinct subdirectory. The naming convention will be explained by the local support.
    • All output should be captured (e.g. by typescript) including any modules loaded & environment variables set up and parameters passed to "configure" scripts etc
    • The software needs to be tested.
    • Ideally, an example dataset and scaling results will be made available by the local expert.
  4. The local support will work with the local expert to create the appropriate modulefiles·
  5. Once installed and tested, the local support will change the permissions of the software application directory (to prevent accidents)
  6. If the software is for more general use, the sys admin will create a central module reference
  7. Sufficient documentation should be passed to the local support team (for saving on the N8 HPC intranet) such that, if required, others could re-install the software from scratch and to help others provide initial support

Documentation and Support

There is a page on the website "A-Z listing" that follows the standard template. Each N8 HPC member institution is responsible for writing and maintaining the pages for the software that it installs.

Login Form