Linoz stratospheric ozone chemistry

Overview

NOTE: Page under construction

The Linoz stratospheric ozone chemistry package ...

Authors and collaborators:

• Chris McLinden (UC Irvine ?)
• Philip Cameron-Smith (LLNL)
• Brendan Field (formerly Harvard)
• Dylan Jones (U. Toronto)
• Jane Liu (U. Toronto)

Implementation notes

Linoz has been implemented into GEOS-Chem v8-02-04.

Code structure

The main-level Code directory has now been divided into several subdirectories:

GeosCore/    GEOS-Chem "core" routines
GeosUtil/    "Utility" modules (e.g. error_mod.f, file_mod.f, time_mod.f, etc.
Headers/     Header files (define.h, CMN_SIZE, CMN_DIAG, etc.)
ISOROPIA/    Directory where ISORROPIA II code resides   
KPP/         KPP solver directory structure
bin/         Directory where executables are placed
doc/         Directory where documentation is created
help/        Directory for GEOS-Chem Help Screen
lib/         Directory where library files are placed
mod/         Directory where module files are placed
obsolete/    Directory where obsolete versions of code are archived

Linoz consists of the following files:

• GeosCore/linoz_mod.f: Source code file with Linoz chemistry subroutines
• GEOS_1x1/Linoz_200910/Linoz_March2007.dat: File with ozone climatology in the GEOS_1x1 data directory

Validation

Dylan Jones (dbj@atmosp.physics.utoronto.ca) wrote:

Testing [the Linoz code in GEOS-Chem v8-02-04 was more difficult that I thought. I began by trying to compare the output of v8-02-04 with our previous runs with v8-02-01. I accounted for the changes in the transport_mod.f and I tried to undo the changes in when the diagnostics are archived in v8-02-04, but I was still getting large differences between v8-02-04 and v8-02-01. I finally gave up on this since I may have made a mistake in reverting to the old way of doing the diagnostics in v8-02-04. In the end I took the new linoz code from v8-02-04 and used it in v8-02-01. I ran two GEOS-5 full chemistry simulations for 2007 and the output were consistent over the full year.

I think that it is safe to release [Linoz in v8-02-04]. However, we should acknowledge that it was [only] tested in v8-02-01, since I was not able to assess the quality of the output in v8-02-04.

--Bob Y. 11:09, 4 February 2010 (EST)

Known issues

None at this time.