Blog

ECMWF is updating the default versions of its software packages and libraries used across all user platforms at the centre as part of the regular update cycle.

When?

The changes will take place on Wednesday 5 May 2021 09:00 UTC

What platforms are affected?

All user platforms at the centre will see their default additional software stack updated:

  • All clusters in our High Performance Computing Facility, mainly CCA and CCB
  • ECGATE
  • Linux Clusters
  • Linux Desktops
  • TEMS

Do I need to do anything?

We strongly recommend you test that your programs, scripts and suites work with the new versions of any software or library affected before the change happens.

Table of contents

Highlights

Software stack ready for next operational IFS cycle

With the upcoming Implementation of IFS Cycle 47r2, this set of defaults is ready to handle the data produced, including all the new parameters introduced in this cycle and the update to Tropical Cyclone tracks.

Python 3.8 becomes default

For our Python users, we offer now a more recent version of Python 3.8 with the usual extra modules found on the previous default 3.6 which would be out of official maintenance at the end of the year.

For those still using Python 2, note that this major version of Python reached its end of life on 1st January 2020, If you haven't done moved to Python 3.6 yet, please see Migration to Python 3 for some guidance on where to start. We are providing the latest Python 2.7 for compatibility purposes only.

ECMWF software improvements

See the blog posts for the latest two software releases to learn about what is new in some of our own software packages and libraries such as ecCodes, Magics or Metview.

Potentially disruptive changes in ecCodes

It is worth highligting a number of changes in ecCodes that could have an impact in specific user workflows:

  • The GRIB2 representation of parameter 238 (Temperature of snow layer - tsn) has been modified. See the new encoding here: https://apps-test.ecmwf.int/codes/grib/param-db/?id=238
  • The command codes_info -v no longer outputs a trailing space. Some user scripts may need to be modified.
  • grib_get_data output is slightly modified: Words on the first line are now separated by spaces not commas.
  • The tools now check that the output file is not the same as the input to avoid overwriting/corrupting the source.
  • The MARS keys levtype and levelist have been removed from the GRIB2 templates 4.53 and 4.54.

A lot of other bugfixes and improvements

All the new versions, both ECMWF and 3rd Party, come with a number of bug fixes and improvements. You may see the Change logs for any individual package or library in the list below if you want to have all the details.

How to use the new versions for testing BEFORE the update

Users are strongly encouraged to test their software applications and data processing chain with the new versions of the various software packages before the date of the change to the default versions.

The new versions of the software packages can be selected by using the may21 tag in modules. For example:

module swap metview/may21
module load Magics/may21
module swap eccodes/may21
module swap python3/may21

How to revert to the old versions in case of problems AFTER the update

Users that experience problems with the new default software packages after the update will be able to revert to the old default versions. These can be selected with the commands:

module swap metview/old
module load Magics/old
module swap eccodes/old
module swap python3/old

Please let ECMWF know if you need to revert to the old version of any of the packages after the update of the defaults has taken place. 

Change list

ECMWF Software

This table summarises the changes in the version of the different packages:

ecCodes is now the official ECMWF encoder and decoder for GRIB and BUFR formats. It supersedes GRIB-API, for the GRIB format, and EMOSLIB, for the BUFR. If you still use any of those, we encourage you to migrate to ecCodes.

Please see the Release notes for full details of the changes implemented in each package.

Third-party software

Some of the versions in this list may already be the default for a specific package on a certain platform, so no changes will be made in those cases. After the update, all platforms will have the same defaults for all these packages.

Package

Next default

Notes

aec1.0.4

https://gitlab.dkrz.de/k202009/libaec/-/blob/v1.0.4/CHANGELOG.md

boost1.71.0

https://www.boost.org/users/history/version_1_71_0.html

cdo1.9.10

https://code.mpimet.mpg.de/projects/cdo/news

clang11.0.1

https://releases.llvm.org/11.0.1/tools/clang/docs/ReleaseNotes.html

cmake3.19.5https://cmake.org/cmake/help/v3.19/release/3.19.html
cmor3.6.1https://cmor.llnl.gov/news/2020/12/16/cmor3/
ferret7.6.3https://ferret.pmel.noaa.gov/Ferret/documentation/version-763-release-notes
fcm2019.05.0https://github.com/metomi/fcm/blob/master/CHANGES.md
fftw3.3.9http://www.fftw.org/release-notes.html
gdal3.2.1https://github.com/OSGeo/gdal/blob/v3.2.1/gdal/NEWS
geos3.9.1https://github.com/libgeos/geos/blob/3.9.1/NEWS
git2.30.1https://github.com/git/git/tree/master/Documentation/RelNotes
gnuparallel20210222https://savannah.gnu.org/forum/forum.php?forum_id=9943
gsl2.6http://git.savannah.gnu.org/cgit/gsl.git/tree/NEWS
grads2.2.1http://cola.gmu.edu/grads/ChangeLog
grass7.8.5https://grass.osgeo.org/news/2020_12_21_grass_gis_7_8_5_released/
hdf51.10.6https://support.hdfgroup.org/ftp/HDF5/releases/ReleaseFiles/hdf5-1.10.6-RELEASE.txt
nccmp1.8.2.1https://gitlab.com/remikz/nccmp/-/blob/master/README.md
nco4.9.7http://nco.sourceforge.net/ANNOUNCE
ncview2.1.7https://cirrus.ucsd.edu/ncview/
netcdf44.7.4https://www.unidata.ucar.edu/blogs/news/entry/netcdf-4-7-4
ninja1.10.2https://groups.google.com/g/ninja-build/c/oobwq_F0PpA/m/FeJC5LoRBgAJ
octave6.2.0https://www.gnu.org/software/octave/news/release/2021/02/20/octave-6.2.0-released.html
openmpi4.1.0

*not on HPCF

https://raw.githubusercontent.com/open-mpi/ompi/v4.1.x/NEWS

panoply4.12.3https://www.giss.nasa.gov/tools/panoply/
pcraster4.3.0-01https://pcraster.geo.uu.nl
proj7.2.1https://proj.org/news.html#id26
python2.7.17-01

More up-to-date extra python packages

https://docs.python.org/2.7/whatsnew/2.7.html

python33.8.8-01

More up-to-date extra python packages

https://docs.python.org/3.8/whatsnew/3.8.html


R4.0.4

More up-to-date extra R packages

https://cran.r-project.org/doc/manuals/r-release/NEWS.html

udunits2.2.28

https://www.unidata.ucar.edu/software/udunits/CHANGE_LOG

valgrind3.16.1

https://www.valgrind.org/docs/manual/dist.news.html

wgrib23.0.0

https://www.cpc.ncep.noaa.gov/products/wesley/wgrib2/

wreport3.27

https://github.com/ARPA-SIMC/wreport/blob/master/NEWS.md

ECMWF is updating the default versions of its software packages and libraries used across all user platforms at the centre as part of the regular update cycle.

When?

The changes will take place on Wednesday 25 November 2020 10:00 - 10:30 UTC

What platforms are affected?

All user platforms at the centre will see their default additional software stack updated:

  • All clusters in our High Performance Computing Facility, mainly CCA and CCB
  • ECGATE
  • Linux Clusters
  • Linux Desktops

The next defaults are tagged as "nov20" in modules. After the session the previous defaults will be tagged as "old"

Table of contents

Highlights

A number of bug fixes and performance improvements have been introduced on the different versions to become default. Here are some of the most relevant new features in respect to the previous default set of versions:

  • ecCodes, the heart of GRIB and BUFR handling, brings performance improvements, new parameters, contributions from users and several smaller features/bug fixes including support for the Mercator projectionPlease note that ecCodes' Python 2 interface is no longer being developed. Users are strongly advised to migrate to Python 3.
  • Magics, ECMWF's plotting library, adds some smaller fixes and additional improvements including :
    • combined with the latest ecCodes, Magics brings plotting support, including interactive Cursor Data, for GRIBs encoded with various projections such as Mercator and Lambert variants.
                 
    • a major code clean-up has reduced the number of dependencies. The Boost library and Python are not required to install Magics anymore.
    • fix issue with logging that was degrading observation plotting speed when used from Python
    • fix issue in python when passing single element array.
  • Metview, ECMWF's interactive and batch software for manipulation and plotting of data, brings several new features and functions, such as:
    • much improved speed of plotting in-memory arrays of data using the Input Visualiser thanks to allowing vectors (Macro language) or numpy arrays (Python) to be used as data
    • the last two modules that were originally implemented in Fortran (Spectra and Potential Temperature) have been converted to C++, meaning they will be available to more users
    • fixes for macOS
    • new Gallery examples
    • a new regridding module that exposes many new interpolation methods for expert users
    • user interface improvements such as a new preview panel that allows quick inspection of icons
    • the long-awaited ability to filter for parameters in the icon editors makes its way into this release
    • a whole raft of new Python/Macro functions for thermodynamic computations and plotting utilities
    • more - see the release notes!

      Metview's new Regrid module brings new possibilities in gridding and transformation of data

  • CodesUI, the standalone combination of Metview's GRIB and BUFR examiners, added syntax highlighting for textual GRIB dumps and fixed an issue where the BUFR filter could unexpectedly crash.

How to use the new versions for testing BEFORE the update

Users are strongly encouraged to test their software applications and data processing chain with the new versions of the various software packages before the date of the change to the default versions.

The new versions of the software packages can be selected by using the nov20 tag in modules. For example:

module swap metview/nov20
module load Magics/nov20
module load bufrdc/nov20
module swap eccodes/nov20 

How to revert to the old versions in case of problems AFTER the update

Users that experience problems with the new default software packages after the update will be able to revert to the old default versions. These can be selected with the commands:

module swap metview/old
module load Magics/old
module load bufrdc/old
module swap eccodes/old 

Please let ECMWF know if you need to revert to the old version of any of the packages after the update of the defaults has taken place. 

Version changes

This table summarises the changes in the version of the different packages:

Please see the Release notes for full details of the changes implemented in each package.

ecCodes is now the official ECMWF encoder and decoder for GRIB and BUFR formats. It superseded GRIB-API, for the GRIB format, and EMOSLIB, for the BUFR. If you still use any of those, we encourage you to migrate to ecCodes. EMOSLIB is, in fact, no longer updated. The standalone BUFRDC package is also installed to help in the migration.

PackageDefault version
BeforeAfter
BUFRDC4.6.34.6.4

Caveats

ecCodes 2.19 and Snow Depth Parameter (141)

ParameterNumber for Snow Depth (141) is now 254 instead of 11 when encoding in GRIB2 format.

The GRIB edition 2 for 141 encoding was wrong in previous versions of ecCodes: The parameterNumber should be 60, not 11 because 11 is the physical depth not the one converted to water volume.

In older versions, both paramIds 141 and 3066 shared the same GRIB2 representation and the consequence of that was 141 was obfuscated by 3066 (water converted depth is obfuscated but the true physical depth!)

From ecCodes 2.19 onwards, this parameter uses local GRIB2 encoding in ECMWF local table 1:

discipline = 0;
parameterCategory = 1;
parameterNumber = 254;
localTablesVersion = 1 ;




ECMWF is updating the default versions of its software packages and libraries used across all user platforms at the centre as part of the regular update cycle.

When?

The changes will take place on  Wednesday 3 June 2020 10:00 UTC

What platforms are affected?

All user platforms at the centre will see their default additional software stack updated:

  • All clusters in our High Performance Computing Facility, mainly CCA and CCB
  • ECGATE
  • Linux Clusters
  • Linux Desktops

Do I need to do anything?

We strongly recommend you test that your programs, scripts and suites work with the new versions of any software or library affected before the change happens.

Table of contents

Highlights

Software stack ready for next operational IFS cycle

With the upcoming Implementation of IFS Cycle 47r1, this set of defaults is ready to handle the data produced, including all the new parameters introduced in this cycle.

No Python 2 upgrade

As Python 2 reached its end of life on 1st January 2020, no newer versions of the Python 2 installations and their associated subpackages such as numpy and others. Older versions remain available for those who haven't migrated to Python 3. If you haven't done so yet, please see Migration to Python 3 for some guidance on where to start.

Metview improvements

Metview, ECMWF's interactive and batch software for manipulation and plotting of data, brings a number of new features and improvements, such as:

  • easier access to the layer metadata in the interactive plot window
  • a new set of pre-defined areas in the Geographical View icon
  • improvements to the GRIB and BUFR examiners (and hence also in CodesUI)
  • improvements to the existing thermodynamic functions
  • plus a new function to compute relative humidity from temperature and dewpoint, a new way to control the font sizes in the user interface

Codes UI efficiency improvements

CodesUI, the standalone combination of Metview's GRIB and BUFR examiners, provides a highly improved initial BUFR message scan (about 50-100 times faster than before), a filter bar for the GRIB namespace list and extra information about BUFR elements.

A lot of other bugfixes and improvements

All the new versions, both ECMWF and 3rd Party, come with a number of bug fixes and improvements. You may see the Change logs for any individual package or library in the list below if you want to have all the details.

How to use the new versions for testing BEFORE the update

Users are strongly encouraged to test their software applications and data processing chain with the new versions of the various software packages before the date of the change to the default versions.

The new versions of the software packages can be selected by using the jun20 tag in modules. For example:

module swap metview/jun20
module load Magics/jun20
module swap eccodes/jun20
module swap python3/jun20

How to revert to the old versions in case of problems AFTER the update

Users that experience problems with the new default software packages after the update will be able to revert to the old default versions. These can be selected with the commands:

module swap metview/old
module load Magics/old
module swap eccodes/old
module swap python3/old

Please let ECMWF know if you need to revert to the old version of any of the packages after the update of the defaults has taken place. 

Change list

ECMWF Software

This table summarises the changes in the version of the different packages:

ecCodes is now the official ECMWF encoder and decoder for GRIB and BUFR formats. It supersedes GRIB-API, for the GRIB format, and EMOSLIB, for the BUFR. If you still use any of those, we encourage you to migrate to ecCodes.

Please see the Release notes for full details of the changes implemented in each package.

Third-party software

Some of the versions in this list may already be the default for a specific package on a certain platform, so no changes will be made in those cases. After the update, all platforms will have the same defaults for all these packages.

The Product Requirements Editor was successfully launched in operations, for Member and Co-operating State users, on Tuesday 18th February.  Member and Co-operating States can now use the application to make operational changes to their real-time data.

Access the Product Requirements Editor

Note : This is an operational system.  Any changes you make in the application WILL affect your operational delivery.

Provide your feedback

We look forward to your feedback, which will be used to shape future improvements to the application.
Please contact servicedesk@ecmwf.int, including 'PRE feedback' in the subject.

Further updates

  • The application will be released to Maximum charge and NMHS licence holders later today.
  • Webinar dates will be announced shortly. Become a watcher of this blog to receive a notification of the announcement.

Highlights & new features

The Product Requirements Editor offers a variety of new features designed to assist users in the management of real-time data delivery.

Examples features include:

 Autocomplete

Autocomplete

  • What it does: Provides users with a list of parameters that exist in the parameter database
  • How to use: ctrl+space
  • Example videoAutocomplete.mov
  • Future enhancements:
    • search for ALL parameters by parameter ID
    • only display parameters that are valid in dissemination and valid for your current request (this is currently just a dump of all parameters from the parameter database)


 Inheritance

Inheritance

  • What it does: Displays the data that is being inherited from the preceding dissemination request
  • How to use: hover over the (info) icon
  • Example videoInheritance.mov
  • Future enhancements: selectively paste inherited data into the requirements

 Snippets (template requirements)

Snippets

  • What it does: Allows users to insert template requirements into their feed, which they can modify and use to build requests from scratch
  • How to use: hover over the <> icon
  • Example videoSnippets.mov
  • Future enhancements: snippets for ALL datasets will be added prior to the first release


 View differences between old and new requirements

Diff

  • What it does: Displays differences between:
    1. the operational version of a feed and the amended version of that same feed
    2. the operational version and a previous operational version
    3. two previous operational versions
  • How to use: select the 'view changes' action
  • Example videoDiff.mov
  • Future enhancements: add the option to save any changes that are made to the requirements while using the diff window



As previously announced, the Product Requirements Editor will replace the existing requirement-editing interface, used by ECMWF Member and Cooperating Sates for the management of real-time dissemination requirements, on Tuesday 18th February 2020.

For full details and final testing, please refer to the following blog post:  Introducing the Product Requirements Editor

Important reminder

Access to the requirements will be disabled between 09:00 UTC on 17th February and 09:00 UTC on 19th February to allow for this implementation.

You can track the progress of the implementation via our Service Status page: https://www.ecmwf.int/en/service-status

For urgent changes or support during this period, please contact servicedesk@ecmwf.int

ECMWF are pleased to announce the availability of a beta version of a new real-time requirement-editing interface.

The Product Requirements Editor will replace the existing requirement-editing interface, used by ECMWF Member and Cooperating Sates for the management of real-time dissemination requirements, on Tuesday 18th February 2020.

Who is it for?

The Product Requirements Editor is an intuitive platform for the editing of real-time data requirements.

User groupAccess to the legacy platform Access to beta phase of the new platformAccess to the new platform (18th February 2020)

Member & Cooperating State

(tick)(tick) - 17th January - 18th February(tick)

NMHS licence holders 

(error) (access to requirements was only available via ECPDS)
(tick) 

Maximum charge customers

(error) (access to requirements was only available via ECPDS)
(tick)

Highlights & new features

The Product Requirements Editor offers a variety of new features designed to assist users in the management of real-time data delivery.

Examples features include:

 Autocomplete

Autocomplete

  • What it does: Provides users with a list of parameters that exist in the parameter database
  • How to use: ctrl+space
  • Example videoAutocomplete copy.mov
  • Future enhancements:
    • search for ALL parameters by parameter ID
    • only display parameters that are valid in dissemination and valid for your current request (this is currently just a dump of all parameters from the parameter database)


 Inheritance

Inheritance

  • What it does: Displays the data that is being inherited from the preceding dissemination request
  • How to use: hover over the (info) icon
  • Example videoInheritance.mov
  • Future enhancements: selectively paste inherited data into the requirements

 Snippets (template requirements)

Snippets

  • What it does: Allows users to insert template requirements into their feed, which they can modify and use to build requests from scratch
  • How to use: hover over the <> icon
  • Example videoSnippet copy.mov
  • Future enhancements: snippets for ALL datasets will be added prior to the first release


 View differences between old and new requirements

Diff

  • What it does: Displays differences between:
    1. the operational version of a feed and the amended version of that same feed
    2. the operational version and a previous operational version
    3. two previous operational versions
  • How to use: select the 'view changes' action
  • Example videoDiff copy.mov
  • Future enhancements: add the option to save any changes that are made to the requirements while using the diff window



How to test

To ensure that you are ready to use the new application from Tuesday 18th February 2020 please test at your earliest convenience.

 How to test

Access the Product Requirements Editor

Log in to the ECMWF website using your user ID and password : https://apps.ecmwf.int/auth/login

Access the web application via the following link : https://apps.ecmwf.int/products/requirements/

User documentation : An introduction to the new requirements web interface

Note : Any changes you make in the application WILL NOT affect your operational delivery. This is strictly a test system.

Report bugs and provide your feedback

This is a beta version of the web application. 

We look forward to your feedback, which will be used to shape future improvements to the application. Please report any feedback to data.services@ecmwf.int using the format below:

Page (URL)

Screenshot

Comments

<provide a link to the page you would like to report><provide a screenshot of the issue><provide a summary of the issue and/or your suggestions for improvement

Further updates

Become a watcher of this blog if you would like to receive further updates regarding the Product Requirements Editor, including announcements of Webinars.


Still using GRIBEX?

GRIBEX is one of the packages that will not be migrated to Bologna - New Data Centre. Please migrate to ecCodes.

GRIBEX, our old GRIB edition 1 decoder/encoder, has been discontinued for years, as it was replaced by GRIB API and then superseded by ecCodes. However, we are aware that it may still be used by some of our users. As part of the retirement of EMOSLIB process, access to the current location of the GRIBEX tables is to be closed. When this happens, any existing program or tool using EMOSLIB for the GRIB decoding/encoding will stop working. This should raise awareness of the places in your workflow that need your attention before our migration to the new data centre.

When?

The session is scheduled for Wednesday 29 January 2020 at 10:45 UTC

Where?

The platforms affected are:

  • All clusters in our High Performance Computing Facility, mainly CCA and CCB
  • ECGATE
  • Linux Clusters
  • Linux Desktops

Actions to take

If you are currently using an old version of emoslib for the GRIB decoding, you will need to migrate those to ecCodes as soon as possible. As a starting point please check here.

However, to temporarily continue working with the existing executables, libraries and tools as they are, you may load the emos_gribex_tables module before running them. This will make the GRIBEX tables available.

module load emos_gribex_tables

The  emos_gribex_tables is a compatibility module that will not be ported to future platforms. You should migrate to ecCodes as soon as possible

Throughout the years, new software packages and multiple versions of them have been deployed on our different computing platforms. In preparation for our future migration to Bologna - New Data Centre, we will be streamlining the number of software packages and their versions available, so the majority of the user base is on recent software stacks prior to our move.

In a first stage in September, we removed the modules for those versions. Now is time to close the access to the actual deployments and installations for those software packages and libraries. Although they are not going to be deleted at this point, they will become unavailable.

Any jobs or programs using any of those items on the list below will most likely fail after the change.

If you are using any of the versions affected, we strongly recommend moving to the default version for that particular package

If you have any concerns, please get in touch with our servicedesk@ecmwf.int.

When?

The session is scheduled for Wednesday 27 November 2019 at 11:00 UTC

Where?

The platforms affected are:

  • All clusters in our High Performance Computing Facility, mainly CCA and CCB
  • ECGATE
  • Linux Clusters
  • Linux Desktops

Packages to be retired

Package

Version

Magics2.20.2
Magics2.24.2
Magics2.26.2
Magics2.29.6
Magics2.30.0
Magics2.32.0
Magics2.32.2
Magics2.33.0
Magics2.35.0
Magics3.0.1
Magics3.0.2
Magics3.0.3
Magics3.2.1
Magics3.3.1
R3.0.1
R3.1.0
R3.1.3
R3.5.1
batch_utils1.0.1
batch_utils1.1
batch_utils1.2
batch_utils1.3
batch_utils1.5
cairo1.15.4
cdftools2.1
cdo1.6.0
cdo1.6.3
cdo1.7.0
cdo1.9.1
cdo1.9.2
cgal4.1
clang3.3
clang3.4
clang5.0.1
cmake2.8.11.2
cmake3.0.2
cmake3.1.2
cmake3.12.0
cmake3.6.2
cmake3.7.1
cmor2.9.3
cmor3.2.2
cmor3.2.3
cmor3.3.3
codes_ui1.0.1
codes_ui1.1.0
codes_ui1.1.0-develop
codes_ui1.2.0-develop
codes_ui1.2.2
codes_ui1.2.3
comfies0.1
comfies0.3
comfies0.4
comfies0.5
comfies0.6
comfies1.0.2
comfies1.0.3
comfies1.0.4
darshan2.3.1-pre1
doxygen1.8.5
ecaccess4.0.2t
ecbuild1.3.1
ecbuild1.3.2
ecbuild1.5.0
ecbuild1.9.0
ecbuild2.1.0
ecbuild2.2.0
ecbuild2.3.0
ecbuild2.3.1
ecbuild2.5.0
ecbuild2.5.1
ecbuild2.6.1
ecbuild2.6.2
ecbuild2.7.0
ecbuild2.7.1
ecbuild2.7.2
ecbuild2.7.3
ecbuild2.8.1
ecbuild2.9.0
ecbuild2.9.2
ecbuild2.9.3
ecbuild2.9.4
eccodes0.16.0
eccodes2.1.0tmp
eccodes2.12.1
eccodes2.6.1
eccodes2.9.1
ecflow4.0.0
ecflow4.0.1
ecflow4.0.2
ecflow4.0.3
ecflow4.0.3.todel
ecflow4.0.4
ecflow4.0.5
ecflow4.0.6
ecflow4.0.8
ecflow4.0.8rc1
ecflow4.0.9
ecflow4.11.0
ecflow4.11.0-develop
ecflow4.12.0-develop
ecflow4.13.0
ecflow4.14.0
ecflow4.4.0
ecflow4.6.0
ecflow4.6.1
ecflow4.7.0
ecflow4.8.0
ecflowx4.6.0-develop
ecfs2.0.12
ecfs2.0.13rc1
ecfs2.0.13rc2
ecfs2.2.0
ecfs2.2.0-rc1
ecfs2.2.0-rc3
ecfs2.2.1-rc1
ecfs2.2.1-rc2
ecfs2.2.2-rc1
eckit0.12.0
eckit0.13.0
eckit0.23.0
eclib20131118
eclib20131205
ecmp1.1.0
ecpds4.0.0_2013110301
ecpds4.0.2_2014051101
ecpds4.0.2_2014271101
extrae3.4.3
extrae3.6.1
extrae3.6.1-single-mpi-lib
fcm2014.09.0
ferret7.2
ferret7.3-standalone
ferret7.4.2
fftw3.3.7
forge18.0.1
gcc8.2.0
gdal1.9.2
gdal2.0.2
git1.8.4
git2.6.1
grib_api1.12.0
grib_api1.12.1
grib_api1.12.3
grib_api1.12.3.OLD
grib_api1.12.3_dbg
grib_api1.13.0
grib_api1.19.0
grib_api1.21.0
grib_api1.22.0
grib_api1.23.0
grib_api1.23.1
grib_api1.25.0
grib_api1.26.0
hdf51.10.2
idl8.2
idl8.5.1
ifs-git-tools1.10.0
ifs-git-tools1.11.0
ifs-git-toolsdevelop
ifs-supportCY41R2.1.WORKS.8.3.1.login
ifs-supportCY41R2.NOTWORK.8.3.1
ifs-supportCY43R1.2
ifs-supportCY43R1.4
ifs-supportCY43R1.5
ifs-supportCY43R1.6
ifs-supportCY43R1.7
ifs-supportCY43R3.1
ifs-supportCY43R3.10
ifs-supportCY43R3.11
ifs-supportCY43R3.2
ifs-supportCY43R3.3
ifs-supportCY43R3.4
ifs-supportCY43R3.5
ifs-supportCY43R3.6
ifs-supportCY43R3.9
ifs-supportCY44R1.0
ifs-supportCY45
ifs-supportCY45R1.0
ifs-supportCY45R1.1
ifs-supportCY45R1.2
ifs-supportCY45R1.4
ifs-supportCY45R1.5
ifs-supportCY45R1.8
libemos392
libemos400
libemos421
libemos422
libemos430
libemos431
libemos444
libemos445
libemos447
libemos448
libemos449
libemos450
libemos451
libemos453
libemos454
libemos456
libemos457
libemos459
libemos460
met3d1.3.0
met3d2017-11
metpy6.0.1
metpy6.0.3
metpy6.0.4
metview-python0.8.4
metview-python0.8.5dev
metview-python0.8.6
metview-python0.9.1
metview-python1.0.0
metview4.4.5
metview4.6.5
metview4.7.1
metview4.7.2
metview4.8.0
metview4.8.2
metview4.8.4
metview4.8.5
metview4.8.6
metview5.0.0-alpha-8
metview5.0.0-beta-1
metview5.0.1
metview5.0.2
metview5.1.0-develop
metview5.1.1
metview5.2.0
metview5.2.0-develop
metview5.2.1
metview5.2.2
metview5.2.4
metview5.3.0
metview5.3.0-develop
metview5.4.0
metview5.4.0-develop
metview5.5.0
metview5.5.0-develop
metview5.5.1
metview5.6.0-develop2
nag22
nag23
ncl6.1.2
ncl6.2.0
ncl6.3.0
nco4.0.8
nco4.6.1
odb1.0.6
odb_api0.10.0
odb_api0.10.5
odb_api0.10.5.4
odb_api0.11.3
odb_api0.12.0
odb_api0.17.2
odb_api0.17.4
odb_api0.17.5
openmpi1.10.3
openmpi1.10.4
openmpi3.0.1
panoply4.5.1
panoply4.7.0
pgen0.10.0.0
pgen0.10.0.1
pgen0.11.0.0
pgen0.11.0.1
pgen0.12.0.0
pgen0.12.0.1
pgen0.2.0.0
pgen0.6.0.0
pgen0.7.0.0
pgen0.7.0.1
pgen0.8.0.0
pgen0.9.0.0
pgen0.9.1.0
pgen0.9.2.0
pgen1.1.0.0
pgen1.1.1.0
pgen1.1.2.0
pgen1.1.3.0
pgen1.1.5.0
pgen1.1.5.1
pgen1.2.0.0
prepifs1.9.1-165
prepifs1.9.1-168
prepifs1.9.1-635
prepifs1.9.1-702
prepifs1.9.1-791
prepifs1.9.1-816
prepifs1.9.1-823
pyg2p2.0.1
python2.7.3-01
python2.7.6-01
python33.5.1-01
python33.6.1-01
quaver1.2.2.1
quaver1.2.4
rttov11.3
slurm14.03.7
subversion1.9.5
swig3.0.12
valgrind3.13.0

ECMWF is updating the default versions of its software packages and libraries used across all user platforms at the centre as part of the regular update cycle.

When?

The changes will take place on Wednesday 13 November 2019 11:00 - 11:30 UTC

What platforms are affected?

All user platforms at the centre will see their default additional software stack updated:

  • All clusters in our High Performance Computing Facility, mainly CCA and CCB
  • ECGATE
  • Linux Clusters
  • Linux Desktops

The next defaults are tagged as "nov19" in modules. After the session the previous defaults will be tagged as "old"

Table of contents

Highlights

A number of bug fixes and performance improvements have been introduced on the different versions to become default. Here are some of the most relevant new features:

  • ecCodes, the heart of GRIB and BUFR handling, brings its usual support for new GRIB parameters along with numerous fixes for extra stability. There are performance improvements for decoding/encoding GRIB data in a multi-threaded program as well as new options for the grib_ls and grib_dump tools.
  • Metview, ECMWF's interactive and batch software for manipulation and plotting of data, brings several new Macro/Python functions, including ml_to_hl(), which converts GRIB data from model levels to height above ground or sea level. Also in this release is an improved inline Help sidebar in the Code Editor.
  • CodesUI, the standalone combination of Metview's GRIB and BUFR examiners, added new tab called Descriptors to show all the expanded descriptors (metadata only) of the given message.
  • Magics, ECMWF's plotting library, adds some smaller fixes.

How to use the new versions for testing BEFORE the update

Users are strongly encouraged to test their software applications and data processing chain with the new versions of the various software packages before the date of the change to the default versions.

The new versions of the software packages can be selected by using the nov19 tag in modules. For example:

module swap metview/nov19
module load Magics/nov19
module load bufrdc/nov19
module swap eccodes/nov19 

How to revert to the old versions in case of problems AFTER the update

Users that experience problems with the new default software packages after the update will be able to revert to the old default versions. These can be selected with the commands:

module swap metview/old
module load Magics/old
module load bufrdc/old
module swap eccodes/old 

Please let ECMWF know if you need to revert to the old version of any of the packages after the update of the defaults has taken place. 

Version changes

This table summarises the changes in the version of the different packages:

Please see the Release notes for full details of the changes implemented in each package.

ecCodes is now the official ECMWF encoder and decoder for GRIB and BUFR formats. It superseded GRIB-API, for the GRIB format, and EMOSLIB, for the BUFR. If you still use any of those, we encourage you to migrate to ecCodes. EMOSLIB is, in fact, no longer updated. The standalone BUFRDC package is also installed to help in the migration.

PackageDefault version
BeforeAfter
BUFRDC4.6.14.6.3

Python is a very popular tool widely used at ECMWF and elsewhere. If you do not use it, you can ignore this message.

As you may know, the official support for Python 2 ends this year. Since Python 3 is not backwards-compatible, steps must be taken to migrate to this new major version. With the lack of official support, we may not be able to install Python 2 on future platforms. Keeping it up-to-date on the existing is also proving increasingly difficult, since many extra modules have dropped their support for Python 2 already. Note that this is not something affecting ECMWF only. If you run Python workloads elsewhere, you will face the same issues.

At ECMWF we have been preparing in order to ensure a smooth transition. Python 3 has been available on all our systems for some time, and it comes with nearly all the extra modules present in our Python 2 installations. This includes interfaces to all our in-house packages and libraries such as ecCodes, Magics or ecFlow. Metview's Python interface has been always only available in Python 3.

We would like to encourage everyone still using Python 2 to take action and start the migration as soon as possible. There are tools that can help you in this task, by doing most of the code changes for you. Please have a look at the Migration to Python 3 wiki page for some advise on how to do this.

Please do not hesitate to contact servicedesk@ecmwf.int for any questions or concerns.

Throughout the years, new software packages and multiple versions of them have been deployed on our different computing platforms. In preparation for our future migration to Bologna - New Data Centre, we will be streamlining the number of software packages and their versions available, so the majority of the user base is on recent software stacks prior to our move.

To accomplish this, we will extend our annual cleanup cycle, removing in a first stage the modules for unused versions as well as those ones that were never set as default. After the session, you will not be able to load the modules affected.

Some of those modules are still actively used, so you are encouraged to check if any of the packages in the list below is used anywhere in your processing workload. If so, we recommend moving to the current default version for each of those software packages and libraries.

Note that the actual deployments and installations for those software packages are not going to be deleted at this point. This will be done at a later stage. 

If you are using any of the versions affected by this change outside the module system, we strongly recommend moving to the default version for that particular package before the second stage to avoid any future problems

If you have any concerns, please get in touch with our servicedesk@ecmwf.int.

When?

The session is scheduled for Wednesday 18 September 2019 at 10:00 UTC

Where?

The platforms affected are:

  • All clusters in our High Performance Computing Facility, mainly CCA and CCB
  • ECGATE
  • Linux Clusters
  • Linux Desktops

Packages to be retired

These are the packages and versions that will no longer be available through the module system on the different platforms:

PackageVersion
Magics2.20.2
Magics2.24.2
Magics2.26.2
Magics2.29.6
Magics2.30.0
Magics2.32.0
Magics2.32.2
Magics2.33.0
Magics2.35.0
Magics3.0.1
Magics3.0.2
Magics3.0.3
Magics3.2.1
Magics3.3.1
R3.0.1
R3.1.0
R3.1.3
R3.5.1
batch_utils1.0.1
batch_utils1.1
batch_utils1.2
batch_utils1.3
batch_utils1.5
cairo1.15.4
cdftools2.1
cdo1.6.0
cdo1.6.3
cdo1.7.0
cdo1.9.1
cdo1.9.2
cgal4.1
clang3.3
clang3.4
clang5.0.1
cmake2.8.11.2
cmake3.0.2
cmake3.1.2
cmake3.12.0
cmake3.6.2
cmake3.7.1
cmor2.9.3
cmor3.2.2
cmor3.2.3
cmor3.3.3
codes_ui1.0.1
codes_ui1.1.0
codes_ui1.1.0-develop
codes_ui1.2.0-develop
codes_ui1.2.2
codes_ui1.2.3
comfies0.1
comfies0.3
comfies0.4
comfies0.5
comfies0.6
comfies1.0.2
comfies1.0.3
comfies1.0.4
darshan2.3.1-pre1
doxygen1.8.5
ecaccess4.0.2t
ecbuild1.3.1
ecbuild1.3.2
ecbuild1.5.0
ecbuild1.9.0
ecbuild2.1.0
ecbuild2.2.0
ecbuild2.3.0
ecbuild2.3.1
ecbuild2.5.0
ecbuild2.5.1
ecbuild2.6.1
ecbuild2.6.2
ecbuild2.7.0
ecbuild2.7.1
ecbuild2.7.2
ecbuild2.7.3
ecbuild2.8.1
ecbuild2.9.0
ecbuild2.9.2
ecbuild2.9.3
ecbuild2.9.4
eccodes0.16.0
eccodes2.1.0tmp
eccodes2.12.1
eccodes2.6.1
eccodes2.9.1
ecflow4.0.0
ecflow4.0.1
ecflow4.0.2
ecflow4.0.3
ecflow4.0.3.todel
ecflow4.0.4
ecflow4.0.5
ecflow4.0.6
ecflow4.0.8
ecflow4.0.8rc1
ecflow4.0.9
ecflow4.11.0
ecflow4.11.0-develop
ecflow4.12.0-develop
ecflow4.13.0
ecflow4.14.0
ecflow4.4.0
ecflow4.6.0
ecflow4.6.1
ecflow4.7.0
ecflow4.8.0
ecflowx4.6.0-develop
ecfs2.0.12
ecfs2.0.13rc1
ecfs2.0.13rc2
ecfs2.2.0
ecfs2.2.0-rc1
ecfs2.2.0-rc3
ecfs2.2.1-rc1
ecfs2.2.1-rc2
ecfs2.2.2-rc1
eckit0.12.0
eckit0.13.0
eckit0.23.0
eclib20131118
eclib20131205
ecmp1.1.0
ecpds4.0.0_2013110301
ecpds4.0.2_2014051101
ecpds4.0.2_2014271101
extrae3.4.3
extrae3.6.1
extrae3.6.1-single-mpi-lib
fcm2014.09.0
ferret7.2
ferret7.3-standalone
ferret7.4.2
fftw3.3.7
forge18.0.1
gcc8.2.0
gdal1.9.2
gdal2.0.2
git1.8.4
git2.6.1
grib_api1.12.0
grib_api1.12.1
grib_api1.12.3
grib_api1.12.3.OLD
grib_api1.12.3_dbg
grib_api1.13.0
grib_api1.19.0
grib_api1.21.0
grib_api1.22.0
grib_api1.23.0
grib_api1.23.1
grib_api1.25.0
grib_api1.26.0
hdf51.10.2
idl8.2
idl8.5.1
ifs-git-tools1.10.0
ifs-git-tools1.11.0
ifs-git-toolsdevelop
ifs-supportCY41R2.1.WORKS.8.3.1.login
ifs-supportCY41R2.NOTWORK.8.3.1
ifs-supportCY43R1.2
ifs-supportCY43R1.4
ifs-supportCY43R1.5
ifs-supportCY43R1.6
ifs-supportCY43R1.7
ifs-supportCY43R3.1
ifs-supportCY43R3.10
ifs-supportCY43R3.11
ifs-supportCY43R3.2
ifs-supportCY43R3.3
ifs-supportCY43R3.4
ifs-supportCY43R3.5
ifs-supportCY43R3.6
ifs-supportCY43R3.9
ifs-supportCY44R1.0
ifs-supportCY45
ifs-supportCY45R1.0
ifs-supportCY45R1.1
ifs-supportCY45R1.2
ifs-supportCY45R1.4
ifs-supportCY45R1.5
ifs-supportCY45R1.8
libemos392
libemos400
libemos421
libemos422
libemos430
libemos431
libemos444
libemos445
libemos447
libemos448
libemos449
libemos450
libemos451
libemos453
libemos454
libemos456
libemos457
libemos459
libemos460
met3d1.3.0
met3d2017-11
metpy6.0.1
metpy6.0.3
metpy6.0.4
metview-python0.8.4
metview-python0.8.5dev
metview-python0.8.6
metview-python0.9.1
metview-python1.0.0
metview4.4.5
metview4.6.5
metview4.7.1
metview4.7.2
metview4.8.0
metview4.8.2
metview4.8.4
metview4.8.5
metview4.8.6
metview5.0.0-alpha-8
metview5.0.0-beta-1
metview5.0.1
metview5.0.2
metview5.1.0-develop
metview5.1.1
metview5.2.0
metview5.2.0-develop
metview5.2.1
metview5.2.2
metview5.2.4
metview5.3.0
metview5.3.0-develop
metview5.4.0
metview5.4.0-develop
metview5.5.0
metview5.5.0-develop
metview5.5.1
metview5.6.0-develop2
nag22
nag23
ncl6.1.2
ncl6.2.0
ncl6.3.0
nco4.0.8
nco4.6.1
odb1.0.6
odb_api0.10.0
odb_api0.10.5
odb_api0.10.5.4
odb_api0.11.3
odb_api0.12.0
odb_api0.17.2
odb_api0.17.4
odb_api0.17.5
openmpi1.10.3
openmpi1.10.4
openmpi3.0.1
panoply4.5.1
panoply4.7.0
pgen0.10.0.0
pgen0.10.0.1
pgen0.11.0.0
pgen0.11.0.1
pgen0.12.0.0
pgen0.12.0.1
pgen0.2.0.0
pgen0.6.0.0
pgen0.7.0.0
pgen0.7.0.1
pgen0.8.0.0
pgen0.9.0.0
pgen0.9.1.0
pgen0.9.2.0
pgen1.1.0.0
pgen1.1.1.0
pgen1.1.2.0
pgen1.1.3.0
pgen1.1.5.0
pgen1.1.5.1
pgen1.2.0.0
prepifs1.9.1-165
prepifs1.9.1-168
prepifs1.9.1-635
prepifs1.9.1-702
prepifs1.9.1-791
prepifs1.9.1-816
prepifs1.9.1-823
pyg2p2.0.1
python2.7.3-01
python2.7.6-01
python33.5.1-01
python33.6.1-01
quaver1.2.2.1
quaver1.2.4
rttov11.3
slurm14.03.7
subversion1.9.5
swig3.0.12
valgrind3.13.0

Emoslib is one of the packages that will not be migrated to Bologna - New Data Centre. Please start considering using the alternatives suggested.

As part of the retirement of EMOSLIB, access to the current location of the BUFR tables is to be closed. When this happens, any existing program or tool using EMOSLIB for the BUFR decoding/encoding will stop working. This should raise awareness of the places in your workflow that need your attention.

When?

The session is scheduled for Wednesday 11 September 2019 at 10:00 UTC

Where?

The platforms affected are:

  • All clusters in our High Performance Computing Facility, mainly CCA and CCB
  • ECGATE
  • Linux Clusters
  • Linux Desktops

Actions to take

If you are currently using emoslib for the BUFR decoding, you will need to migrate those to ecCodes at some point. However, to continue working with the existing tools or code base as they are, there are two alternatives:

Recommended option

Rebuild your program with the new standalone BUFRDC package. This is the preferred option to make sure your program works well with the package that will be installed in the future platforms. Note that you 

module load bufrdc

The standalone bufrdc library is not installed for older compilers. You may need to switch to more recent compilers in order to use it.

If in a rush or causing operational problems...

You may temporarily keep the existing executables, libraries and tools as they are, but you need load the emos_bufr_tables module before running them. This will make the BUFR tables available for them. 

module load emos_bufr_tables

The  emos_bufr_tables is a compatibility module that will not be ported to future platforms. You should start the migration to ecCodes, or at least make sure you can use the bufrdc standalone package.

ECMWF is updating the default versions of its software packages and libraries used across all user platforms at the centre as part of the regular update cycle.

When?

The changes will take place on  5 June 2019 10:00 - 10:30 UTC

What platforms are affected?

All user platforms at the centre will see their default additional software stack updated:

  • All clusters in our High Performance Computing Facility, mainly CCA and CCB
  • ECGATE
  • Linux Clusters
  • Linux Desktops

Do I need to do anything?

We strongly recommend you test that your programs, scripts and suites work with the new versions of any software or library affected before the change happens.

In particular, if using ecFlow, please make sure you check the triggers in your suites are well defined as described below.

Table of contents

Highlights

Software stack ready for next operational IFS cycle

With the upcoming Implementation of IFS cycle 46R1, this set of defaults is ready to handle the data produced, including all the new parameters introduced in this cycle.

Default GNU compiler updated

The GNU GCC compiler is used by default in our Linux Clusters. After this session, version 7.3 of this popular compiler will be used by default, instead of the old 6.3.

Python 3 Ready

A more complete Python 3 deployment has been made, with all major ECMWF packages supporting it: Magics, Metview, ecFlow and ecCodes (in beta). We encourage all Python users to start migrating their programs to Python 3, as the official support for Python 2 will cease at the end of 2019. Please have a look at the Migration to Python 3 documentation page for more details on how to do this migration.

Metview new features

The new Metview 5.5 features a new set of thermodynamic functions and lots of new functionality for the Geopoints format.  It also uses the new interpolation package MIR by default, replacing the old EMOSLIB interpolation library.

See the Magics and Metview latest news for a more detailed list of changes.

Improved ecFlowUI

This ecFlow release introduces the Timeline View in ecFlowUI. This is available as a tab in the Info Panel and provides a graphical view of node state history taken from the log file, allowing greater overview and analysis of node start and run times. It also supports a Duration view mode, displaying the submission and active times. This mode allows you to filter the nodes of your choice. The Timeline View provides the ideal tool to help you identify and optimise the tasks that are taking too much time.

Update of main third-party software package defaults across all platforms

Once a year we take the opportunity to update not only the software we develop at ECMWF, but also the core 3rd party packages and libraries in our software stack. Amongst the affected packages we can find popular tools and libraries like Python, R,  cdo or netCDF 4. See below for the complete list.

Discontinuation of old PGI compilers

Up to now, we have been providing our software libraries built with a legacy PGI 14 compiler for the FORTRAN parts of the code. This helped with the migration from older platforms to new ones where our default compiler of choice has been the GNU GCC. The new versions becoming default now are no longer available for the PGI environment on those platforms where it is present. If you still use it, please consider moving to the default environment. Note that older versions of our software stack will still be available for a bit longer in case you cannot migrate immediately.

How to use the new versions for testing BEFORE the update

Users are strongly encouraged to test their software applications and data processing chain with the new versions of the various software packages before the date of the change to the default versions.

The new versions of the software packages can be selected by using the jun19 tag in modules. For example:

module swap metview/jun19
module load Magics/jun19
module swap eccodes/jun19 
module swap python/jun19

How to revert to the old versions in case of problems AFTER the update

Users that experience problems with the new default software packages after the update will be able to revert to the old default versions. These can be selected with the commands:

module swap metview/old
module load Magics/old
module swap eccodes/old 
module swap python/old

Please let ECMWF know if you need to revert to the old version of any of the packages after the update of the defaults has taken place. 

Ecflow change: possible impact after upgrading

This release corrects some faulty triggers expression, that may require validation:

ecflow 4.11.0 or less, these are now errors in 4.12.0
...
family f1
   task t1
       trigger f1 == aborted
   task t2
       trigger ./f1 == aborted
corrected triggers in ecflow 4.12.0
...
family f1
   task t1
        trigger ../f1 == aborted
   task t2
        trigger ../f1 == aborted

If your suite contains wrongly defined triggers like the one on the left, they will never be satisfied and therefore the tasks or families depending on them will not run.

It is highly recommended that whenever you migrate to version 4.12 or beyond from an earlier release, you run the checks below. This will highlight problems early, and save you a lot of debug time.

This can be done before we migrate.

  •  If you use python to generate your suite definitions, then simple make sure you run(defs.check())

    module load ecflow/ new
    ...
    # build your python suite definitions
    def = ...
    print defs.check()  #  this will print any problems with triggers and inlimit

  • Alternatively you can use:

    module swap ecflow/ 4.12.0
    ecflow_client --get > tmp.def
    ecflow_client --load tmp.def check_only #  this will print any problems with triggers and inlimit

If you have migrated to the new release, to check all your suites run:

module load ecflow/ 4.12.0
ecflow_client --check=_all_   #  this will print any problems with triggers and inlimits

You have all the details in the ecflow release 4.12.0.

Change list

ECMWF Software

This table summarises the changes in the version of the different packages:

ecCodes is now the official ECMWF encoder and decoder for GRIB and BUFR formats. It supersedes GRIB-API, for the GRIB format, and EMOSLIB, for the BUFR. If you still use any of those, we encourage you to migrate to ecCodes.

PackageDefault versionRelease notesDownload page
BeforeAfter
EMOSLIB4.5.84.6.1History of EMOSLIB changesEMOSLIB Releases

Please see the Release notes for full details of the changes implemented in each package.

GRIB-API is now out of support and not updated any longer. If you are still using it, we strongly encourage you to migrate to ecCodes.


Third-party software

Some of the versions in this list may already be the default for a specific package on a certain platform, so no changes will be made in those cases. After the update, all platforms will have the same defaults for all these packages.


There are many modules of ECMWF and 3rd-party software deployed on all platforms at the centre that, according to our logs, haven't been used for long time. In a first stage in November, we removed the modules for those unused versions.  Now is time to close the access to the actual deployments and installations for those software packages and libraries. Although they are not going to be deleted at this point, they will become unavailable.

Any jobs or programs using any of those items on the list below will most likely fail after the change.

If you are using any of the versions affected, we strongly recommend moving to the default version for that particular package

If you have any concerns, please get in touch with our servicedesk@ecmwf.int.

When?

The session is scheduled for Wednesday 13 February 2019 at 10:00 UTC

What and where?

PlatformModuleVersions affected
ecgateecbuild1.0.10
ecgateecbuild1.5.0
ecgateecbuild1.6.0
ecgateecbuild1.8.0
ecgateecbuild2.7.3
ecgateodb_api0.17.4
ecgatelibemos394
ecgatelibemos400
ecgatelibemos443
ecgatelibemos453
ecgatelibemos454
ecgatelibemos456
ecgategrib_api1.12.0
ecgategrib_api1.12.1
ecgategrib_api1.12.3
ecgategrib_api1.14.0
ecgategrib_api1.23.1
ecgategrib_api1.25.0
ecgategrib_api1.26.0
ecgateMagics2.22.7
ecgateMagics2.23.1
ecgateMagics2.24.2
ecgateMagics2.24.3
ecgateMagics3.0.2
ecgateecfs2.0.13rc2
ecgategmt5.1.1
ecgateodbCY39R1.001
ecgateecflow4.0.1
ecgateecflow4.0.2
ecgateecflow4.0.3
ecgateecflow4.4.0
ecgatefcm2.3.1
ecgatefcm2014.09.0
ecgatefcm2016.10.0
ecgateeckit0.11.0
ecgateeckit0.18.1
ecgateeckit0.6.0
ecgateeckit0.8.0
ecgateschedule1.1
ecgateschedule1.3
ecgateeccodes2.3.0
ecgateeccodes2.9.1
ecgateiris1.10.0
ecgateifs-git-tools1.7.1
ecgateifs-git-tools1.7.2
ecgatecodes_ui1.1.0
ecgatequaver0.5.1
ecgatequaver1.0.0
ecgatequaver1.0.6
ecgateecmp0.1
ecgateecmp0.3
ecgateecmp1.0.1
cca/ccbecbuild2.4.0
cca/ccbecbuild2.7.0
cca/ccbecflow4.7.0
cca/ccbecflow4.8.0
cca/ccbeckit0.15.0
cca/ccbeckit0.18.1
cca/ccbgrib_api1.14.2
cca/ccbgrib_api1.23.0
cca/ccbgrib_api1.26.0
cca/ccblibemos442
cca/ccblibemos443
cca/ccblibemos454
cca/ccblibemos456
cca/ccbodb_api0.10.2
cca/ccbodb_api0.16.1
cca/ccbodb_api0.17.1
cca/ccbodb_api0.17.4
cca/ccbeclib20131118
cca/ccbmetview5.0.0-beta-1
cca/ccbmetview5.1.0
cca/ccbmetview5.1.1
cca/ccbmetview5.2.1
cca/ccbfcm2.2
cca/ccbfcm2.3.1
cca/ccbmetpy5.3.0
cca/ccbmetpy6.emos
cca/ccbeccodes2.9.1
cca/ccbifs-supportCY43R1.0
cca/ccbifs-supportCY43R1.0-UNSTABLE
cca/ccbifs-supportCY43R1.5
cca/ccbifs-supportCY45R1.3
cca/ccbcmor2.9.3
cca/ccbpgenunstable
cca/ccbecmp0.1
cca/ccbecmp0.2
cca/ccbecmp0.3
cca/ccbecmp1.0.1
cctecflow4.0.8
cctecflow4.7.0
cctecflow4.8.0
cctgrib_api1.10.0
cctgrib_api1.12.3
cctgrib_api1.13.0
cctgrib_api1.13.1
cctgrib_api1.14.0
cctgrib_api1.14.2
cctgrib_api1.14.4
cctgrib_api1.25.0
cctgrib_api1.26.0
cctcmake3.3.2
cctboost1.59.0
cctecbuild1.5.0
cctecbuild1.6.0
cctecbuild1.8.0
cctecbuild2.7.3
ccteckit0.11.0
ccteckit0.12.0
ccteckit0.18.1
ccteckit0.6.0
cctecfs2.2.1-rc2
cctlibemos453
cctlibemos454
cctlibemos456
cctlibemos457
ccteccodes2.9.1
cctfcm2.2
cctfcm2.3.1
cckecflow4.7.0
cckecflow4.8.0
cckecbuild2.9.2
cckeckit0.18.1
cckeccodes2.6.0
cckeccodes2.8.1
cckeccodes2.8.2
cckeccodes2.9.1
leap42ecflow4.0.8
leap42ecflow4.6.1
leap42grib_api1.12.1
leap42grib_api1.13.1
leap42grib_api1.14.2
leap42grib_api1.21.0
leap42grib_api1.25.0
leap42libemos443
leap42libemos444
leap42libemos454
leap42metview4.6.0
leap42metview4.6.1
leap42metview4.8.8
leap42cmake3.1.2
leap42javacurrent-5
leap42javacurrent-7
leap42odb_api0.17.2
leap42totalviewtv8.12.0-0
leap42ecbuild1.5.0
leap42ecbuild1.6.0
leap42ecbuild1.8.0
leap42eccodes0.16.0
leap42comfies0.1
leap42cppcheck1.68
leap42cppcheck1.79
leap42valgrind3.11.0
leap42git1.8.4.5
leap42met3d2017-10
leap42ifs-git-tools1.7.1
leap42ifs-git-tools1.7.2
leap42ncchecker0.1.1
leap42ecmp1.0.1
lxcgrib_api1.14.0
lxcgrib_api1.18.0
lxcmetpy5.5.8
lxcecflow4.0.8
lxcecflow4.6.0
lxcecflow4.6.1
lxceckit0.11.0
lxceckit0.18.1
lxcecbuild1.6.0
lxcecbuild1.8.0
lxcecbuild2.7.1
lxcecbuild2.7.2
lxcecbuild2.7.3
lxclibemos453
lxclibemos454
lxclibemos456
lxclibemos457
lxcpgen0.7.0.1
lxcpgen0.8.0.0
lxcpgen0.9.1.0
lxcpgen0.9.2.0
lxcodb_api0.10.2
lxcodb_api0.11.3
lxcodb_api0.17.4
lxcMagics2.32.1
lxcMagics3.0.0
lxcmetview4.6.0
lxcmetview4.6.1
lxcmetview4.8.1
lxcmetview4.8.6
lxcmetview5.0.0-alpha-5
lxcmetview5.0.0-beta-1
lxcmetview5.0.1
lxceccodes2.9.1
lxcifs-supportCY43R3.4
lxcifs-supportCY45R1.0
lxcifs-supportCY45R1.8
lxcwebdev2016-11-09-001
lxcwebdev2016-11-30-001
lxcwebdevfeature-earthserver
lxcwebdevfeature-reduce-latency-in-datastore
lxcwebdevrelease-2015-09-30-0001
lxcwebdevrelease-2015-11-06-001
lxcperl5.12.2-01
lxcifs-git-tools1.7.1
lxcifs-git-tools1.7.2
lxccomfies0.1
lxcecmp0.1
lxcecmp0.3
lxcecmp1.0.1
lxgecbuild2.7.3
lxgecflow4.0.8
lxgecflow4.7.0
lxgecflow4.8.0
lxglibemos451
lxglibemos453
lxglibemos454
lxglibemos456
lxglibemos457
lxgeccodes2.9.1
lxgforge6.0.6
lxgforge7
lxgpython33.5.1-01
lxgifs-git-tools1.7.1
lxgifs-git-tools1.7.2
lxgperl5.12.2-01
lxgfcm2016.10.0
lxgmetview4.7.2
lxgmetview4.8.0
lxgmetview4.8.3
lxgmetview4.8.6
lxgmetview4.8.7
lxgmetview4.8.8
lxgmetview5.0.0-beta-1
lxgmetview5.0.1
lxgmetview5.0.2
lxgmetview5.1.0
lxgmetview5.2.1
lxggrib_api1.21.0
lxopcmake3.3.2
lxopgit1.8.4.5
lxopgit2.8.1
lxopecflow4.7.0
lxopecflow4.8.0
lxoplibemos456
lxoplibemos457
lxopidl8.5.1
lxopMagics2.29.4
lxopMagics3.2.1
lxopeccodes2.9.1
lxopwebdev2016-10-12-002
lxopifs-supportCY45R1.6
lxopcomfies0.1

We are pleased to announce that the new MARS client with MIR, the new interpolation library replacing EMOSLIB, is now considered ready to become the default at ECMWF. This new version has endured months of extensive tests by many users to ensure a smooth transition. This change of the default MARS client is planned for 29 January 2019.

The old MARS/EMOSLIB would still be accessible with:

mars -e

or, if using the WebAPI, with the keyword:

ppengine=emos

You can find some more information about this in our User Documentation wiki space, including the main differences and known issues:

This page will be updated to reflect any updates relevant to this update and the new MARS/MIR client. You may want to "watch" this page to be notified about those updates.