Specifying software libraries for GEOS-Chem
- Minimum system requirements
- Configuring your computational environment
- Downloading source code
- Downloading data directories
- Creating run directories
- Configuring runs
- Output files
- Visualizing and processing output
- Coding and debugging
- Further reading
Selecting pre-built libraries
If you are using GEOS-Chem on your institutions computational cluster, then chances are the sofware libraries that you need will have already been built for you. If this is the case, then it is typically a simple matter to select a certain set of libraries
IMPORTANT NOTE: You should select libraries corresponding to the compiler that you specified . Otherwise, the libraries might not function properly.
Using Lmod modules
As we saw in the previous chapter, the Lmod module system is a convenient way to select not only your compiler, but also the software libraries that you will need to use with GEOS-Chem. You can use the module load command to select the libraries that you need for GEOS-Chem, which typically are:
module load netcdf/4.7.0 # Loads netCDF 4.7.0 module load netcdf-fortran/4.4.0 # Loads netCDF-Fortran 4.4.0 module load git # Loads Git module load flex # Loads Flex (needed to build mechanisms with KPP) module load nco # Loads netCDF Operators, useful for working w/ data files module load cdo # Loads Climate Data operators, useful for working w/ data files module load cmake/3.15 # Loads CMake 3.15, used to build GEOS-Chem (12.6.0 and later) module load gdb # Loads the GDB debugger module load emacs # Emacs editor (if available)
Depending on how your system is maintained, you might have to specify a version number as part of the module name. You can usually use a command such as module avail to find specific implementations of a software library. You can also ask your IT staff which module versions to use.
Also note: depending on the version of netCDF that is installed, you may or may not have to also load netcdf-fortran separately.