Experimental service

IMPORTANT: Please be aware that the Service outlined herein is experimental and is provided on an "AS IS" basis with no warranties of any kind. By using this experimental Service, you acknowledge it may contain bugs, experience downtime, or produce unexpected results, and you assume all risks associated with its use.

We reserve the right to modify or discontinue this Service, or modify the Terms of Use of this service, at any time.

The European Centre for Medium-Range Weather Forecasts (ECMWF) operates Data Store Services (DSS) as a family of common architecture data stores, such as the Climate Data Store (CDS), Atmosphere Data Store (ADS), Early Warning Data Store (EWDS), etc. To this effect, the DSS provides access, among others, to the data products produced and brokered as part of, the Copernicus Climate Change Service (C3S), the Copernicus Atmospheric Monitoring Service (CAMS), the Copernicus Emergency Management Service (CEMS) and internally produced ECMWF data products. In addition to the data access, the ECMWF provides a separate JupyterHub service for DSS (DSS JupyterHub Service or Service), by means of which DSS users can have interactive compute sessions (JupyterLab sessions) on DSS compute infrastructure, typically associated with Python 1 Notebooks, but also compatible with standard Python scripts and bash scripts.

Use of the ECMWF DSS JupyterHub Service is regulated by these Terms of Use. For avoidance of doubt, by using DSS JupyterHub Service the DSS user agrees to be bound to all terms and conditions provided in these Terms of Use. If a DSS user is agreeing to these Terms of Use on behalf of an organisation, company or other legal entity, such DSS user represents that they have the legal authority to bind that organisation, company or legal entity to these Terms of Use.  To the same effect, the use of one account to access DSS JupyterHub Service by a number of DSS users constitutes an agreement with these Terms of Use by each one of these different DSS users and the obligations of a DSS user as outlined hereto are applicable to each one of these different DSS users.

These Terms of Use are in addition to any terms and conditions associated with the use of the respective data store and the data, associated products and services from such a data store.

These Terms of Use are complemented by the complete technical description of the DSS JupyterHub Service and the ECMWF Data Protection and Privacy Statement, unless otherwise expressly stipulated herein.

Article 1: Subject of the Terms of Use

Jupyter 2 is a multi-user notebook server, which gives users access to computational environments and resources without the need for any installation and maintenance tasks by the users.

The use of JupyterHub in DSS is to enable the deployment of compute sessions (JupyterLab sessions) to DSS users based on availability. These JupyterLab sessions provide fast access to the data available on the various data stores and allow DSS users to perform post-processing and visualisation of this data. These JupyterLab sessions are not designed for very large computations 3 . For clarification JupyterLab is a flexible and extendible user interface for interactive computing. It has several extensions that are tailored for using Jupyter Notebooks, as well as extensions for other parts of the data science stack.

The use of JupyterHub in DSS as described in these Terms of Use is hereinafter referred to as ‘DSS JupyterHub Service’ or ‘Service’.

Article 2: Registration

DSS JupyterHub Service is available to all DSS users registered with the respective data store, serviced by DSS. No additional registration is needed.

Article 3: Access

DSS JupyterHub Service is available from the ECMWF JupyterHub launcher page, linked from the respective data store web site. Access requires ECMWF log-in credentials, including a two-factor authentication.

Once logged in, DSS users have a choice of environment to use for their JupyterLab session, as described below in Article (4) Description of the Service.

DSS JupyterHub Service may be unavailable from time to time for scheduled maintenance or due to unforeseen circumstances. Furthermore, during busy periods DSS users may have to wait for resources to become available before a session is allocated.

Article 4: Description of the Service

For the complete technical description of the DSS JupyterHub Service please refer to the JupyterHub for ECMWF's Data Store Services (DSS) description page. For 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, all aspects detailed in the complete technical description of the DSS JupyterHub Service are applicable and enforceable as part of the DSS JupyterHub Service.

4.1 Available Environments

DSS users are able to spawn JupyterLab sessions, by means of the DSS JupyterHub Service, with one of the environments summarised in the environments available to DSS users section in the complete technical description of the DSS JupyterHub Service.

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

4.2 Pre-installed Software

The pre-installed Python environments provided are created using conda-forge 4 . The packages included in the Pre-instatlled environments are described in the Pre-installed software section of the complete technical description of the DSS JupyterHub Service.

DSS users can install additional packages from the conda-forge channel (`conda install PACKAGE-NAME`), or from PyPi (`pip install PACKAGE-NAME`). These packages will be installed in the DSS user’s Private Storage and will be available next time the DSS user creates a JupyterLab session. For such packages and other software, additionally installed by the DSS user Articles 5.3-5.5 below shall apply.

4.3 User Storage

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

4.3.1 Private Storage

Each DSS user has Private Storage allocation, which is accessible only to the given DSS user. For the size of this private storage alllocation, please refer to the technical description of the DSS JupyterHub Service.

If a Private Storage is not accessed (i.e., by spawning a JupyterLab 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 DSS user’s Private Storage and git repositories, which the DSS 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.

4.3.2 Scratch Storage

Each DSS user will have a temporary Scratch Storage with a maximum quota per each DSS user on a temporary scratch disk. For the size of the the maximum quota, please refer to the technical description of the DSS JupyterHub Service. If the individual quota is exceeded, automated scripts will delete the oldest files (in terms of file modification time) until the quota is no longer exceeded.

Should the DSS user circumvent the quota, in addition to any other rights available under these Terms of Use, ECMWF reserves the right to delete any files stored in the Scratch Storage of the DSS user.

The purpose of the Scratch Storage is to store files for a current JupyterLab session or several JupyterLab 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 modified files.

4.4 Shared Resources

There is a shared resources directory available for the DSS 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.

4.5 External Network Access

For 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 to access repositories outside DSS and/or the DSS JupyterHub Service, given they are not forbidden by the ECMWF firewall.

4.6 Technical and Security Requirements

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 their accounts in a manner that provides appropriate security and protection from unauthorised access, including but not limited to maintaining the confidentiality of and protecting their access credentials (e.g. private keys or passwords).

DSS 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.

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

4.7 Purpose of use and Acceptable 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 aligned with the purposes, objectives and activities of ECMWF and the Copernicus services (C3S, CAMS and CEMS) 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 controls, including but not limited to:

    1. DSS user shall not store, share, or distribute content that is illegal, harmful, threatening, abusive, harassing, defamatory, vulgar, obscene, or otherwise objectionable;
    2. DSS user shall not engage in any copyright infringement, fraud, and unauthorised access to data;
    3. DSS user shall not distribute malware, viruses, or any other harmful software;
    4. DSS user shall not engage in activities that disrupt the DSS JupyterHub Service, ECMWF operations or harm other users;
    5. DSS user shall not generate, distribute, publish or facilitate unsolicited mass email, promotions, advertisements, or other solicitations (“spam”)
    6. DSS user shall not attempt to gain unauthorised access to any systems, networks, or data, including attempting to bypass security measures or access accounts that do not belong to the given DSS user;
    7. DSS user shall not use the DSS JupyterHub Service in a manner that excessively consumes resources, such as bandwidth, storage, or processing power, which could negatively impact other users.

Further to any other available remedies to ECMWF as per these Terms of Use or the applicable laws, serious violations may be reported to law enforcement authorities and/or could result in criminal and/or civil liability.

Article 5: Ownership, Intellectual Property Rights, Licenses

5.1 Ownership of service and software

DSS is operated by ECMWF, where JupyterHub is a third-party software, licensed under Modified BSD License.

5.2 Content licensing

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.

5.3 Third-party software licensing

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

5.4 Ownership of uploaded content

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

5.5 Ownership and licensing of uploaded and/or authored software, data and products

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

Article 6: Control of Access and of Use

ECMWF reserves the right to monitor and screen on-going aggregate activity deemed to be in compliance with these Terms of Use or otherwise unacceptable or inappropriate, be it for legal, security or other reasons.

Article 7: No Endorsement

No DSS user may publicly represent or imply that ECMWF and/or the respective data provider and/or any other third-party copyright holder/contributor of the data or the software used  are participating in, or has sponsored, approved or endorsed the manner or purpose of the use of DSS JupyterHub Service.

Article 8: Right to Modification

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.

Article 9: Discontinuation and Termination

ECMWF reserves the right, at any time, to modify or discontinue, temporarily or permanently, the DSS JupyterHub Service as well as any means of accessing or utilising it at its sole discretion with or without prior notice to the DSS users.

ECMWF may at its sole discretion, under any circumstances, for any or no reason and with or without prior notice to the DSS users, suspend, terminate or restrict any DSS user’s access to the DSS JupyterHub Service, particularly in cases of violation of these Terms of Use or any of the applicable license terms or if a Private Storage is not accessed (i.e., by spawning a JupyterLab session) for a certain period of time beyond thirty-one (31) consecutive days.

Article 10: Exclusion of Liability and Warranties

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 respective data provider, nor any other third-party copyright holder/contributor of the data or the software used 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 DSS JupyterHub Service.

ECMWF and/or the respective data provider and/or any other third-party copyright holder of the data or the software used shall not be responsible or liable for the accuracy, usefulness or availability of the DSS 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 respective data provider, nor any other third-party copyright holders/contributors of the data or the software used, 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 respective data provider and any other third-party copyright holder/contributor of the data or the software used disclaim all warranties related to the provision of DSS JupyterHub Service.

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

Article 11: Privileges and Immunities

Nothing in or relating to these Terms of Use shall be deemed a waiver of any of the privileges and immunities of ECMWF in conformity with its Protocol on the Privileges and Immunities.

Article 12: Dispute Settlement

Any dispute between ECMWF and interested parties arising out of or relating to the use of the DSS JupyterHub Service shall be resolved amicably by negotiation. If the dispute cannot be so settled, it shall be finally settled under the Rules of Arbitration of the International Chamber of Commerce by three arbitrators appointed in accordance with the said rules; sitting in London, England. The proceedings shall be in the English language. The right of appeal by either party to any national courts on a question of law arising in the course of any arbitral proceedings or out of an award made in any arbitral proceedings is hereby agreed to be excluded.

Article 13: Protection of Personal Data

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

13.1 Categories of Personal Data Processed

The personal data processed when using DSS JupyterHub Service is the personal data contained in either or both of these two types of data:

13.1.1 User Data

User Data, such as: (i) data provided to ECMWF by the DSS user through DSS JupyterHub Service in the DSS user’s account, environments and/or storage, and data that the DSS user derives from that data through their use of DSS JupyterHub Service; or (ii) data submitted, stored, sent or received by or on behalf of the DSS user via the DSS JupyterHub Service under the account of the DSS user and/or DSS user’s environments and/or storage.

The DSS user acknowledges that given the nature of the DSS JupyterHub Service, ECMWF will not able to verify the types of personal data that may be contained in the respective DSS user’s account, environments and/or storage. In order to maintain an accurate record, the DSS user will notify ECMWF if any of the personal data types listed below are not processed in the DSS user’s account, environments and/or storage.

The following types of personal data are generally contained in a DSS user’s account, environments and/or storage and/or can be processed within the DSS JupyterHub Service: basic personal information about the identity of an individual (such as name, address, phone number, email) and personal data contained in credentials for access to data stores and/or other services.

13.1.2 Service data

Data that ECMWF collects or generates during the provision and administration of the DSS JupyterHub Service and related technical support, excluding the User Data. The Service Data consists of: (i) account information (username, names, contact details and job titles); (ii) any data that may be contained or provided by the DSS user with respect to the DSS JupyterHub Service settings and configurations, including resource identifiers and attributes, and service and security settings for data and other resources; (iii) technical and operational details of the usage of the DSS JupyterHub Service by the DSS user (usage, operational status, software errors and crash reports, authentication details, quality and performance metrics, and other technical details necessary to operate and maintain cloud services and related software, incl. device identifiers, identifiers from cookies or tokens, and IP addresses); (iv) direct communications of the DSS user with ECMWF and its partners (user feedback, questions, request for technical support).

13.2 Purpose(s) of the Processing

ECMWF collects and processes the personal data under Article 13.1 above for the provision, administration, security and improvement of the DSS JupyterHub Service and related technical support in line with these Terms of Use, as well as according to DSS user’s use of the features of the DSS JupyterHub Service.

13.3 Obligations of the DSS user

The DSS user shall comply with the respective obligations under the applicable data protection laws and shall not use DSS JupyterHub Service in a manner that would violate such applicable data protection laws. The DSS user is responsible for not including any personal data that is not designed to be processed by ECMWF or the DSS user for the provisioning or use of the DSS JupyterHub Service. The DSS user shall not include personal data in text fields that are not intended for or do not request personal data. The DSS user is responsible to decide if the DSS JupyterHub Service, including its security features, functions and certifications, is appropriate for personal data and other regulated content.

13.4 ECMWF Data Protection and Privacy Statement

ECMWF Data Protection and Privacy Statement applies supplementary to the above-listed provisions of this Article 13.

Article 14: 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.2 (March 2025)


  1. Copyright © 2001-2024 Python Software Foundation; All Rights Reserved, License terms available at https://docs.python.org/3/license.html.
  2. Copyright (c) 2014-, Jupyter Development Team, All rights reserved. Distributed under the terms of the Modified BSD License.
  3. For larger computation tasks, CDS users may consider other JupyterHub resources, for example WEkEO.
  4. Copyright © 2015-2022, conda-forge, All rights reserved. Distributed under the terms of the Modified BSD License.

  • No labels