ECMWF is updating updated the default versions of its software packages and libraries used across on Atos HPCF and ECS as part of the regular update cycle.
Info | ||
---|---|---|
| ||
The changes will take took place on on Wednesday 15 May 2024 09:00 UTC |
...
Python 3.11 becomes default
For our Python users, we now offer now a more recent version of Python 3.11 with the usual extra modules found on the previous default 3.10. Note that new versions of other packages with python bindings may only come with support for the new Python 3.11.
...
We have recently opened our new ECMWF Jupyterhub service at https://jupyterhub.ecmwf.int. to all users of our HPCF and ECS. While the old software stack is also supported, you will benefit from an updated Jupyter environment and tools. You can find more information about this new way of working on the HPCF and ECS int the in the ECMWF JupyterHub documentation pages.
...
All the new versions, both ECMWF and 3rd Party, come with a number of bug fixes and improvements, since it has been 2 years since our last change of default software. You may see the Change change logs and news for any individual package or library in the list below if you want to have all the details.
...
Besides ecmwf-toolbox
, the following ECMWF packages with their corresponding module also see their default changed:
ecFlow | 5.11.4 | 5.12.34 | ecFlow Releases | |
---|---|---|---|---|
climetlab | 0.12.8 | 0.21.3 | https://github.com/ecmwf/climetlab | https://github.com/ecmwf/climetlab/releases |
...
Potential issues
ecFlow and python3 incompatibilities
While the ecFlow client and python3 default versions are updated on the HPCF, if you may be running an older version of the ecFlow server. If in your ecFlow tasks you use the ecFlow Python bindings, they may not work with the new default version of Python.
We will update the version of all servers shortly, but in the meantime you may need to either revert to using python3/old in your tasks, or force them to load the new default ecFlow module.