Documentation of the Changes in INT2LM
Version 1.23

02.10.2013

This version is the (hopefully) last consolidation version for the new release INT2LM 2.0. It contains again some technical changes and bug fixes.

Contents:

  1. Bug fix for array of vertical coordinate parameters pv_in, pv_out
  2. KIND parameters for grib_api
  3. Using of Namelist variable: l_ke_in_gds
  4. Using of names: vcoord, refatm
  5. Technical Changes and Bug Fixes
  6. Changes in the Namelists
  7. Changes of the Results

1. Bug fix for array of vertical coordinate parameters pv_in, pv_out

(by Uli Schättler)

pv_in, pv_out were defined as single precision values, but were treated in the INT2LM as double precision fields, especially in the communication. This caused severe memory corruption in several applications. Now they are defined as double precision fields in data_int2lm_io.f90, io_utilities.f90 and src_lm_output.f90.

Back to Contents


2. KIND parameters for grib_api

(by Uli Schättler)

The integer kindOfSize has lately been implemented as an 8-byte Integer at ECMWF in grib-api 1.11.0. An integer of this KIND is taken from subroutine grib_read_from_file (which gives the length of the message in bytes) in read_gribapi and passed to the MPI_SEND routine. But MPI_SEND does not interpret this integer correctly (not in the "INCLUDE mpif.h" variant, but also not in the "USE mpi" variant, although it compiles without error.

Therefore the value of the length of the message is transferred to a 4-byte integer before it is passed to MPI_SEND.

The same problem occured in subroutine write_gribapi.

Back to Contents


3. Using of Namelist variable: l_ke_in_gds

(by Uli Schättler)

There are two different ways of coding vertical coordinate parameters (and some additional parameters for the reference atmosphere and the vertical coordinate type). Which way is chosen in INT2LM and the COSMO-Model can be specified by the Namelist variable l_ke_in_gds:

The following table shows the vertical coordinate parameters for both types. The name pv is taken from the grib_api convention for the vertical coordinate parameters and is now also used in the COSMO-Model.

Entry in pv Old specifications New specifications
pv( 1) p0sl ivctype
pv( 2) t0sl ke
pv( 3) dt0lp p0sl
pv( 4) vcflat t0sl
pv( 5) vcoords(1) dt0lp
pv( 6) vcoords(2) vcflat
pv( 7) vcoords(3) vcoords(1)
pv( 8) vcoords(4) vcoords(2)
etc.
pv( 3+ke1) vcoords(ke1-1) vcoords(ke1-3)
pv( 4+ke1) vcoords(ke1) vcoords(ke1-2)
pv( 4+ke1+1) ivctype vcoords(ke1-1)
pv( 4+ke1+2) svc1 vcoords(ke1)
pv( 4+ke1+3) svc2 svc1
pv( 4+ke1+4) nfltvc svc2
pv( 4+ke1+5) delta_t nfltvc
pv( 4+ke1+6) h_scal delta_t
pv( 4+ke1+7) ---- h_scal

The default for this namelist variable has been changed to: .TRUE. Therefore all GRIB1 vertical coordinate parameters are now coded in the new way. Note that the values after the vcoords depend on other namelist settings for the reference atmosphere and the vertical coordinate type.

If the old way of coding should be used, l_ke_in_gds has to be set to .FALSE. explicitely.

Back to Contents


4. Using of names: vcoord, refatm

(by Ulrich Schättler)

In version 1.22, new types were used to hold all vertical coordinate parameters and also parameters of the reference atmosphere. While names with suffixes _in and _out were used then in INT2LM and also in the COSMO-Model, it was decided to use _in in the INT2LM for the incoming fields from coarse grid models and the names without suffix for the corresponding variables of the COSMO grid and also throughout the whole COSMO-model.

Back to Contents


5. Technical Changes and Bug Fixes

Back to Contents


6. Changes of the Namelists

There were the following changes for the Namelist variables:

Group Name Meaning Default
/IOCTL/ l_ke_in_gds new default explicit GDS entry for number of model levels .TRUE.

Back to Contents


6. Changes of the Results

There are no changes of results!

Back to Contents