GEOS-Chem v11-01

From Geos-chem
Revision as of 14:30, 5 May 2015 by Melissa Payer (Talk | contribs) (New page: === History === The table below shows the previous, current, and successive versions of GEOS-Chem: {| border=1 cellspacing=0 cellpadding=5 |-align="center" !width="250px"|Previous versi...)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

History

The table below shows the previous, current, and successive versions of GEOS-Chem:

Previous version This version Next version
GEOS-Chem v10-01 GEOS-Chem v11-01 TBD
PROVISIONAL RELEASE 01 May 2015 TBD TBD
View v10-01 benchmark history View v11-01 benchmark history TBD

--Melissa Sulprizio 10:30, 5 May 2015 (EDT)

What's new in this version

NOTE: v11-01a, v11-02b, etc. denote 1-month benchmark simulations, which are designed to evaluate GEOS-Chem's performance at intermediate stages of development.

v11-01a

TBD

New data directories

The following new data directories have been added for GEOS-Chem v11-01. You will have to download the directories relevant to your simulation.

Validation

In this section we provide information about the benchmarks and tests that we have done to validate GEOS-Chem v11-01.

1-month and 1-year benchmarks

For complete information about the benchmark simulations used to validate GEOS-Chem v11-01, please see our GEOS-Chem v11-01 benchmark history wiki page.

--Melissa Sulprizio 10:30, 5 May 2015 (EDT)

Unit tests for GEOS-Chem v11-01

We performed a full set of unit tests on GEOS-Chem before submitting each 1-month benchmark. Click on the links below to see the results from each set of unit tests:

Unit test Date Notes
TBD TBD

--Melissa Sulprizio 10:30, 5 May 2015 (EDT)

Previous issues now resolved in GEOS-Chem v11-01

The following bugs and/or technical issues have now been resolved in GEOS-Chem v11-01.

Outstanding issues not yet resolved in GEOS-Chem v11-01

The following issues have not yet been resolved in GEOS-Chem v11-01. Some of these issues represent questions of open research rather than bugs in the source code.