Specifying compilers for GEOS-Chem

From Geos-chem
Revision as of 21:18, 17 December 2019 by Bmy (Talk | contribs) (Using spack)

Jump to: navigation, search

Previous | Next | Getting Started with GEOS-Chem

  1. Minimum system requirements
  2. Configuring your computational environment
  3. Downloading source code
  4. Downloading data directories
  5. Creating run directories
  6. Configuring runs
  7. Compiling
  8. Running
  9. Output files
  10. Visualizing and processing output
  11. Coding and debugging
  12. Further reading

Selecting the compiler

There are typically several ways in which you can select the compiler that you wish to use with GEOS-Chem. Not all of these may be present on your system, so it is always best to ask your IT staff about specifics

Using Lmod modules

Many computational clusters use the Lmod module system to allow you to pick and choose different pre-compiled software programs and libraries. Lmod makes it easy to switch between different compiler versions, if more than compiler has been installed. Check with your IT staff if your system uses the Lmod module command.

If your system uses Lmod, then you can load the compiler with commands such as:

module load intel/19.0


module load gcc/9.2.0

... etc ...

(Actual commands will vary from system to system.)

You can typically place these module load commands in your .bashrc or .bash_aliases startup scripts. Ask your IT staff where they would prefer them to be placed.

When a module is "loaded", the following things typically happen:

  1. The path to the compiler executable is added to your Unix $PATH variable.
  2. The path to the compiler library files is added to your $LD_LIBRARY_PATH environment variable.
  3. One or more environment variables (e.g. $INTEL_HOME, $GCC_HOME) are added to your Unix environment.

Using spack


Direct specification


Defining the proper environment variables


Previous | Next | Getting Started with GEOS-Chem