Skip to main content

netcdf

Versions and Availability

h4

h5
Module Names for netcdf on qb2
Machine Version Module Name
qb2 4.2.1.1 netcdf/4.2.1.1/INTEL-140-MVAPICH2-2.0
qb2 4.2 netcdf_fortran/4.2/INTEL-140-MVAPICH2-2.0

▶ Module FAQ?

The information here is applicable to LSU HPC and LONI systems.

h4

Shells

A user may choose between using /bin/bash and /bin/tcsh. Details about each shell follows.

/bin/bash

System resource file: /etc/profile

When one access the shell, the following user files are read in if they exist (in order):

  1. ~/.bash_profile (anything sent to STDOUT or STDERR will cause things like rsync to break)
  2. ~/.bashrc (interactive login only)
  3. ~/.profile

When a user logs out of an interactive session, the file ~/.bash_logout is executed if it exists.

The default value of the environmental variable, PATH, is set automatically using Modules. See below for more information.

/bin/tcsh

The file ~/.cshrc is used to customize the user's environment if his login shell is /bin/tcsh.

Modules

Modules is a utility which helps users manage the complex business of setting up their shell environment in the face of potentially conflicting application versions and libraries.

Default Setup

When a user logs in, the system looks for a file named .modules in their home directory. This file contains module commands to set up the initial shell environment.

Viewing Available Modules

The command

$ module avail

displays a list of all the modules available. The list will look something like:

--- some stuff deleted ---
velvet/1.2.10/INTEL-14.0.2
vmatch/2.2.2

---------------- /usr/local/packages/Modules/modulefiles/admin -----------------
EasyBuild/1.11.1       GCC/4.9.0              INTEL-140-MPICH/3.1.1
EasyBuild/1.13.0       INTEL/14.0.2           INTEL-140-MVAPICH2/2.0
--- some stuff deleted ---

The module names take the form appname/version/compiler, providing the application name, the version, and information about how it was compiled (if needed).

Managing Modules

Besides avail, there are other basic module commands to use for manipulating the environment. These include:

add/load mod1 mod2 ... modn . . . Add modules
rm/unload mod1 mod2 ... modn  . . Remove modules
switch/swap mod . . . . . . . . . Switch or swap one module for another
display/show  . . . . . . . . . . List modules loaded in the environment
avail . . . . . . . . . . . . . . List available module names
whatis mod1 mod2 ... modn . . . . Describe listed modules

The -h option to module will list all available commands.

▶ Did not find the version you want to use??

If a software package you would like to use for your research is not available on a cluster, you can request it to be installed. The software requests are evaluated by the HPC staff on a case-by-case basis. Before you send in a software request, please go through the information below.

h3

Types of request

Depending on how many users need to use the software, software requests are divided into three types, each of which corresponds to the location where the software is installed:

  • The user's home directory
    • Software packages installed here will be accessible only to the user.
    • It is suitable for software packages that will be used by a single user.
    • Python, Perl and R modules should be installed here.
  • /project
    • Software packages installed in /project can be accessed by a group of users.
    • It is suitable for software packages that
      • Need to be shared by users from the same research group, or
      • are bigger than the quota on the home file syste.
    • This type of request must be sent by the PI of the research group, who may be asked to apply for a storage allocation.
  • /usr/local/packages
    • Software packages installed under /usr/local/packages can be accessed by all users.
    • It is suitable for software packages that will be used by users from multiple research groups.
    • This type of request must be sent by the PI of a research group.

h3

How to request

Please send an email to sys-help@loni.org with the following information:

  • Your user name
  • The name of cluster where you want to use the requested software
  • The name, version and download link of the software
  • Specific installation instructions if any (e.g. compiler flags, variants and flavor, etc.)
  • Why the software is needed
  • Where the software should be installed (locally, /project, or /usr/local/packages) and justification explaining how many users are expected.

Please note that, once the software is installed, testing and validation are users' responsibility.

About the Software

NetCDF (network Common Data Form) is a set of software libraries and machine-independent data formats that support the creation, access, and sharing of array-oriented scientific data. - Homepage: http://www.unidata.ucar.edu/software/netcdf/

Usage

Softenv or Module defines some variables which point at the library home directory.

For clusters using softenv, use soft-dbq to determine it's name, then use it to add a link option to your build. You may see something like this (the output has been edited for brevity):

$ soft-dbq  +netcdf-4.1.3-Intel-13.0.0

. . .

Name: +netcdf-4.1.3-Intel-13.0.0
Description: @types: Library/IO @name: netcdf @version: 4.1.3 @build:
Intel-13.0.0 @internal: @external:
http://www.unidata.ucar.edu/software/netcdf @about: NetCDF is a set of
software libraries and self-describing, machine-independent data
formats that support the creation, access, and sharing of
array-oriented scientific data.
Flags: none
Groups: none
Exists on: Linux
. . .
    PATH = ${PATH}:/usr/local/packages/netcdf/4.1.3/Intel-13.0.0/bin
    netcdf_HOME = /usr/local/packages/netcdf/4.1.3/Intel-13.0.0
. . .
$ ls /usr/local/packages/netcdf/4.1.3/Intel-13.0.0/lib
libnetcdf.a       libnetcdff.la        libnetcdf.la        pkgconfig
libnetcdf_c++.a   libnetcdff.so        libnetcdf.so
libnetcdf_c++.la  libnetcdff.so.5      libnetcdf.so.7
libnetcdff.a      libnetcdff.so.5.1.0  libnetcdf.so.7.1.1

The libraries are used at link time by the compiler, so the following options could be used:

   -L${netcdf_HOME}/lib -lnetcdf

For clusters using module, use the module disp command to determine the location of the netcdf path and then add it to your build options:

$ module disp netcdf/4.2.1.1/INTEL-140-MVAPICH2-2.0
-------------------------------------------------------------------
/usr/local/packages/Modules/modulefiles/apps/netcdf/4.2.1.1/INTEL-140-MVAPICH2-2.0:
. . .
module-whatis    Description: NetCDF (network Common Data Form) is a set of software libraries
 and machine-independent data formats that support the creation, access, and sharing of array-oriented
  scientific data. - Homepage: http://www.unidata.ucar.edu/software/netcdf/
  conflict         netcdf
  module           load hdf5/1.8.12/INTEL-140-MVAPICH2-2.0
  prepend-path     LIBRARY_PATH /usr/local/packages/netcdf/4.2.1.1/INTEL-140-MVAPICH2-2.0/lib
  prepend-path     MANPATH /usr/local/packages/netcdf/4.2.1.1/INTEL-140-MVAPICH2-2.0/share/man
  prepend-path     PATH /usr/local/packages/netcdf/4.2.1.1/INTEL-140-MVAPICH2-2.0/bin
  prepend-path     PKG_CONFIG_PATH /usr/local/packages/netcdf/4.2.1.1/INTEL-140-MVAPICH2-2.0/lib/pkgconfig
  setenv           LHPC_ROOTNETCDF /usr/local/packages/netcdf/4.2.1.1/INTEL-140-MVAPICH2-2.0
  setenv           LHPC_VERSIONNETCDF 4.2.1.1
. . .
$ ls $LHPC_ROOTNETCDF/lib
libnetcdf.a  libnetcdf.la  libnetcdf.so  libnetcdf.so.7  libnetcdf.so.7.2.0  pkgconfig

The libraries are used at link time by the compiler, so the following options could be used:

   -L${LHPC_ROOTNETCDF}/lib -lnetcdf

Please refer to the documentation in Resources for a discussion of the API and how to choose the correct library.

Resources

Last modified: September 10 2020 11:58:50.