Skip to content

Latest commit

 

History

History
78 lines (56 loc) · 6.48 KB

CONTRIBUTING.md

File metadata and controls

78 lines (56 loc) · 6.48 KB
Raw

Contributing Guidelines

Thank you for looking into contributing to GEOS-Chem! GEOS-Chem is a grass-roots model that relies on contributions from community members like you. Whether you're new to GEOS-Chem or a longtime user, you're a valued member of the community, and we want you to feel empowered to contribute.

Updates to the GEOS-Chem model benefit both you and the entire GEOS-Chem community. You benefit through coauthorship and citations. Priority development needs are identified at GEOS-Chem users' meetings with updates between meetings based on GEOS-Chem Steering Committee (GCSC) input through Working Groups.

We use GitHub and ReadTheDocs

We use GitHub to host the GEOS-Chem Classic source code, to track issues, user questions, and feature requests, and to accept pull requests: https://github.com/geoschem/geos-chem. Please help out as you can in response to issues and user questions.

GEOS-Chem Classic documentation can be found at geos-chem.readthedocs.io.

When should I submit updates?

Submit bug fixes right away, as these will be given the highest priority. Please see "Support Guidelines" for more information.

Submit updates (code and/or data) for mature model developments once you have submitted a paper on the topic. Your Working Group chair can offer guidance on the timing of submitting code for inclusion into GEOS-Chem.

The practical aspects of submitting code updates are listed below.

How can I submit updates?

We use GitHub Flow, so all changes happen through pull requests. This workflow is described here.

As the author you are responsible for:

  • Testing your changes
  • Updating the user documentation (if applicable)
  • Supporting issues and questions related to your changes

Process for submitting code updates

  1. Contact your GEOS-Chem Working Group leaders to request that your updates be added to GEOS-Chem. They will will forward your request to the GCSC.
  2. The GCSC meets quarterly to set GEOS-Chem model development priorities. Your update will be slated for inclusion into an upcoming GEOS-Chem version.
  3. Create or log into your GitHub account.
  4. Fork the relevant GEOS-Chem repositories into your Github account.
  5. Clone your forks of the GEOS-Chem repositories to your computer system.
  6. Add your modifications into a new branch off the main branch.
  7. Test your update thoroughly and make sure that it works. For structural updates we recommend performing a difference test (i.e. testing against the prior version) in order to ensure that identical results are obtained).
  8. Review the coding conventions and checklists for code and data updates listed below.
  9. Create a pull request in GitHub.
  10. The GEOS-Chem Support Team will add your updates into the development branch for an upcoming GEOS-Chem version. They will also validate your updates with benchmark simulations.
  11. If the benchmark simulations reveal a problem with your update, the GCST will request that you take further corrective action.

Coding conventions

The GEOS-Chem codebase dates back several decades and includes contributions from many people and multiple organizations. Therefore, some inconsistent conventions are inevitable, but we ask that you do your best to be consistent with nearby code.

Checklist for submitting code updates

  1. Use Fortran-90 free format instead of Fortran-77 fixed format.
  2. Include thorough comments in all submitted code.
  3. Include full citations for references at the top of relevant source code modules.
  4. Remove extraneous code updates (e.g. testing options, other science).
  5. Submit any related code or configuration files for GCHP along with code or configuration files for GEOS-Chem Classic.

Checklist for submitting data files

  1. Choose a final file naming convention before submitting data files for inclusion to GEOS-Chem.
  2. Make sure that all netCDF files adhere to the COARDS conventions.
  3. Concatenate netCDF files to reduce the number of files that need to be opened. This results in more efficient I/O operations.
  4. Chunk and deflate netCDF files in order to improve file I/O.
  5. Include an updated HEMCO configuration file corresponding to the new data.
  6. Include a README file detailing data source, contents, etc.
  7. Include script(s) used to process original data
  8. Include a summary or description of the expected results (e.g. emission totals for each species)

Also follow these additional steps to ensure that your data can be read by GCHP:

  1. All netCDF data variables should be of type float (aka REAL*4) or double (aka REAL*8).
  2. Use a recent reference datetime (i.e. after 1900-01-01) for the netCDF time:units attribute.
  3. The first time value in each file should be 0, corresponding with the reference datetime.

How can I request a new feature?

We accept feature requests through issues on GitHub. To request a new feature, open a new issue and select the feature request template. Please include all the information that migth be relevant, including the motivation for the feature.

How can I report a bug?

Please see "Support Guidelines".

Where can I ask for help?

Please see "Support Guidelines".