Difference between revisions of "Setting Up the GCHP Environment"

From Geos-chem
Jump to: navigation, search
(Changing MPI)
Line 1: Line 1:
'''''[[Obtaining_a_GCHP_Run_Directory|Previous]] | [[Compiling_GCHP|Next]] |  [[Getting_Started_With_GCHP|Getting Started with GCHP]]'''''
'''''[[Obtaining_a_GCHP_Run_Directory|Previous]] | [[Compiling_GCHP|Next]] |  [[Getting_Started_With_GCHP|Getting Started with GCHP]]'''''
#[[GCHP_Hardware_and_Software_Requirements|Hardware and Software Requirements]]
#[[Downloading_GCHP|Downloading Source Code]]
#[[Downloading_GCHP|Downloading Source Code]]
#[[Obtaining_a_GCHP_Run_Directory|Obtaining a Run Directory]]
#[[Obtaining_a_GCHP_Run_Directory|Obtaining a Run Directory]]

Revision as of 20:27, 2 August 2018

Previous | Next | Getting Started with GCHP

  1. Hardware and Software Requirements
  2. Downloading Source Code
  3. Obtaining a Run Directory
  4. Setting Up the GCHP Environment
  5. Compiling
  6. Basic Example Run
  7. Run Configuration Files
  8. Advanced Run Examples
  9. Output Data
  10. Developing GCHP

Load Libraries and Set Environment Variables

Once you are sure you meet all GCHP hardware and software requirements, you must load all necessary libraries and export certain environment variables before compiling GCHP. If you are using Harvard's Odyssey compute cluster setting up an interactive session is required. For non-Odyssey users, check with your IT staff about preferred protocol.

The GCHP environment is different from GEOS-Chem classic and we have tried to make setting libraries and variables as automatic as possible to minimize problems. We recommend simplifying the environment setup process by customizing a GCHP-specific .bashrc (or .cshrc) file that you source prior to compiling and running GCHP.

Sample .bashrc files are included in the run directory, several for the Harvard University Odyssey cluster and one for a more generic Linux system. These are located in the bashrcSamples subdirectory. You can use these to develop one compatible with your system. Eacj sample .bashrc file is customized for a specific combination of Fortran compiler, MPI implementation, and compute cluster. For example, one of the .bashrcs customized for use on the Harvard Odyssey compute cluster uses ifort15 and the MVAPICH2 implemenation of MPI. To setup your environment source your .bashrc file, use the command: source .bashrc.

We recommend opening several of the sample environment files and getting familiar with the environment variables set. The files include printing the variables to screen when the sourced. This is particularly useful for logging purposes if you automatically source the environment file within a run script: the environment variables will be printed to your system log file and will reflect the settings using during your run, potentially useful for debugging and archiving. Also included in the environment files are a few aliases which for commands that are commonly repeated when developing, compiling, and running GCHP. We recommend that you look at them to see if you would like to adopt them or add your own.

Changing MPI

The GCHP run directory is set up by default for use with the openMPI implementation of MPI. However, we realize that you may want to use a different implementation, possibly out of necessity. To do this, follow the steps below.

  1. Specify environment variable ESMF_COMM to match the MPI implementation. Options are currently in place for MVAPICH2 (ESMF_COMM=mvapich2), OpenMPI (ESMF_COMM=openmpi), and a generic MPI implementation. (ESMF_COMM=mpi). The generic option is sufficient when, for example, running with the SGI MPI implementation on NASA's Pleiades servers. If you are using a new MPI implementation not covered by one of these options, we recommend running first with ESMF_COMM=mpi.
  2. Specify the environment variable MPI_ROOT to point to the MPI root directory, such that $MPI_ROOT/bin/mpirun points to the correct MPI run binary.
  3. Ensure that you have valid mpif90 and mpifort executables. These almost always perform the same role but both names are invoked in the build sequence. If you have one but not the other, we strongly recommend that you make a softlink to the working binary with the name of the missing binary in a dedicated folder, and then add that folder to your path at the command line and in your .bashrc. For example, if you have a mpifort binary but not an mpif90 binary, run the following commands:
mkdir $HOME/mpi_extra
cd $HOME/mpi_extra
ln -s $( which mpifort ) mpif90
export PATH=${PATH}:${HOME}/mpi_extra

You should now try to compile GCHP. If the generic option does not work then you will need to implement a new option. This involves updating GCHP source code. An example of how to do this for Intel MPI is as follows:

  1. Decide a new name, such as ESMF_COMM=intel for the Intel MPI implementation.
  2. Determine the relevant include path and linker commands for your MPI implementation. In this example for Intel MPI they are $(MPI_ROOT)/include and -L$(MPI_ROOT)/lib -lmpi -lmpi++ respectively.
  3. Update source code files CodeDir/GCHP/GIGC.mk and CodeDir/GCHP/Shared/Config/ESMA_base.mk. In both files, search for environment variable ESMF_COMM in the file. You should find a small set of occurrences in a single "if..else.." block. Add a new clause below the one for mvapich2 as follows.

In GIGC.mk:

else ifeq ($(ESMF_COMM),intel)
   # %%%%% Intel MPI %%%%%
   MPI_LIB     := -L$(MPI_ROOT)/lib -lmpi -lmpi++

In ESMA_base.mk:

else ifeq ($(ESMF_COMM),intel)
   INC_MPI := $(MPI_ROOT)/include
   LIB_MPI := -L$(MPI_ROOT)/lib -lmpi -lmpi++

If you have tried all of this and are still having trouble, please contact the GEOS-Chem Support Team. If you have a new MPI implementation working please also let us know! We may want to bring in your updates as a permanent option for use by the wider community.

Previous | Next | GCHP Home