GEOS-Chem version numbering system
Alphanumeric versioning system (now retired)
GEOS-Chem versions v9-02 through v11-02 have used an alphanumeric version number system to denote major versions as opposed to intermediate checkpoint versions. The table below lists several previous GEOS-Chem versions that used the this system.
|Action||Resulting version #|
|GEOS-Chem 10 public release||v10-01-public|
|First intermediate checkpoint of v11-01
|Second intermediate checkpoint of v11-01
|...etc Intermediate checkpoint versions...||v11-02c thru v11-01k|
|v11-01 "provisional" release
|GEOS-Chem v11-01 "public" release||v11-01-public|
|First intermediate checkpoint version of v11-02
|Second intermediate checkpoint version of v11-02
|...etc intermediate checkpoint versions ...||v11-02c thru v11-01f|
|v11-02 "release candidate"
|GEOS-Chem v11-02 final release
- All intermediate checkpoint versions were validated with a 1-month benchmark. Some intermediate checkpoint versions were validated with both 1-month and 1-year benchmarks. For clarity, we have not denoted the checkpoint releases for which 1-year benchmarks were also done.
- We have listed the version numbers in the table from oldest at the top to newest at the bottom. This more clearly shows the progression of version numbers. Note that this is the opposite of how versions are displayed in the Git history.
Limitations of the alphanumeric system
Prior to GEOS-Chem v11-02, intermediate checkpoint versions were not made available to GEOS-Chem users. Because of this, the last version in a series was always denoted as the "public" release (e.g v9-02-public, v10-01-public, etc.). This made sense at the time, because the "public" version was the version that GEOS-Chem users would would be able to download. The GEOS-Chem manual was only updated for each "public" version.
We have since discontinued the term "public version", as GEOS-Chem users are now invited to download any intermediate checkpoint release when starting a research project. The last version in the v11-02 series will now be named v11-02-final.
The practice of issuing a "provisional" or "release candidate" version immediately prior to the "final" release in a series began with GEOS-Chem v9-02. This was intended as a way of allowing users to take the "release candidate" version for a test-drive and to report any bugs or issues to the GEOS-Chem Support Team. The GCST would then be able to fix the issues for the "final" release.
While this versioning system worked well, it is not in line with accepted software industry best practice. Also the change in terminology from "public" to "final" and from "provisional" to "release candidate", while well-intentioned, can lead to confusion. Furthermore, an intermediate checkpoint version number such as v11-02c does not distinguish between the addition of new features as opposed to bug fixes. For these reasons, we are migrating to a purely numeric version numbering system, as discussed in the following section.
Numeric versioning system
In order to transition between the alphanumeric and numeric versioning systems, the upcoming GEOS-Chem release v11-02-final will also carry the version number 12.0.0.
In order to conform more closely to industry-standard software versioning protocol, we shall retire the use of alphanumeric version numbers (e.g. v11-02a) for GEOS-Chem. Instead we shall adopt purely numeric version descriptors of the form X.Y.Z, as described in the table below. (This system is loosely based on the idea of Semantic Versioning.)
|Number||Description||When is this digit incremented?|
|X||Major version number.
||X is incremented when we introduce an update that immediately breaks backward compatibility with the previous series of GEOS-Chem versions.
Examples of when the major number was changed in past versions of GEOS-Chem:
|Y||Benchmark number (aka feature number)
||Y changes when a new set of features is validated with a 1-month benchmark.
NOTE: Any change to a GEOS-Chem run directory (that is, modifying input.geos, HEMCO_Config.rc, HISTORY.rc, etc.) necessitates that Y be incremented.
|Z||Bug fix number (aka patch number)||Z changes when the following types of updates are added to the code:
NOTE: All patched X.Y.Z versions of GEOS-Chem will remain compatible with the run directories from the last benchmarked version (X.Y.0).
A sample progression of GEOS-Chem version numbers using the purely numeric versioning system is illustrated in the table below.
|Action||Resulting version #|
|The GEOS-Chem v11-02 major release is issued||v11-02-final, aka 12.0.0|
|Bugs are fixed, but this does not break backwards compatibility|| 12.0.1|
|A collection of new features is added
|A bug identified during the benchmark is fixed||12.1.1|
|Another collection of new features is added
|A bug identified during the benchmark is fixed||12.2.1|
|The next GEOS-Chem "release candidate" is issued
||12.N.0 (N is TBD)|
|The next major version of GEOS-Chem is released||13.0.0|
The GEOS-Chem manual will be rewritten for each "major" release X.0.0. But the GEOS-Chem wiki will be updated for each benchmark and patch version X.Y.Z. Since GEOS-Chem v11-01, much of the GEOS-Chem manual now points to information on the GEOS-Chem wiki.
GEOS-Chem users will no longer need to wait for a major release (X.0.0), but instead can download the most recent version (X.Y.Z) when starting a new research project.
As of July 2021, We are currently in the process of migrating the GEOS-Chem Classic manual from the GEOS-Chem wiki to . This will allow us to archive manual pages for older versions (which is difficult to do on the wiki). Other manual pages (GCHP, HEMCO) have already been ported to ReadTheDocs.
GEOS-Chem Classic and GCHP versions
For the sake of clarity, GEOS-Chem Classic and GCHP will be assigned the same version number. It may be possible that a given version only contains updates for GEOS-Chem Classic, or GCHP, but not both.