Note |
---|
This change is combined with the update on the default compiler stacks on our Cray HPCF. See 2017 Compiling environment upgrade on HPCs for more information |
ECMWF will change is changing the default versions of its software packages and libraries used across all user platforms at the centre on the following dates:
...
Package | Default version | Release notes | Download page | |
---|---|---|---|---|
Before10/05/2017 | After 10/05/2017 | |||
ecCodes | 2.1.0 | 2.5.0 | ecCodes Releases | |
EMOSLIB | 4.4.7 | 4.5.2 | History of EMOSLIB changes | EMOSLIB Releases |
Magics | 2.31.0 | 2.34.3 | Latest News | Magics Releases |
Metview | 4.8.3 | 4.9.0 | Metview Releases Metview Bundle | |
GRIB-API | 1.20.0 | 1.24.0 | GRIB-API Releases | |
ODB API | 0.16.1 | 0.17.3 | Change history | ODB API Releases |
ECFLOW | 4.5.0 | 4.7.0 | ecFlow Releases | |
ECFS | 2.2.3 | 2.2.4 | - | - |
...
Warning | ||
---|---|---|
| ||
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. |
Reverting to older versions of ecflow (for server only)
Ecflow 4.7.0 introduces a new file format for the checkpoint files, which is where ecflow keeps the state of the suites so it can recover from a failure or a server stop. This new version of ecflow can work with both formats, being able to load a checkpoint from an older version. However, it will always write out the checkpoints using the new format, so older versions of ecflow will not be able to read it.
if you need to revert your server to an older version once the new server has been used, you need to do the following:
- Stop the running new (>=4.7.0) server.
- With your ecflow server stopped, locate the checkpoint files, in ECF_HOME and move them aside with a different name.
- Start the old (<4.7.0) server, which will appear completely empty.
- Since the new format of the checkpoint uses de ecflow definition language, you can load it as if it was a normal suite, with ecflow_client --load checkpoint_name.