Relationship between spectral and grid resolution

IFS is a model of two resolutions: the spectral resolution determining the number of retained waves and the corresponding grid onto which these waves can be transformed. A greater spectral resolution can improve the forecast quality whilst reduced Gaussian grid resolutions can improve the efficiency of the model.

IFS model grids

IFS can make use of different latitude-longitude grids for the same spectral resolution. Each grid type offers different advantages and disadvantages.  A 'reduced' grid is one in which the number of gridpoints around each latitude circle is reduced as the poles are approached. A full grid, or 'regular' grid, has the same number of points around each latitude circle. The terms 'linear', 'quadratic' and 'cubic' refer to the number of gridpoints used to describe the shortest waves retained in spectral space. For example, linear grids use two gridpoints to describe the shortest wave, and so on.

A linear grid allows a higher spectral truncation for the same number of gridpoints as a quadratic or cubic grid. Linear and quadratic in this sense means enough gridpoints are available to compute the linear and quadratic terms in the equations respectively. Likewise a cubic grid has more gridpoints per spectral wavenumber and provides more gridpoints to describe the highest wavenumbers. However, aliassing of the quadratic (and cubic) terms in the model equations can result from using linear grids, which needs to be compensated for in the model formulation. A cubic grid removes aliassing and the need for additional filters.

For more information about IFS grids please see: OpenIFS: Gaussian grids and OpenIFS: Octahedral grid in the OpenIFS User Guide.

The following table describes the different grid types together with the filename extension used in the ifsdata filesnames (see: Download OpenIFS).

Linear reduced and Cubic Octahedral are by far the most commonly used, with cubic octahedral grids typically used for the higher resolutions.

The cubic grids are only available in OpenIFS 43r3 and later. They were introduced in the IFS at cycle 41r2, operational March 2016.

Model timestep

The timestep depends on the horizontal resolution and the choice of the grid. ECMWF typically use a long a timestep as possible for efficiency reasons. However, there are times when this may result in some of the semi-Lagrangian trajectories going underground (messages can be seen in the model logfile), though generally this is not a problem.

Recommended maximum timesteps are given in the table below. Shorter timesteps can be used, though note that the model will not produce the exact same result between two forecasts with different timesteps.

Wave model grids

The ECMWF Wave Model, a component of IFS, uses a different grid to the atmospheric grid in IFS.

The wave model uses an irregular latitude-longitude grid. For such grids the distance between latitudes is set to a certain resolution in degrees, where the number of grid points per latitude is adjusted so that the actual distance between points on each latitude is roughly the same as the one between 2 consecutive latitudes.

There is an approximate match between the number of latitudes in the atmospheric grid and the wave model grid, it is still a good approximation to run the wave model on a slightly coarser grid in order to save overall cost during operational forecasts. Future developments of IFS will include a wave model grid that matches the IFS.

The table below summarises the wave model recommended grid (as used by ECMWF) for each atmospheric resolution. This is for information only, the wave initial files provided by ECMWF will already have this taken into account for the requested resolutions.

Supported spectral and horizontal grid resolutions

The table below summarizes the supported configurations of the IFS and the relationship between spectral truncation, atmosphere and wave model grids and the recommended timestep for optimum performance.


Click in the column header to display the table according to that column.


Spectral truncationGrid
(lats pole to eq)
Grid typeResolution at equator
(npts at eq. / spacing)
Wave model
latitude spacing
Recommended
timestep (mins)

Application

Tco1279O1280cubic oct / _45136 / 8km / 0.070o0.125o7.5Operational forecast resolution (43r3)
Tl1279N640linear reduced / l_22560 / 16km / 0.141o0.25o10Operational forecast resolution (40r1)

Tl1023

N512linear reduced / l_22048 / 20km / 0.176o0.25o10-
Tco799O800cubic oct / _43216 / 12.5km / 0.112o0.125o12-
Tl799N400linear reduced / l_21600 / 25km / 0.225o0.36o12-
Tco639O640cubic oct / _42576 / 16km / 0.140o0.25o12Operational ensemble resolution (43r3)
Tl639N320linear reduced / l_21280 / 31km / 0.281o0.36o15ERA-5 high resolution
Tl511N256linear reduced / l_21024 / 39km / 0.352o0.50o15-
Tco399O400cubic oct / _41616 / 25km / 0.223o0.36o15-
Tl399N200linear reduced / l_2800 / 50km / 0.45o1.0o20Operational ensemble resolution (40r1)
Tco319O320cubic oct / _41296 / 31km / 0.278o0.36o15Seasonal system 5
Tl319N160linear reduced / l_2640 / 63km / 0.563o1.0o20ERA-5 ensemble
Tco255O256cubic oct / _41040 / 39km / 0.346o
0.50o20-
Tl255N128linear reduced / l_2512 / 78km / 0.703o1.0o45ERA-Interim; Seasonal system 4
Tq213

N160

quadratic reduced / _2640 / 63km / 0.563o1.0o20-
Tco199O200cubic oct / _4816 / 49km / 0.44o1.0o20-
Tco159O160cubic oct / _4656 / 61km / 0.55o1.0o20-
Tl159N80linear reduced / l_2320 / 125km / 1.125o1.5o60ERA-40
Tq106F80quadratic reduced / _2320 / 125km / 1.125o1.5o60-
Tco95O96cubic oct / _4400 / 100km / 0.9o1.0o30-
Tl95N48linear reduced / l_2192 / 209km / 1.875o3.0o60-
Tq63F48quadratic reduced / _2192 / 209km / 1.875o3.0o60-
Tq42F32quadratic regular / _full128 / 313km / 2.813o3.0o30Development/testing only
Tq21F16quadratic regular / _full64 / 626km / 5.625o3.0o30Development/testing only



  • Grid type suffix refers to the file suffix used at the end of filenames for the OpenIFS/IFS climatology files. It is also used as an argument to the 'gaussgr' command, see 4.5 OpenIFS: Grid tools.
  • The 'cubic' grid rather than 'cubic octahedral' is not listed here as it's infrequently used, the suffix for these files is '_3'.
  • T21 and T42 use the Eulerian dynamical core and a regular Gaussian grid.
  • Tco denotes cubic octahedral grid, Tl denotes a linear grid, Tq denotes a quadratic grid.
  • Other resolutions not listed here may be provided with the OpenIFS climatology files.













6 Comments

  1. Regarding the recommended timestep, what is this based on? I'm running TCO159 with 60 minute timestep without any semi-Lagrangian trajectories going underground. Recommended are 20 minutes. Am I in the clear as long as the model is stable, or can I expect degradation of results by coming close to the limit?

    Cheers, Jan


  2. Unknown User (de3j)

    I would ask your boss since he wrote a nice paper about it a while back. Jung et al. doi: 10.1175/JCLI-D-11-00265.1. They mention that TL159 (lin trunc) with 60min time step has lots of biases in tropics, but reducing time step to 15 min (as TL511) improves this a lot. Also, I accidentally ran TL511 with 60 min time step once. So I think OpenIFS is very stable numerically and your choice of time step is boils down to computational cost vs. quality of forecasts.

  3. Unknown User (nagc)

    Jan, Joakim,

    The values in the table above were taken from 'prepIFS' that creates the experiments and are the recommended defaults. Joakim is correct, the model's semi-Lagrangian dynamics can remain stable but will become less accurate as the timestep is increased. You should always validate the model results.

    Glenn

  4. Interesting, some of these values seem to be quite conservative. E.g. recommended maximum for TCO199 is 12 minutes but in Primavera ECMWF used 30 minutes: 10.5194/gmd-11-3681-2018

    Long timesteps are one of the main advantages of OpenIFS, so I think you are selling yourself a bit short with these.

    1. Unknown User (nagc)

      I double checked the value for Tco199 and 12 mins is what our prepIFS system would set it to. However, that looks like a mistake to me as the timestep is 20mins for the next highest resolution. The timestep should go with the physical grid resolution (O200), the equivalent to Tco199 would be Tl399 (N200), which again has a 20min timestep.  I will make the change to the table and leave these comments here for interest.

      Thanks for pointing that out!

  5. Hello, can TL191 be added to this table? It's used in the CAMS GHG o-suite (becoming officially operational in 48r1).