Environment and Modules

The default login shell is Bash (/bin/bash). Check your configured shell with:

echo "$SHELL"

Example output:

/bin/bash

Keep the assigned Bash shell. Customize aliases and functions in $HOME/.bashrc; use modules for compiler and library paths.

Environment Variables

Environment variables configure your shell and applications: HOME is your home directory; PATH lists command directories.

To list the variables in your current environment, run:

env

To inspect an individual value, use echo, for example:

echo "$HOME"
echo "$PATH"

Environment output can include credentials or tokens set by applications. Check it before sharing it in a support ticket.

Lmod adjusts compiler and library paths in the current shell. It selects installed software; it does not install packages.

Command	Purpose
`module list`	Show loaded modules
`module avail`	Show available modules
`module spider nvhpc`	Search module versions and prerequisites
`module help nvhpc-hpcx-cuda13-openmpi5/26.5`	Read module help
`module show nvhpc-hpcx-cuda13-openmpi5/26.5`	Inspect environment changes without loading

Selected entries from the recorded module avail output:

nvhpc/26.5
nvhpc-hpcx-cuda13-openmpi5/26.5
nvhpc-hpcx-cuda13-openmpi4/26.5
nvhpc-nompi/26.5
mpi/openmpi/5.0.10-cuda
mpi/openmpi/5.0.10 (D)

(D) marks the default version. Inspect module paths before selecting a stack for compute nodes.

The following changes affect your current shell's software environment:

module purge
module load nvhpc-hpcx-cuda13-openmpi5/26.5
module list
mpicc --version

purge unloads modules (sticky modules may remain). Use one compatible compiler/MPI stack at a time rather than combining unrelated MPI modules.

mpicc wraps the C compiler. See Compilers for language wrappers and version checks.

Load the same module in your batch script. See the job templates.

To unload this module in your shell:

module unload nvhpc-hpcx-cuda13-openmpi5/26.5