GEOS-Chem Newsletter April 2010
Dear GEOS-Chem Users,
Here is your April 2010 Newsletter. Better late than never!
Thank you for your continued support of GEOS-Chem,
Bob Yantosca and Claire Carouge
- 1 GEOS-Chem model management and logistics
- 2 GEOS-Chem update
- 3 Column code update
GEOS-Chem model management and logistics
GEOS-Chem Steering Committee
The last GEOS-Chem Steering Committee telecon took place on March 9, 2010. Minutes of this meeting (and past meetings) are available HERE.
The next Steering Committee Telecon shall take place on Tuesday, June 29, 2010 at 10:30 EST. Mark your calendars!
If you would like to bring any items to the attention of the Steering Committee before the next telecon, please contact your Working Group Chairperson(s).
GEOS-Chem Working Groups
Please see the GEOS-Chem Working Groups web page for links to each of the Working Groups.
We encourage each GEOS-Chem user to join the Working Group that is most relevant to his/her area of research.
New and improved pages
In the last month, several new pages have been added to the GEOS-Chem wiki. Many other existing wiki pages have also received a "face-lift" in order to make them easier to navigate. In particular:
- A new GEOS-Chem performance page has been added.
- A page which describes Linking GEOS-Chem to CMAQ has been added.
- The GEOS-Chem supported platforms and compilers page has been "pruned"; new info was added and obsolete info removed.
- Extra information has been added to the CO2 simulation wiki page.
We encourage all GEOS-Chem code developers and users to check the wiki frequently, as this is the place where the latest information about GEOS-Chem will be posted. The wiki is designed to be a two-way street of communication. Users should feel free to add content to the wiki pages that are most closely related to their research.
In particular, the GEOS-Chem Support Team has started a new effort to make sure that all 3rd-party code and data that is submitted into GEOS-Chem has a corresponding wiki page. This will ensure that all information can be shared transparently.
We would like to update the timing information contained on the GEOS-Chem supported platforms and compilers page. If you have run the 1-month benchmark on your system, please consider updating this page with the following information:
- GEOS-Chem model version
- Platform/OS combination
- Compiler version
- Number of CPU's
- Wall time
- Contact person
We have removed the timing information from some of the more ancient versions of GEOS-Chem, in favor of more recent model releases.
- Photolysis is now computed at midpoint of chemistry timestep
- Option to use Caltech isoprene chemistry (F. Paulot)
- ISORROPIA II (H. Pye, T. Nenes)
- Updated aerosol optical properties for FAST-J photolysis (R. Martin, C. Heald)
- Modifications to SOA formation (Aerosols Working Group)
- SOA formation from aromatics (D. Henze)
- Speciated biogenic emissions from MEGAN v2.1 now used in SOA code (H. O. T. Pye)
- Global 1 x 1.25 simulation capability (L. Lamsal)
- Modifications to / Creation of the GEOS-5 0.5 x 0.667 N. American and European Nested Grid simulation (A. van Donkelaar)
- TOMAS aerosol microphysics option (W. Trivitayanurak, D. Westervelt, J. Pierce)
- Extension of annual anthropogenic scale factors to 2006 (A. van Donkelaar)
- EMEP emissions extended to 2007 and Seasonality extended to SOx, CO, and NH3 (A. van Donkelaar)
GEOS-Chem v8-03-01 is the first standard version of GEOS-Chem to contain an aerosol microphysics option. The TOMAS aerosol microphysics code from Carnegie-Mellon can be invoked to perform simulations which track both aerosol size and number.
The CMU group will perform aerosol microphysics benchmark simulations in order to ensure the scientific integrity of the TOMAS code. These simulations, however, will not become part of the standard GEOS-Chem benchmark suite (i.e. the 1-yr and 1-month benchmarks). The GEOS-Chem Support Team is not responsible for TOMAS support (other than making sure the latest TOMAS code is added to the GEOS-Chem standard code).
All inquiries about TOMAS should be directed to Dan Westervelt at CMU.
We have plans to include a second aerosol microphysics package, the APM microphysics code from SUNY Albany into GEOS-Chem v8-03-02. Work on this will commence once v8-03-01 is released.
Version control with Git
GEOS-Chem v8-03-01 is now the first version of GEOS-Chem to use the Git source code management system instead of CVS. Git is a powerful, flexible, simple-to-use software package that contains useful GUI tools for managing source code revisions. It is open-source software, and is freely available.
Please see our Version control with Git wiki page for more information. We have also posted some links to tutorials and videos which explain how Git works.
NOTE: Git will be the preferred method for downloading the GEOS-Chem source code and run directories. We will no longer produce the GEOS-Chem*.tar.gz files (which was the previous method of distributing the GEOS-Chem source code). Please install (or ask your IT dept to install) Git on your systems as soon as possible.
In the pipeline
The following updates will be added into GEOS-Chem following the v8-03-01 release.
|APM aerosol microphysics
|APM code is ready; Currently slated for inclusion into v8-03-02.
|Updated CO2 simulation
|Code has been received by G-C support team is imminent. Will be installed in v8-03-02 immediately after v8-03-01 is released.
|Updated mercury simulation with improved soil model (GTMM)
|Code has been delivered to G-C support team; Slated for inclusion into v8-03-02 or a later version.
For a complete list of outstanding code updates, please see our GEOS-Chem model development priorities page.
Column code update
The GEOS-Chem column code continues to progress quickly. Bob Yantosca and Arlindo da Silva from GSFC are working on interfacing the GEOS-Chem column code to the GEOS-5 GCM.
Bob and Arlindo have created an ESMF Gridded Component to which the GEOS-Chem column code is attached. The Gridded Component can initialize, run, and finalize the GEOS-Chem column code without any software errors (such as segmentation faults, bus errors, etc). However, much work remains to ensure that the test simulation is producing proper results. The testing is ongoing.
--Bob Y. 15:24, 28 April 2010 (EDT)