UAF-RCS HPC Documentation
  • README
  • RCS High Performance Computing (HPC) Documentation
  • Request an Account
  • Getting Started
    • Introduction
    • Linux Training/Overview
    • SSH
    • Nodes
    • Using VNC to Login
    • Migrating to the New Environment
  • Available Filesystems
    • Available Filesystems
  • Using Batch
    • Batch Overview
    • Available Partitions
    • Common Slurm Commands
    • Batch Scripts
    • Interactive Jobs
    • Select a Processor Architecture
  • Third Party Software
    • Third-Party Software
    • Installing Your Own Software
    • Using the Software Stack
    • Using Software Collections (SCL)
    • Complier Toolchains
    • Maintained Software Packages
    • Singularity
    • Miniconda
    • Jupyter
    • Lmod
  • Compiling Source
    • Compiling from Source Code
  • System Architecture
    • System Architecture
  • Community Condo Model
    • Community Condo Model
  • Policies
    • Policies
Powered by GitBook
On this page
  • Software requests
  • Software Updates
  1. Third Party Software

Third-Party Software

PreviousSelect a Processor ArchitectureNextInstalling Your Own Software

Last updated 9 months ago

RCS will help researchers build and install third-party software upon request. If the software is used by multiple researchers and research groups RCS may install it as part of the RCS maintained central software stack, accessible via modules.

If the software does not meet our criteria for installation in the central software stack, RCS will help researchers build the software themselves either via source install, pre-built binary, conda, or via a container.

Software requests

RCS evaluates for widely-used HPC software on a case-by-case basis for inclusion in the central software stack. Some factors that affect request eligibility are:

  • Applicability to multiple or large research groups

  • Complexity of the installation process

  • Software update schedule

  • Software licensing

RCS will prioritize software that multiple researchers or research groups will need over software that is specific to a single researcher or small research group. RCS will also only update a software package at most once annually.

If a third-party software installation request is found to be a viable candidate for installation, RCS may elect to install the software through one of several means:

  • Source build

  • RPM

  • Binary (pre-built) distribution

If an application or library is available through standard RPM repositories (Penguin Computing, CentOS, EPEL, ...) then the RPM may be installed. Users should test the installed software to determine if it meets requirements. If the RPM version does not meet needs, please contact RCS to have alternate installation methods evaluated.

Software that is not installed as an RPM will be installed in a publicly-available location and be accessible via Linux environment modules. If the software is built from source, then RCS will default to using the Intel compiler suite.

If an installation request does not meet our criteria, we will help researchers install it themselves via source, conda, or a container.

Software Updates

RCS will evaluate software updates yearly, and based on multiple factors may update software packages. RCS will deprecate and hide old modules, keeping at most 3 versions of a software package on the system.

third-party software installation requests