This page describes the JupyterHub service provided by the ECMWF-Data Store Service (DSS) Service, including how to access the service and what resources and software are available.
...
Once logged in, users are given a choice of environment to use for their Jupyter session session from from a dropdown menu at the top of the page. The DSS offers a single environment to users: "ECMWF Data Store Service".
To start your session, click the "Start" button, if enough resources are available you will be assign a jupyter Jupyter session which will be running for the length of time stated in the resource provisions table below.
Just above the "Start" button there is a "Version" dropdown which refers to the version of the image used to create in your session (i.e. the versioning of the various software packages installed).
To ensure that the software is kept up-to-date, the image will be updated several times a year. Only the "Default" image is officially supported.
The "Rollback" version provides the previous version of the image to assist in cases where a software update has resulted in breaking workflows.
The "Rollback" image is only available for a limited time and we encourage users to update their workflows to use the "Default" image as soon as possible.
...
| Note | ||
|---|---|---|
| ||
All JupyterHub sessions running on this service are time limited. When the time is up, the instance will be killed automatically along with any active processing that may be taking place. You can only have one session running. If you left one running, JupyterHub will connect you straight back into it. If the service is busy and there are no resources available, you will be informed as such and will need to try again later. In the the early stages of the service we will closely monitor usage, and modify options to ensure that we provide a fair usage service to all our users. |
| Info | ||
|---|---|---|
| ||
This is the general ECMWF JupyterHub launcher, therefore it is possible that you have access to more than the Data Store option described here. |
Environments available to DSS users
...
The default python environment is created using conda-forge with a python version version versoin 3.12.8 and the following environment.yml file below. This environment includes a number of ecmwf python packages, including the latest stable release of earthkit. This is the python enviornment environment used when launching the earthkit Notebooks and Consoles from the quick start menu.
| Expand | |||||||
|---|---|---|---|---|---|---|---|
| |||||||
|
CDO environment
To ensure the requirements are correctly installed, the The CDO software is available in a separate python environment. This can be used when selecting a Notebook or Console from the launcher tab, or if using a bash terminal the CDO environment can be activated with the following:
...
| Note | ||
|---|---|---|
| ||
As specified in aritcle article 5.5 of the the Terms of Use for the ECMWF Data Store Service JupyterHub, it is the user's responsibility to ensure they have all the necessary rights to use any of services, applications (including software), data and products used on DSS via the DSS JupyterHub. The software and configuration provided in the initial environment uses open-source channels only (i.e. conda-forge) and we encourage users to use, and contribute to, open source software distributions. |
...
Each user will have an allocated quota on the temporary scratch disk (see table above for size). If you exceed the maximum quota, a clean up script will irreversibly remove your oldest files (by modified time). Any attempt to cirumvent circumvent this behaviour is considered malicious and will lead to your access to JupyterHub being revoked.
...