Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Current »

Software for your local Linux resource

Windows and Mac users are accustomed to downloading Lehigh licensed software from https://software.lehigh.edu. Linux users can mount HPC software stack on their local machine. Users need to either know admin credentials on their local resource (aka be able to become root) or need to ask the system administrator of their local resource in order to follow the instructions below.

Mounting HPC software stack

Add the following line to /etc/fstab 

leviathan.cc.lehigh.edu:/mnt/zhome-core /share/Apps nfs defaults 0 0

Software will not run on older hardware i.e. anything older than Intel's IvyBridge architecture.

Usage

You need to modify your PATH and optionally the LD_LIBRARY_PATH and LD_INCLUDE_PATH to use the software. The preferred method is to use the module environment to dynamically modify your environment thereby avoiding conflicts with other software in your path.

Environment Module

Add the following lines to your .bashrc,

source /share/Apps/compilers/etc/lmod/zlmod.sh
module use --append /share/Apps/compilers/share/spack/lmod/linux-centos8-x86_64/Core
module load hawk

Additional information on Module Environment. For MPI enabled applications, load the rdma-core and slurm libraries (not guaranteed to work).


Issues with mounting HPC software

Users who mount HPC software should be aware that performance of software packages may vary based on your local network. Please do not direct questions related to performance of HPC software on your local resource to Research Computing staff. Research Computing Staff is not taking responsibility for supporting your linux desktop. We are only providing instructions to use our software so that you do not have to try to duplicate our efforts. Please request your computing consultant to provide support for Linux on your desktop.

Users should consider building a software stack locally using the SPACK package manager if the network causes performance issues for the software in question.

  • No labels