Jupyter service implementations and registration Sample Clauses

Jupyter service implementations and registration status Table 1 Jupyter service instances at PaNOSC RIs and their EOSC registration Facility Service Prototype Production URL EOSC registration In progress done ESRF JupyterHub ✔ xxxxx://xxxxxxx-xxxxx.xxxx.xx ✔[1] ILL VISA ✔ xxxxx://xxxx.xxx.xx ✔[2] EuXFEL JupyterHub ✔ xxxxx://xxx-xxxx.xxxx.xx (✔*) ESS Jupyter Hub ✔ xxxxx://x-xxxxxxxx.xxx- xxxxxxxx.xx ✔[3] XXX-XXXX Xxxxxxx Hub ✔ xxxxxxxxx.xxx-laser.eu ✔ CERIC- XXXX Xxxxxxx ✔ xxxxx://xxx.xxxxxxx.xx ✔ EGI Jupyter Hub ✔ xxxxx://xxxxxxxxx.xxx.xx ✔[4] * Registration will be done by XXXX [1] xxxxx://xxxxxxxxxxx.xxxx-xxxxxx.xx/services/jupyter-notebook-can-be-used-to-create-and-share-documents- that-contain-live-code-equations-visualizations-and-text [2] xxxxx://xxxxxxxxxxx.xxxx-xxxxxx.xx/services/visa-virtual-infrastructure-for-scientific-analysis [3] xxxxx://xxxxxxxxxxx.xxxx-xxxxxx.xx/services/pan-learning-org-f68a8ee0-ed50-4eb1-b51a-b28516df7966 [4] xxxxx://xxxxxxxxxxx.xxxx-xxxxxx.xx/services/egi-notebooks Jupyter ecosystem services are present either as stand-alone web-service or as part of a larger service infrastructure:
AutoNDA by SimpleDocs

Related to Jupyter service implementations and registration

  • Selection of Consulting Services 7. Except as ADB may otherwise agree, and except as set forth in the paragraph below, the Borrower shall apply quality- and cost-based selection for selecting and engaging Consulting Services. Schedule 4

  • Implementation Services The Company and the Client have developed a plan for implementing the services to be provided hereunder, including with respect to the transition of responsibility for such services from the Client and its current administrator to the Company, which plan attached hereto as Schedule I (the “Implementation Plan”). The Company shall perform the services required to complete the Implementation Plan, as set forth therein (the “Implementation Services”). The Company and the Client shall comply with any applicable requirements agreed in the Implementation Plan.

  • Joint Network Implementation and Grooming Process Upon request of either Party, the Parties shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may define and detail, inter alia:

  • Proposing Integration Activities in the Planning Submission No integration activity described in section 6.3 may be proposed in a CAPS unless the LHIN has consented, in writing, to its inclusion pursuant to the process set out in section 6.3(b).

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

  • COOPERATION IN IMPLEMENTATION On demand of the other Spouse and without undue delay or expense, each Spouse shall execute, acknowledge, or deliver any instrument, furnish any information, or perform any other acts reasonably necessary to carry out the provisions of this Agreement. If a Spouse fails to execute any document as required by this provision, the court may appoint the court clerk or his or her authorized designee to execute the document on that Xxxxxx’s behalf.

  • Outpatient emergency and urgicenter services within the service area The emergency room copay applies to all outpatient emergency visits that do not result in hospital admission within twenty-four (24) hours. The urgicenter copay is the same as the primary care clinic office visit copay.

  • DEVELOPMENT OR ASSISTANCE IN DEVELOPMENT OF SPECIFICATIONS REQUIREMENTS/ STATEMENTS OF WORK Firms and/or individuals that assisted in the development or drafting of the specifications, requirements, statements of work, or solicitation documents contained herein are excluded from competing for this solicitation. This shall not be applicable to firms and/or individuals providing responses to a publicly posted Request for Information (RFI) associated with a solicitation.

  • Collocation Transfer of Responsibility Without Working Circuits The Collocation is not serving any End User Customers and does not have active service terminations (e.g., Interconnection trunks or UNE Loops) or 2) Collocation Transfer of Responsibility With Working Circuits – The Collocation has active service terminations, such as Interconnection trunks or is serving End User Customers.

  • Red Hat Enterprise Linux Desktop Software Subscriptions Software Subscriptions for Red Hat Enterprise Linux Desktops and Workstations are subject to the parameters set forth in Table 6 below. Each Red Hat Enterprise Linux Desktop and Workstation Software Subscription includes one Red Hat Network system entitlement and one Smart Management Module, each to be used solely with a single Red Hat Enterprise Linux Desktop or Workstation System. Production Support for Red Hat Enterprise Linux Desktop subscriptions is limited to web-based support only for your helpdesk support personnel. Red Hat is not obligated to support your end users directly.

Time is Money Join Law Insider Premium to draft better contracts faster.