Difference between revisions of "GEOS-Chem v8-02-03"

From Geos-chem
Jump to: navigation, search
(New page: == Overview == BETA RELEASE TBD Description to follow == Previous issues now resolved in v8-02-03 == Description to follow == Outstanding issues not yet resolved in v8-02-03 == Descri...)
 
Line 1: Line 1:
 
== Overview ==
 
== Overview ==
BETA RELEASE TBD
 
  
Description to follow
+
BETA RELEASE TBD -- still in testing
 +
 
 +
Will contain everything in [[GEOS-Chem v8-02-02]], plus:
 +
 
 +
*Kpp chemical solver package (Adrian Sandu group @ Virginia Tech group)
 +
*ICOADS ship emissions (Chulkyu Lee)
 +
*Use of GEOS-5 ozone columns (C. Carouge, still in validation)
 +
*Removal of support for obsolete SGI and COMPAQ compilers
  
 
== Previous issues now resolved in v8-02-03 ==
 
== Previous issues now resolved in v8-02-03 ==
  
Description to follow
+
=== Format problem in planeflight_mod.f ===
 +
 
 +
Jingqiu Mao reported a problem in the <tt>plane.log</tt> output files, in which it looked like some tracers had abnormally large values.
 +
 
 +
'''''Philippe Le Sager (plesager@seas.harvard.edu) wrote:'''''
 +
 
 +
:I found a solution.  The problem is that Fortran output in ASCII switches between 2 formats:
 +
 
 +
    1.234E-12
 +
    1.234-12
 +
 
 +
:Correct, the E can disappear. And that confuses IDL. With the format specified by <tt>planeflight_mod.f</tt> (line 1237), it happens when the exponent is less than -100.
 +
 
 +
:To keep the routine general, you can force the number of digit in the exponent with a 'e' in the format descriptor as follows:
 +
 
 +
    y = -1.233d-122
 +
    write(6, '(es10.3)'  ), y  ! what is used now
 +
    write(6, '(es11.3e3)' ), y  ! what we should use instead
 +
    write(6, '(es12.3e4)' ), y
 +
 
 +
:gives
 +
 
 +
    -1.233-122
 +
    -1.233E-122
 +
    -1.233E-0122
 +
 
 +
:So replace <tt>(es10.3)</tt> with <tt>(es11.3e3)</tt> line 1237 of <tt>planeflight_mod.f</tt> and that should fix it.
 +
 
 +
--[[User:Bmy|Bob Y.]] 11:35, 13 July 2009 (EDT)
 +
 
 +
=== Minor fixes for IBM XLF compiler ===
 +
 
 +
Gabriel Morin wrote:
 +
 
 +
:In <tt>ocean_mercury_mod.f</tt>, replace line 491:
 +
 
 +
          EF    = MAX( (0.63 - 0.02 * TC), 0.0) ! keep export > 0
 +
 
 +
:by the line:
 +
 
 +
          EF    = MAX( (0.63d0 - 0.02d0 * TC), 0.0d0) ! keep export > 0
 +
 
 +
:In lightning_nox_mod.f, replace line 1441:
 +
 
 +
    CC = MAX( CCTHICK * 1d-3, 5.5 )
 +
 
 +
:by the line:
 +
 
 +
    CC = MAX( CCTHICK * 1d-3, 5.5d0 )
 +
 
 +
--[[User:Bmy|Bob Y.]] 11:35, 13 July 2009 (EDT)
  
 
== Outstanding issues not yet resolved in v8-02-03 ==
 
== Outstanding issues not yet resolved in v8-02-03 ==
  
 
Description to follow
 
Description to follow

Revision as of 15:35, 13 July 2009

Overview

BETA RELEASE TBD -- still in testing

Will contain everything in GEOS-Chem v8-02-02, plus:

  • Kpp chemical solver package (Adrian Sandu group @ Virginia Tech group)
  • ICOADS ship emissions (Chulkyu Lee)
  • Use of GEOS-5 ozone columns (C. Carouge, still in validation)
  • Removal of support for obsolete SGI and COMPAQ compilers

Previous issues now resolved in v8-02-03

Format problem in planeflight_mod.f

Jingqiu Mao reported a problem in the plane.log output files, in which it looked like some tracers had abnormally large values.

Philippe Le Sager (plesager@seas.harvard.edu) wrote:

I found a solution. The problem is that Fortran output in ASCII switches between 2 formats:
   1.234E-12
   1.234-12
Correct, the E can disappear. And that confuses IDL. With the format specified by planeflight_mod.f (line 1237), it happens when the exponent is less than -100.
To keep the routine general, you can force the number of digit in the exponent with a 'e' in the format descriptor as follows:
   y = -1.233d-122
   write(6, '(es10.3)'   ), y   ! what is used now
   write(6, '(es11.3e3)' ), y   ! what we should use instead
   write(6, '(es12.3e4)' ), y
gives
   -1.233-122
   -1.233E-122
   -1.233E-0122
So replace (es10.3) with (es11.3e3) line 1237 of planeflight_mod.f and that should fix it.

--Bob Y. 11:35, 13 July 2009 (EDT)

Minor fixes for IBM XLF compiler

Gabriel Morin wrote:

In ocean_mercury_mod.f, replace line 491:
          EF     = MAX( (0.63 - 0.02 * TC), 0.0) ! keep export > 0
by the line:
          EF     = MAX( (0.63d0 - 0.02d0 * TC), 0.0d0) ! keep export > 0
In lightning_nox_mod.f, replace line 1441:
    CC = MAX( CCTHICK * 1d-3, 5.5 )
by the line:
    CC = MAX( CCTHICK * 1d-3, 5.5d0 )

--Bob Y. 11:35, 13 July 2009 (EDT)

Outstanding issues not yet resolved in v8-02-03

Description to follow