...

Description of the Service

For a full the complete technical description of the DSS JupyterHub Service please refer to the JupyterHub for the ECMWF Data Store Service (DSS) description  description page. For the purposes avoidance of doubt the complete technical description of the DSS JupyterHub Service forms an integral part of these Terms of Use. While the following elements are specifically noted herein, the below shall be explicitly noted as applicable to all aspects detailed in the complete technical description of the DSS JupyterHub Service are applicable and enforceable as part of the DSS JupyterHub Service:.

Available Environments

DSS users are able to spawn sessions with one of the environments summarised in the Environments environments available to DSS users section n the service description page section in the complete technical description of the DSS JupyterHub Service.

To ensure fair usage of CDS and CDS DSS JupyterHub Service and/or the respective data store, ECMWF reserves the right to prioritise smaller (and shorter) sessions before others.

...

The default Python environment is created using conda-forge

with the following environment.yml file described in the Pre-installed software section of the service description page complete technical description of the DSS JupyterHub Service.

DSS users can install additional packages from the (open-source) conda- conda-forge channel (`conda install PACKAGE-NAME`), or from PyPi (`pip install PACKAGE-NAME`). These packages will be installed in the DSS user’s local private storage and will be available next time the DSS user creates a session. For such packages and other software, additionally installed by the DSS user Article 5.4 below shall apply.

User Storage

DSS JupyterHub Service is provided with two forms of storage: Private and Scratch, as described below.

...

Private Storage

...

Private Storage

If a Private Storage is not accessed (i.e., by spawning a session) for a period of thirty-one (31) consecutive days, this Private Storage together with its contents may be deleted in its entirety.

DSS JupyterHub Service provides a git plugin between the DDS user’s Private Storage and git repositories, which the DDS user may use to back up any files stored in their Private Storage.  For avoidance of doubt, back up of any data on either storage forms is not provided as part of the DSS JupyterHub Service.

Scratch Storage

Each DSS user will have a Scratch Storage, which represents 100Gb maximum quota per each DSS user on a temporary scratch disk. If the individual quota be exceeded, automated scripts will delete the oldest files (in terms of access file modification time) until the quota is no longer exceeded.

...

The purpose of the Scratch Storage is to store files for a current session or several sessions and such files shall not be considered permanently stored. The Scratch Storage is mounted on a shared disk and is cleaned regularly to ensure that the disk does not exceed capacity. Therefore, the lifetime of the storage of files in the Scratch Storage depends on the overall usage of the DSS JupyterHub Service by all DSS users. The cleanup of files is based on the least recently accessed modified files.

Shared Resources

There is a shared resources directory available for the CDS DDS JupyterHub Service. This shared resources directory is ‘read only’ and contains resources provided by Copernicus Climate Change (C3S) and Copernicus Atmospheric Monitoring (CAMS) services and ECMWF, including but not limited, the notebooks found in the C3S training material.

External Network Access

For security Security reasons secure shell (SSH) protocol connections are disabled with respect to the DSS JupyterHub Service. 

DSS users can use the hypertext transfer protocol secure (HTTPS) address for to access repositories outside DSS and/or the DSS JupyterHub Service, given they are not forbidden by the ECMWF firewall.

...

DSS users are responsible for all activities that occur under their account and shall ensure that their content or service will not violate any applicable law. The DSS users are responsible for properly using the DSS JupyterHub Service to secure , and protect and backup their accounts in a manner that provides appropriate security and protection from unauthorized access, including but not limited to  protecting their access credentials (e.g. private keys or passwords).

DDS users shall keep all their registered information correct and up to date.

DSS users shall ensure that no damage is caused to any products, data or services of any other DSS user or ECMWF.

No use of the DSS JupyterHub Service is allowed for activities which may violate the legal rights of other DSS users or ECMWF, or which may constitute an illegal activity in any form.

DSS users shall not take any action or use any software that could interfere with the functioning of DSS JupyterHub Service or DSS infrastructure as a whole, or interfere with their availability.

If a DSS user becomes aware that their account is compromised or becomes aware of any non-permitted activity, they shall immediately update change their password and contact ECMWF via the support portal.

...

Purpose of use

DSS users are responsible for ensuring that the use of the DSS JupyterHub Service, as well as any data, content and information stored on DSS infrastructure is for purposes aligned with the objectives and legal obligations of ECMWF and the Copernicus services (C3S, CAMS and CEMS) .

Additional Service Specifications

and is in compliance with the applicable laws.

DSS user shall not use DSS JupyterHub Service, as well as any data, content and information stored on DSS infrastructure, for any purpose that is unlawful and not (attempt to) breach or circumvent any administrative or security controlsAdditional Service specifications for the DSS JupyterHub Service can be found on JupyterHub for the ECMWF Data Store Service (DSS).

Ownership, Intellectual Property Rights, Licenses

DSS is operated by ECMWF

...

, where JupyterHub is a third-party software, licensed under Modified BSD License.

Content accessible through

...

the respective data stores while using the DSS JupyterHub Service shall only be used under the terms of the license attributed to it, as updated from time to time by the licensors.

Use of third-party software pre-installed on the DSS infrastructure shall be in line with the applicable third- party software license.

ECMWF does not claim ownership of any software, data, content or information uploaded by the DSS users while using the DSS JupyterHub Service.

DSS users providing software, data and products retain ownership in the items provided. DSS users warrant that they have all the necessary rights to use any of services, applications (including software), data and products used on DSS via the DSS JupyterHub

...

Control of Access and of Use

...

ECMWF reserves the right at any time to modify these Terms of Use and the DSS JupyterHub Service. Any revised Terms of Use will be posted here. Modifications shall take effect immediately following posting of the revised Terms of Use.

...

Other than in cases of intentional or grossly negligent breaches of duty by its staff or representatives or claims resting on an injury to life, body or health, neither ECMWF nor the EU (in relation to the use of EU-owned data) shall be responsible or liable to any user of the DSS and/or the DSS JupyterHub Service for any loss or damage of any sort incurred in connection with the use of the CDS JupyterHub Service.

ECMWF and/or the EU (in relation to the use of EU-owned data) shall not be responsible or liable for the accuracy, usefulness or availability of the CDS JupyterHub Service.

DSS JupyterHub Service is supplied "as is", on a “best effort” basis and without further warranties of any kind, either express or implied, including, but not limited to, the quality, performance, merchantability or fitness for a particular use or purpose. Subject to the aforesaid, neither ECMWF, nor the EU, nor JupyterHub, nor any other third-party copyright holders/contributors shall be liable for any damages, including but not limited to direct, indirect, special, incidental, punitive, exemplary or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise), arising out of the use of or the inability to use the DSS JupyterHub Service and/or the JupyterHub software and/or any other third-party software, even if advised of the possibility of such damage.

ECMWF and the EU (in relation to the use of EU-owned data) disclaim all warranties related to the provision of DSS JupyterHub Service.

DSS user are liable for the consequences of any violation of these Terms of Use.

Privileges and Immunities

...

Protection of Personal Data

The Copernicus ECMWF Data Protection and Privacy Statement applies to all personal data provided by the DSS user in order to registeruse the DSS JupyterHub Service.

Severability

If any provision of these Terms of Use is for any reason held to be invalid, illegal or otherwise unenforceable, such unenforceability does not affect any other provision; the Terms of Use are then to be construed as if they had never contained the provision(s) in question and are to be interpreted, in so far as possible, in such a way as to maintain their original intent.

Version 1.0 (November 2024)