- Hardware and Software Requirements
- Downloading Source Code
- Obtaining a Run Directory
- Setting Up the GCHP Environment
- Basic Example Run
- Run Configuration Files
- Advanced Run Examples
- Output Data
- Developing GCHP
GCHP is built to wrap around a standard GEOS-Chem Classic installation. The first step to obtaining GCHP is therefore to clone the standard GEOS-Chem source code repository. Enabling GCHP functionality simply involves the added step of cloning the GCHP source code repository to store as a subdirectory within GEOS-Chem.
Acquiring the GCHP subdirectory does not change anything in the standard GEOS-Chem code; you can use the same source code to run regular non-GCHP GEOS-Chem simulations. However, we recommend that you keep separate GEOS-Chem source code directories for use with GCHP and GEOS-Chem Classic, e.g. Code.12.0.0_gchp and Code.12.0.0_gcclassic. This avoids confusion and extra work since each requires separate compilation. You also may want to develop and test them separately
Please note that certain files in GEOS-Chem Classic source code will be present but ignored when running GCHP. Most notably this includes main.F in the GeosCore directory; much of the functionality of this file is done instead in the GCHP/gigc_chunk_mod.F90.
Step 1: Download GEOS-Chem
Clone the GEOS-Chem repository on Github to a directory name of your choosing.
git clone firstname.lastname@example.org:geoschem/geos-chem.git Code.gchp
Take note of the path where the code was downloaded. In this example let's say the source code is stored at /mypath/GCHP/Code.gchp.
Note for advanced git users: If you plan on developing GEOS-Chem updates to submit for inclusion in the model we recommend that you fork the repository on Github and clone it from your own account. You can then make pull requests when you are ready to submit updates to the GEOS-Chem Support Team. If you have no idea what this means do not worry about it.
Step 2: Download GCHP within GEOS-Chem
Navigate to your GEOS-Chem code directory that you just downloaded and clone the GCHP repository on Github:
cd /mypath/GCHP/Code.gchp git clone email@example.com:geoschem/gchp.git GCHP
Step 3: Know Your Version
When you clone GEOS-Chem and GCHP you will always get the master branch. This branch is set on the last benchmarked version of GEOS-Chem. You can determine the version label by typing "git log" within each repository and looking at the git tag string printed for the top-most commit. Always be sure that the versions you have in the two repositories are compatible.
If you would like an earlier version you can checkout the version tag for that specific version in both the GEOS-Chem and GCHP repositories. To see a list of available tags for a repository type "git tag". To checkout a tagged version type "git checkout tags/tagname".
When you checkout a tag beware that you will be in what is called a detached HEAD status. This means you are not officially on a git branch. Committing in this state risks losing your changes since they are not associated with an actual git branch. If you plan on developing code in the version you checkout you should therefore create a branch to work in: "git checkout -b mybranch". However, we request that new updates always be built off of the master branch that is current at the time you begin work. We further recommend that you pull in future version updates as they are released.
If you are in doubt about how to use git with GEOS-Chem please contact the GEOS-Chem Support Team for help.