Difference between revisions of "GEOS-Chem Support Team"

From Geos-chem
Jump to: navigation, search
(GCST Members)
(GCST Members)
Line 11: Line 11:
=== GCST Members ===
=== GCST Members ===
The table below lists full-time members of the GCST:
The table below lists members of the GCST:
{| border=1 cellspacing=0 cellpadding=5
{| border=1 cellspacing=0 cellpadding=5
Line 90: Line 90:
*Data management on Compute Canada
*Data management on Compute Canada
*Processing GMAO met data for input into GEOS-Chem
*Processing GMAO met data for input into GEOS-Chem
|Jourdan He
|Research Assistant

Revision as of 17:31, 2 June 2022

This page contains information about the GEOS-Chem Support Team (aka GCST).

Contact information

General Inquiries

If you are reporting a GEOS-Chem bug or technical issue, then please also see our Submitting GEOS-Chem support requests wiki page for more detailed instructions.

For other requests, please use this email address: geos-chem-support [at] g.harvard.edu.

GCST Members

The table below lists members of the GCST:

Name Title Focus
Bob Yantosca
(GitHub: @yantosca)
Senior Software Engineer Lead developer for:
  • Fundamental software development
  • Documentation
  • User support

Other areas of focus:

  • Debugging and testing
  • High-performance computing
  • AWS cloud computing support and development
Melissa Sulprizio
(GitHub: @msulprizio)
Senior Scientific Programmer Lead developer for:

Other areas of focus:

  • Fundamental software development
  • Debugging and testing
  • Documentation
  • User support
Lizzie Lundgren
(GitHub: @lizziel)
Senior Scientific Software Engineer Lead developer for:
  • GEOS-Chem in GEOS and CESM
  • Liaison between GCST and GMAO

Other areas of focus:

  • Fundamental software development
  • High performance computing
  • Debugging and testing
  • User support
Lucas Estrada
(GitHub: @laestrada)
Scientific Programmer Lead developer for:
  • GCPy python visualization package
  • AWS cloud computing support and development

Other areas of focus:

  • Fundamental software development
  • Debugging and testing
  • User support
  • Documentation
Liam Bindle
(GitHub: @LiamBindle)
Scientific Applications Software Engineer Lead developer for:
  • GCHP stretched-grid development
  • GCHP on AWS
  • Continuous Integration and Delivery (CI/CD)

Other areas of focus:

  • General GCHP development
  • Improving GCHP usability
  • GCHP user support
Yanshun Li
(GitHub: @YanshunLi-washu)
Doctoral Student Lead developer for:
  • Data management on Compute Canada
  • Processing GMAO met data for input into GEOS-Chem
Jourdan He Research Assistant TBD

GCST Liaisons

The table below lists contact persons for specific GEOS-Chem applications that are not directly supported by the GCST:

Application Liaison
GEOS-Chem Adjoint Daven Henze
APM Fangqun Yu
GEOS-Chem Nested Model Yuxuan Wang (GitHub: @yxw246) and
Lin Zhang
Hg and POPs Colin Thackray (GitHub: cpthackray)
RRTMG Sebastian Eastham (GitHub: @sdeastham)
TOMAS Jeff Pierce


The GEOS-Chem Support Team now uses issue trackers attached to the relevant Github repositories to manage its workflow. For more information, please see:

Product Issue Tracker @ Github
GEOS-Chem code geoschem/geos-chem/issues
GEOS-Chem Unit Tester geoschem/geos-chem-unittest/issues
Current GCHP
(will be retired in 13.0.0)
(will be added in 13.0.0)
GEOS-Chem cloud tutorial geoschem/geos-chem-cloud/issues
GCPy geoschem/gcpy/issues
HEMCO geoschem/HEMCO/issues


The GEOS–Chem Support Team uses robust source code management techniques to facilitate the open-source development of GEOS–Chem, maintain code integrity, ensure proper documentation and traceability, and support users. Its principal activities are as follows:

  1. Implementation of new GEOS–Chem developments into the standard model. Most developments of the model are initiated by individual users for their own scientific purposes. Their implementation into the standard model is led by the Support Team in collaboration with the developer. We use the Git software management system (Git, www.git-scm.com) to ensure that each user’s source code revisions can be tracked properly.
  2. Fundamental GEOS–Chem development. The Support Team conducts fundamental model development essential for the long term. This includes upgrades to new versions of GEOS meteorological data, acquisition and storage of data, implementation of new coding and data structures, and technical updates.
  3. Benchmarking of new versions. The Support Team benchmarks each new version of GEOS–Chem following a standard protocol to ensure the traceability and integrity of the model.
  4. Documentation, communication, and education. The Support Team maintains the GEOS–Chem User’s Manual and wiki pages, publishes monthly e-newsletters, welcomes new users, offers programming guidelines and advice, develops standards for coding and documentation (GEOS–Chem Style Guide), instructs users on the use of various software tools, and conducts model clinics at Users’ Meetings.
  5. Development of supporting software. The Support Team publishes open-source software for the benefit of the GEOS–Chem and broader modeling community. It maintains GAMAP, a collection of IDL programs that facilitates the analysis and visualization of CTM data. GAMAP is the standard visualization tool for GEOS–Chem and is updated regularly to maintain compatibility with the standard model.

Specific tasks handled by the GEOS-Chem Support Team

The GEOS-Chem Support Team shall be responsible for the following tasks:

  1. Managing the "standard" GEOS-Chem model for distribution:
  2. Publishing the relevant documentation for GEOS-Chem using the following media:
  3. Validating the "standard" simulation by means of:
  4. Processing the meteorological data products that are used to drive GEOS-Chem simulations
  5. Adding updates from GEOS-Chem developers into the "standard" GEOS-Chem code repository
  6. Distributing various software packages for visualization and data processing
  7. Assisting GEOS-Chem developers and users with technical problems and issues
  8. Development of GCHP, which is the MPI implementation of GEOS-Chem

Responsibilities of the GEOS-Chem User Community

Please keep in mind that the GEOS-Chem Support Team primarily works with the GEOS-Chem source code. If your question is more scientific than technical, then the GEOS-Chem Support Team might not possess the expertise to answer your question fully. In these cases we request that you contact the relevant GEOS-Chem Working Group or direct your question to other members of the GEOS-Chem user community who can better assist you.

We expect that the GEOS-Chem user community shall be responsible for the scientific content and validation of the following GEOS-Chem simulations:

  1. Aerosol-only simulations
  2. Aerosol Microphysics Simulations (e.g. TOMAS, APM)
  3. CH4 simulations
  4. CO and Tagged CO simulations
  5. CO2 and Tagged CO2 simulations
  6. Tagged O3 simulations
  7. Hg and Tagged Hg simulations
  8. Nested-grid simulations
  9. 222Rn-210Pb-7Be simulations

If you use one of these types of GEOS-Chem simulations, the GEOS-Chem Support Team will of course be happy to assist you in including your updates into the standard code, or in resolving technical issues.

Regrettably, the GEOS-Chem Support Team cannot assist you with the following:

  1. Teaching you how to program in Fortran, Python IDL, Matlab, Perl, etc.
  2. Installing libraries or software on your system
  3. Installing hardware on your system
  4. Setting up web pages for your group

We invite you to read our GEOS-Chem basics wiki page for more information on these topics.

For more information about the expectations and responsibilities of GEOS-Chem users please see the welcome letter for new GEOS-Chem users.