Blog

On 29.11.2022 the SBU Accounting app will be migrated to the new Web infrastructure in Bologna and move from the current https://apps.ecmwf.int/sbu-accounting/ to its new URL  

    https://hpc-usage.ecmwf.int

On 1 Nov 2022 we started to charge for Atos HPC usage. At this occasion we would like to encourage all those using or monitoring Atos HPC resources to login to the SBU Accounting app and check if the reported usage on the Atos is in-line with expectations. Please report any unexpected SBU usage via our Support Portal. For more information please also refer to Atos accounting documentation.

With the DHS Move progressing well and the IFS Cycle 47r3 Release Candidate on the Atos on track for implementation on 18 October we would like to give you a further update on the remaining migration steps and any action you might need to take:  

  • The Atos system, replacing both the Cray HPCF and ecgate, is now supported 24/7, making it particularly suitable for running time-critical applications. From 1 November usage of the operational Atos HPC service (hpc-login) will be charged against SBU allocations. The Atos ECS service (ecs-login), which replaces ecgate, will remain free of charge.
  • After 31 October the Cray HPCF and all attached filesystems will no longer be available. The Cray will be immediately shutdown by the vendor and users must copy all files they need to keep to the Atos before that date.
  • From 1 November a full general user service on ecgate will no longer be available. All users are urged to migrate their activities as early as possible and copy all files still needed to the Atos before that date.
  • Users of the Time-critical option 1 (TC1) framework should now migrate their activities to the Atos, preferably by 18 October, the day of the operational switch-over. Once migrated please stop running your TC1 jobs in Reading. This framework will still be fully supported on ecgate until 31 October.
  • A reduced ecgate service will still be available from 1 November until 13 December, mainly to run TC1 activities. As ECMWF’s focus is on the systems in Bologna, ecgate will only be supported on a least-effort basis.
  • Owners of Time-critical option 2 suites should continue testing their workflow on the Atos HPC. We are contacting those owners to discuss the move of their suites to the Atos HPC.
  • Users of remote ECaccess gateways are advised to check with their Computing Representative regarding the availability of new gateways, necessary to connect to the ECMWF gateways in Bologna, boaccess.ecmwf.int. On these new gateways users will need to re-create their ectrans associations.
  • While the DHS Move is still in progress please watch our detailed Move page for further updates and availability of data.
  • To run graphical applications in Bologna, e.g. ecFlow_ui, Metview, we will offer VDI Virtual Linux Desktops in addition to SSH access via Teleport.
  • The migration of ECPDS (the ECMWF Production Data Store) to Bologna will take place over a 2-week period, starting from 4 October, see our ECPDS migration page.  

To support users with their migration we are offering Atos expert sessions. Please see the event page for more details and to register.  

The information above is based on current expectations. For more details and to get notified about further updates and changes, please “watch” the relevant migration pages and the Atos documentation.  

Thank you for your patience and continued co-operation during this significant migration to our new Data Centre.

As the transition to our new Data Centre in Bologna is approaching its final phase and we are getting closer to the decommissioning of the data centre in Reading we would like to update you on the remaining migration steps and any action you might need to take:  

  • The Atos system, replacing both the Cray HPCF and ecgate, is still awaiting formal acceptance but is providing a full parallel service, reliably supporting the IFS Cycle 47r3 Release Candidate Phase. As we are getting closer to the switch of the operational forecast, the system support will be heightened from the current ‘social hours’ to 24/7. From 1 November usage of the operational Atos HPC service (hpc-login) will be charged against SBU allocations. The Atos ECS service (ecs-login) which replaces ecgate will remain free of charge.
  • All users are invited to migrate their workload to the Atos at their earliest convenience.
  • From 1 November ecgate, the Cray HPCF, and all attached filesystems will no longer be available. The Cray HPCF will be immediately shutdown by the vendor and the decommissioning of the Reading data centre will start. Please copy all Cray and ecgate files you need to keep to the Atos before that date.
  • The DHS Move, expected to cause 5-6 weeks of reduced MARS and ECFS service, will start on 8 September.
  • The switch of ECMWF’s operational forecast (Cycle 47r3) to the Atos is scheduled for 18 October and Release Candidate test data has been available since 19 July.
  • Time-critical option 1 framework has been set up on the Atos (HPC and ECS) and events are being triggered by the ECMWF operational suite run on the Cray HPCF. Jobs can also be triggered by a smaller number of events linked to the availability of the Release Candidate test data being produced on the Atos HPC. At present, these events can be used for testing.  We will inform users when the time-critical workflow can be moved to the Atos HPC and jobs running on ecgate or the Cray can be stopped.
  • Owners of Time-critical option 2 suites should start testing their workflow on the Atos HPC. Operational versions of the suites should continue to run on the Cray until further notice.  We will inform owners when suites can be moved to the Atos HPC.
  • The ECaccess Web Toolkit services, such as job submission, file transfers and ectrans have been set up on Atos HPCF with the new ECaccess gateway boaccess.ecmwf.int. Remote ECaccess Web Toolkits should be able to interact with this new gateway. However, we are still working on the interoperability with other ECaccess gateways. Remote sites may need to install new gateway versions.
  • To prepare for the migration of ECPDS (the ECMWF Production Data Store) to Bologna all real-time dissemination users are invited to participate in tests to receive Release Candidate test data from Bologna, scheduled for September.

The information above is based on current expectations. For more details and to get notified about further updates and changes, please “watch” the relevant migration pages and the Atos documentation.  

To support users with their migration we are offering Atos expert sessions. Please see the event page for more details and to register.  

Thank you for your patience and continued co-operation during this significant migration to our new Data Centre.

As of 23 March, the Climate Data Store (CDS) and Atmosphere Data Store (ADS) are the first two user facing services operationally supported from our new Data Centre in Bologna. Following that successful migration, we would like to update you on the next steps in the transition to the Bologna Data Centre.

The Atos system, the central component of the new infrastructure in Bologna, was initially expected to start its operational service on 1 May 2022. As additional work is required to ensure that our standards and expectations regarding this system are fully met before it can be accepted, the initial start date for the operational Atos service is unfortunately no longer feasible. This will have the following main implications for the further migration:  

  • The operational Atos HPC service will start on 1 September 2022 at the earliest. Until then users will not be charged System Billing Units against their allocation. HPC users are encouraged to continue the testing and migration of their applications to the Atos.
  • The switch of ECMWF’s operational forecast (Cycle 47r3) to the Atos is now expected for late September 2022. Initial technical beta test data produced on the Atos is now available. The Release Candidate Phase will start at least 3 months before the operational switch.   
  • The migration of real-time dissemination users to ECPDS ( the ECMWF Production Data Store) in Bologna is scheduled to happen in September 2022, close to, or on the day of the operational forecast switch-over.
  • The DHS Move, causing 28 days of reduced MARS and ECFS service, is expected to start in mid-June 2022 . Two short dry-run s with reduced MARS and ECFS service for 12-48 hours, are scheduled for 5 April and 26-28 April.
  • Users of the ecgate service will be invited later in April 2022 to start migrating their applications to the on the Atos system.
  • Both the Cray and ecgate system will be switched off on 1 October 2022 at the earliest.

The information above is based on current expectations. For more details and to get notified about further updates and changes, please “watch” the relevant migration pages.  

Thank you for your patience during this significant migration to our new data centre which will enable exciting scientific developments and an overall better service to all ECMWF users.

Following the termination of the test Atos system (TEMS) in Reading in November 2021 and a lot of work by many teams across ECMWF, we are pleased to announce the availability of the first Atos cluster, named 'aa', in Bologna, for Member State users of our High Performance Facility (HPCF).  

If you are currently using our Cray HPCs (cca and ccb), we invite you to start testing your activities on the first Atos system (aa). To help you with this work, we have made available the Atos HPCF Documentation. We strongly encourage you to read carefully through those pages before you start any tests on this new platform. You have more details on this in the HPC2020: News Feed, and we recommend you watch that for updates on the Atos services in Bologna.

Thank you for reporting any issues or sharing your feedback via the ECMWF Support Portal mentioning 'Atos' in the title.

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 6 October 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 47r3, this set of defaults is ready to handle the data produced, including all the new parameters introduced in this cycle.

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.

All the new versions come with a number of bug fixes and improvements. You may see the changelogs 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 oct21 tag in modules. For example:

module swap metview/oct21
module load Magics/oct21
module swap eccodes/oct21

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

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

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

PackageDefault versionNotesDownload page
BeforeAfter
BUFRDC4.6.44.6.5

No changes to the library, just updated BUFR tables

-
CodesUI1.5.11.5.4CodesUI - Change HistoryCodesUI - Releases
ecCodes2.21.02.23.0

Latest news

ecCodes Releases
ecFlow4.17.2

4.17.2

no change

Latest news

ecFlow Releases
ecFlow/55.6.35.7.0

Latest news

ecFlow Releases
Magics

4.6.0

4.9.3Latest NewsMagics Releases
Metview5.11.15.13.2

Change History

Metview Releases
Metview Bundle
ODC1.3.0

1.4.1

--
ODB API0.19.5

0.19.5

no change

Change historyODB API Release
Quaver1.4.6.4

2.0.8.1

See the Quaver 2 migration page.
Quaver/1 users should load it by
module load quaver/1

-
ECMWF toolbox

2021.03.1.0

2021.08.0.0


Only available on Atos Systems-
CDO

1.9.10

1.9.10-01


Same CDO version, with updated ecCodes 2.23.0-

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.

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

  • 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

  • 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

  • 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


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

  • 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

  • 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

  • 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


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.

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