quantumrings 0.11.2000__py3-none-any.whl

quantumrings-0.11.2000.dist-info/METADATA

@@ -0,0 +1,475 @@
+Metadata-Version: 2.4
+Name: quantumrings
+Version: 0.11.2000
+Summary: A Quantum Development Library
+Author-email: "Quantum Rings Inc." <contact@quantumrings.com>
+Project-URL: Homepage, https://www.quantumrings.com
+Project-URL: Documentation, https://portal.quantumrings.com/doc/
+Project-URL: API Reference, https://portal.quantumrings.com/doc/modules.html
+Keywords: quantum,quantum circuit,quantum computing,quantum programming language,quantum register,quantum tools,tools,sdk
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Science/Research
+Classifier: Topic :: Software Development :: Build Tools
+Classifier: Topic :: Scientific/Engineering
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Operating System :: Microsoft :: Windows
+Requires-Python: >=3.11
+Description-Content-Type: text/x-rst
+License-File: LICENSE.rst
+Provides-Extra: cpu
+Requires-Dist: quantumrings-cpu; extra == "cpu"
+Provides-Extra: cuda12x
+Requires-Dist: quantumrings-cuda12x; extra == "cuda12x"
+Provides-Extra: cuda13x
+Requires-Dist: quantumrings-cuda13x; extra == "cuda13x"
+Provides-Extra: nvidia
+Requires-Dist: quantumrings-cuda13x; extra == "nvidia"
+Dynamic: license-file
+
+================================
+Welcome to the Quantum Rings SDK
+================================
+
+This document serves as a guide for installing the Quantum Rings SDK. You can choose to install the SDK in either CPU-only mode or GPU-enabled mode, 
+depending on your system configuration. Before starting the installation process, please review the sections that outline the minimum system requirements and
+supported GPU architectures. 
+
+Additionally, the section titled "Feedback and Getting Support" provides links for submitting feedback or obtaining further assistance.
+
+
+Finding the Latest Version of the SDK
+-------------------------------------
+
+- 0.11.2311 -- For Python 3.11 based installations
+- 0.11.2312 -- For Python 3.12 based installations
+- 0.11.2313 -- For Python 3.13 based installations
+- 0.11.2314 -- For Python 3.14 based installations
+
+
+Minimum System Requirements
+---------------------------
+
+A system with specifications exceeding the minimum requirements is recommended. 
+Lower specifications may limit the number of qubits supported and could result in poor performance.
+
+-  Operating systems recommended:
+
+    -  Ubuntu 22.04.4 LTS
+    -  Ubuntu 24.04.4 LTS
+    -  Windows 11 Pro
+    -  macOS 15 (Only CPU mode and official Python builds are supported. For more information, visit www.python.org.)
+    -  WSL2 based Linux Instances on Windows 11 Pro
+
+-  64-bit Intel i9 x86 CPU (14 cores 20 logical processors recommended) or equivalent
+
+-  Intel processors or Apple Silicon on Mac Systems 
+
+-  NVIDIA GB10 Grace Blackwell Superchip
+
+-  DDR5 or better memory channels recommended
+
+-  32 GB Installed physical memory
+
+-  18 GB Available physical memory
+
+-  64-bit Python version 3.11, 3.12, 3.13, or 3.14 
+
+
+Supported GPU Architectures
+---------------------------
+
+* Amphere, compute capabilities 8.0, 8.6
+* Hopper, compute capability 9.0
+* Blackwell, compute capability 10.0
+* or later
+
+A minimum of 4 GB global memory on the GPU is required to run the SDK. 
+The actual amount of memory needed depends upon the number of qubits used and the gate operations involved.
+CUDA Toolkit 12.x or 13.x is required to install the GPU version of the SDK.
+
+
+=================================================
+Installing the Quantum Rings SDK in CPU-Only Mode
+=================================================
+
+To unlock the full potential of the Quantum Rings Software Development Kit (SDK) in CPU-only mode, 
+follow these essential steps for seamless installation.
+
+
+**STEP - 1**
+
+To obtain your license for the `Quantum Rings SDK <https://www.quantumrings.com/>`_,  register by selecting the **Login** option from the menu.
+
+If you are already registered, you can skip this step.
+
+Next, log in to the `Quantum Rings portal <https://portal.quantumrings.com/developer/>`_. To download your access keys, select the **Manage Keys** option in the left sidebar.
+
+
+**STEP - 2**
+
+Create a virtual environment for your Python version using the following example.
+
+.. code-block:: console
+
+    virtualenv --python=/usr/bin/python3.11 myenv311
+    source myenv311/bin/activate
+
+In some installations, the virtual environment can be created as follows:
+
+.. code-block:: console
+
+    python3.11 -m venv myenv311
+    source myenv311/bin/activate
+
+Note that installing a Python virtual environment may require additional steps.
+
+You can optionally install Jupyter Notebook using the following command:
+
+.. code-block:: console
+
+    pip install notebook
+
+
+**STEP - 3**
+
+Install the Quantum Rings SDK using the following command:
+
+.. code-block:: console
+
+    pip install QuantumRingsLib
+
+
+or by using the following option:
+
+.. code-block:: console
+
+    pip install quantumrings[cpu]
+
+
+**STEP - 6**
+
+Now, try the following Python program from your Jupyter notebook to ensure that everything is working fine.
+
+.. code-block:: python
+   
+    import QuantumRingsLib
+    from QuantumRingsLib import QuantumRegister, AncillaRegister, ClassicalRegister, QuantumCircuit
+    from QuantumRingsLib import QuantumRingsProvider
+    from QuantumRingsLib import job_monitor
+    from QuantumRingsLib import JobStatus
+    from QuantumRingsLib import OptimizeQuantumCircuit
+    from matplotlib import pyplot as plt
+    import numpy as np
+    import math
+
+    provider = QuantumRingsProvider(token =<YOUR_TOKEN_HERE>, name=<YOUR_ACCOUNT_NAME_HERE>)
+    backend = provider.get_backend("scarlet_quantum_rings")
+    numberofqubits = 50
+    shots = 100
+    
+    q = QuantumRegister(numberofqubits , 'q')
+    c = ClassicalRegister(numberofqubits , 'c')
+    qc = QuantumCircuit(q, c)
+
+    qc.h(0)
+    for i in range (qc.num_qubits - 1):
+        qc.cnot(i, i + 1)
+
+    qc.measure_all()
+
+    job = backend.run(qc, shots=shots)
+    job_monitor(job)
+
+    result = job.result()
+    counts = result.get_counts()
+    print(counts)
+
+
+================================================
+Installting the Quantum Rings SDK for NVidia GPU
+================================================
+
+Quantum Rings SDK now supports Nvidia GPUs, either in the native mode or together with the toolkit for Qiskit.
+
+The following steps outline the installation procedure.
+
+
+**STEP - 1**
+
+To obtain your license for the `Quantum Rings SDK <https://www.quantumrings.com/>`_,  register by selecting the **Login** option from the menu.
+
+If you are already registered, you can skip this step.
+
+Next, log in to the `Quantum Rings portal <https://portal.quantumrings.com/developer/>`_. 
+To download your access keys, select the **Manage Keys** option in the left sidebar.
+
+
+
+**STEP - 2**
+
+.. note::
+    
+    If you are using a university supercomputer or a cloud instance with NVIDIA GPUs, your system administrator may have already installed the necessary 
+    NVIDIA drivers for you. In such cases, you can skip this step.
+
+.. warning::
+
+    This step may be challenging, and you may need professional help. Installing device drivers can make your installation unstable. Always proceed with a backup and read all
+    documentation carefully. Ensure you install the correct drivers for your hardware platform. Installing open source drivers may not be a good idea.
+
+Update the `NVIDIA drivers <https://www.nvidia.com/en-us/drivers/>`_ for your system.
+For some Linux distributions, you may need to install the NVIDIA drivers directly from the distribution. Please search for the documentation
+from your Linux operating system provider and follow their recommendation.
+
+If you are installing on WSL-based Linux, you must update the NVIDIA driver in Windows. It will automatically apply to the WSL Linux instance.
+
+Note down the driver version by running the ``nvidia-smi`` command in the terminal and observing the version displayed in the top panel. 
+You will need to know the driver version to install the CUDA Toolkit later.
+
+
+**STEP - 3**
+
+Create a virtual environment for your python version using the following example.
+
+.. code-block:: console
+
+    virtualenv --python=/usr/bin/python3.11 myenv311
+    source myenv31/bin/activate
+
+In some installations, the virtual environment can be created as follows:
+
+.. code-block:: console
+
+    python3.11 -m venv myenv311
+    source myenv311/bin/activate
+
+Note that installing a python virtual environment may require additional steps.
+
+You can optionally choose to install Jupyter notebook, at this time using the following command.
+
+.. code-block:: console
+
+    pip install notebook
+
+
+**STEP - 4**
+
+Choose the appropriate CUDA Toolkit (CTK) for your driver version. Section 2.2 CUDA Driver in `Release notes <https://docs.nvidia.com/cuda/cuda-toolkit-release-notes/index.html>`_ outlines the CUDA Driver 
+version range and the CUDA Toolkit (CTK) you could install.
+Install the CUDA Toolkit (CTK) by following the instructions in the link: `CUDA Toolkit <https://developer.nvidia.com/cuda-toolkit>`_
+Follow the instructions on the screen after installing and setting up the CUDA Toolkit, and set the paths as directed.
+
+
+.. note::
+
+	Linux Users:
+
+	After installing the CUDA Toolkit, you may have to set the environment variable ``LD_LIBRARY_PATH`` to point to the folder where the CUDA Toolkit library was installed.
+	If this is not set, then there may be runtime linkage errors when you import QuantumRingsLib in your Python code.
+
+    Assuming ``/usr/local/cuda-13.0`` is where your CUDA Toolkit is installed, add the following two lines at the bottom of your profile ``~/.profile``.
+
+    .. code-block:: console
+
+        PATH="$PATH:$/usr/local/cuda-13.0/bin"
+        LD_LIBRARY_PATH="$LD_LIBRARY_PATH:$/usr/local/cuda-13.0/lib64"
+
+    Windows Users:
+
+	Ensure that the environment variable ``CUDA_PATH`` is set to the folder where the CUDA Toolkit is installed. Also, ensure that the environment variable ``PATH`` includes the path where
+	CUDA Toolkit components are installed. 
+
+    In addition, you have to tell Python where the CUDA dynamically linkable libraries (DLLs) are located. 
+    
+    Note that:
+    
+    If you are using CUDA Toolkit version 13.x, the runtume is usually installed at: ``"C:\\Program Files\\NVIDIA GPU Computing Toolkit\\CUDA\\v13.0\\bin\\x64"``
+    
+    or
+    
+    If you are using CUDA Toolkit version 12.x, the runtume is usually installed at: ``C:\\Program Files\\NVIDIA GPU Computing Toolkit\\CUDA\\v12.9\\bin``
+    
+    Use the following lines at the top of your code, before importing QuantumRingsLib.
+
+    .. code-block:: console
+
+        import os
+        import platform
+
+        if platform.system() == "Windows":
+            cuda_path = os.getenv("CUDA_PATH", "")
+            if "" == cuda_path:
+                #set a hard-coded path
+                cuda_path = "C:\\Program Files\\NVIDIA GPU Computing Toolkit\\CUDA\\v13.0\\bin\\x64"
+            else:
+                #create from the environment
+                if "13" in cuda_path:
+                    cuda_path += "\\bin\\x64"
+                else:
+                    cuda_path += "\\bin"
+
+            os.add_dll_directory(cuda_path)
+
+        import QuantumRingsLib
+
+
+If environment variables are not set correctly, linker errors will occur, and the SDK will not load. 
+If you are a Windows user, see additional instructions in `Section 6` to set up the DLL search path with Python.
+
+If you are using your university supercomputer or a cloud environment with NVIDIA GPUs, 
+your system administrator may already have installed the necessary runtime components optimized for your hardware platform. 
+You may only need to select the CUDA Toolkit module. Selecting the CUDA Toolkit is typically done using a module loader, as shown below. 
+Browse the modules installed in your system and choose the most recent CUDA Toolkit. 
+Note that your system may use a different way of loading runtime components.
+
+.. code-block:: console
+
+    module load cuda-12.6.1-gcc-12.1.0
+
+
+**STEP - 5**
+
+To install the Quantum Rings SDK, use the command appropriate for your CUDA Toolkit version:
+
+If you are using CUDA Toolkit version 13.x:
+
+.. code-block:: console
+
+    pip install quantumrings-nvidia-gpu
+
+or
+
+.. code-block:: console
+
+    pip install quantumrings[cuda13x]
+
+
+If you are using CUDA Toolkit version 12.x:
+
+.. code-block:: console
+
+    pip install quantumrings[cuda12x]
+
+
+**STEP - 6**
+
+Try running the following Python program in your Jupyter notebook to ensure everything is functioning correctly.
+
+.. code-block:: python
+
+    # For Windows users. Linux users may skip this.
+    # Setup the CUDA Toolkit path with Python
+    import os
+    import platform
+
+    if platform.system() == "Windows":
+        cuda_path = os.getenv("CUDA_PATH", "")
+        if "" == cuda_path:
+            #set a hard-coded path
+            cuda_path = "C:\\Program Files\\NVIDIA GPU Computing Toolkit\\CUDA\\v13.0\\bin\\x64"
+        else:
+            #create from the environment
+            if "13" in cuda_path:
+                cuda_path += "\\bin\\x64"
+            else:
+                cuda_path += "\\bin"
+
+        os.add_dll_directory(cuda_path)
+    #
+    #
+    
+    import QuantumRingsLib
+    from QuantumRingsLib import QuantumRegister, AncillaRegister, ClassicalRegister, QuantumCircuit
+    from QuantumRingsLib import QuantumRingsProvider
+    from QuantumRingsLib import job_monitor
+    from QuantumRingsLib import JobStatus
+    from QuantumRingsLib import OptimizeQuantumCircuit
+    from matplotlib import pyplot as plt
+    import numpy as np
+    import math
+
+    provider = QuantumRingsProvider(token =<YOUR_TOKEN_HERE>, name=<YOUR_ACCOUNT_NAME_HERE>)
+    backend = provider.get_backend("amber_quantum_rings")
+    numberofqubits = 50
+    shots = 100
+    
+    q = QuantumRegister(numberofqubits , 'q')
+    c = ClassicalRegister(numberofqubits , 'c')
+    qc = QuantumCircuit(q, c)
+
+    qc.h(0)
+    for i in range (qc.num_qubits - 1):
+        qc.cnot(i, i + 1)
+
+    qc.measure_all()
+
+    job = backend.run(qc, shots=shots)
+    job_monitor(job)
+
+    result = job.result()
+    counts = result.get_counts()
+    print(counts)
+
+
+
+Using the GPU Mode
+------------------
+
+Certain programs with a large number of qubits (> 22), complex entanglement, and many gate operations can benefit from using a GPU.
+
+To switch to the GPU mode, select the ``amber_quantum_rings`` backend as follows:
+
+
+.. code-block:: console
+
+    backend = provider.get_backend("amber_quantum_rings")
+
+To switch to the CPU mode, select the ``scarlet_quantum_rings`` backend as follows:
+
+.. code-block:: console
+
+    backend = provider.get_backend("scarlet_quantum_rings")
+
+.. note::
+
+    Programs with a few qubits and gate operations usually run faster on the CPU mode with the ``scarlet_quantum_rings`` backend.
+    You can also use the hybrid backend ``serin_quantum_rings`` backend, which uses CPU for most  operations and switches to the GPU mode for complex operations.
+
+
+You can also store the backend name in the configuration file using the key ``backend`` and allow the method ``provider.get_backend`` select it automatically 
+by not providing any arguments. To save the backend name in the configuration file, please follow the instructions in the SDK.
+Once the backend name is saved in the configuration file, you can obtain the backend by providing no arguments to the ``provider.get_backend`` method as follows:
+
+
+.. code-block:: console
+
+    provider = QuantumRingsProvider()
+    backend = provider.get_backend()
+
+
+
+============================
+Feedback and getting support
+============================
+
+We love to hear from you! Please join our `Discord community <https://discord.com/invite/dZJvX5AfkS>`_ to discuss anything quantum computing.
+
+
+`SDK Documentation <https://portal.quantumrings.com/doc/>`_
+
+`FAQ <https://portal.quantumrings.com/developer/support/>`_ (Requires you to login)
+
+`Managing your license keys <https://portal.quantumrings.com/developer/keys/>`_ (Requires you to login)
+
+`Need more qubits? Request here <https://portal.quantumrings.com/developer/keys/>`_ (Requires you to login)
+
+
+
+
+

quantumrings-0.11.2000.dist-info/RECORD

@@ -0,0 +1,5 @@
+quantumrings-0.11.2000.dist-info/licenses/LICENSE.rst,sha256=gjTOlalh8rQGN2uJb06TX4RSNaISgdysUpj5kfl45kE,11097
+quantumrings-0.11.2000.dist-info/METADATA,sha256=usvng47QiVUA0iUaC5HPm0RbrAaCcSK2-pl30tCxUTE,16804
+quantumrings-0.11.2000.dist-info/WHEEL,sha256=_zCd3N1l69ArxyTb8rzEoP9TpbYXkqRFSNOD5OuxnTs,91
+quantumrings-0.11.2000.dist-info/top_level.txt,sha256=AbpHGcgLb-kRsJGnwFEktk7uzpZOCcBY74-YBdrKVGs,1
+quantumrings-0.11.2000.dist-info/RECORD,,

quantumrings-0.11.2000.dist-info/WHEEL

@@ -0,0 +1,5 @@
+Wheel-Version: 1.0
+Generator: setuptools (80.9.0)
+Root-Is-Purelib: true
+Tag: py3-none-any
+

quantumrings-0.11.2000.dist-info/licenses/LICENSE.rst

@@ -0,0 +1,115 @@
+
+====================
+EVALUATION AGREEMENT
+====================
+
+**IMPORTANT:** PLEASE READ THIS EVALUATION AGREEMENT ("**AGREEMENT**") BEFORE CLICKING THE "ACCEPT" BUTTON, AND/OR USING
+THE QUANTUM RINGS, INC. (**"QUANTUM"**) PRODUCT THAT ACCOMPANIES OR IS PROVIDED IN CONNECTION WITH THIS AGREEMENT. BY
+CLICKING THE "ACCEPT" BUTTON, AND/OR USING THE SERVICES IN ANY WAY, YOU AND THE ENTITY THAT YOU REPRESENT ("**EVALUATOR**")
+IS UNCONDITIONALLY CONSENTING TO BE BOUND BY AND IS BECOMING A PARTY TO THIS AGREEMENT WITH QUANTUM AND YOU REPRESENT
+AND WARRANT THAT YOU HAVE THE AUTHORITY TO BIND SUCH ENTITY TO THESE TERMS. IF EVALUATOR DOES NOT UNCONDITIONALLY AGREE
+TO ALL OF THE TERMS OF THIS AGREEMENT, USE OF THE SERVICES IS STRICTLY PROHIBITED. IF EVALUATOR HAS EXECUTED, OR
+SUBSEQUENTLY EXECUTES, AN EVALUATION AGREEMENT OR AN END USER AGREEMENT WITH QUANTUM, THEN THE TERMS AND
+CONDITIONS OF SUCH EXECUTED EVALUATION AGREEMENT OR END USER AGREEMENT, AS APPLICABLE, SHALL GOVERN AND CONTROL
+YOUR USE OF THE PRODUCT.
+
+1. **BETA SERVICES**. Quantum is developing a proprietary, set of development tools for quantum computing (the
+"**Services**"). Evaluator wishes to utilize an evaluation "beta" version of the Services, and Quantum desires to make a beta
+version of the Services available to Evaluator, subject to the following terms and conditions. Subject to the terms and
+conditions of this Agreement, Quantum hereby grants Evaluator, during the Term (as defined below), non-exclusive,
+non-transferable, non-sublicensable right and license to access and use the Services solely for the purpose of evaluating the
+performance and functionality of the Services (the "**Limited Purpose**"). Evaluator agrees to use and evaluate the Services for
+a period of ninty days or such other period of time as mutually agreed by the parties in writing (the "**Term**"). Quantum's
+services outside the scope of this Agreement, if any, shall be provided pursuant to Quantum's then-current applicable services
+policies and procedures ("**Other Terms**"). Nothing in any of Quantum's Other Terms or any other existing agreements that
+Evaluator may have with Quantum apply to or are applicable to this Agreement, or Evaluator's use of the Services offered
+hereunder.
+
+2. **INTELLECTUAL PROPERTY.** The Services (excluding the Evaluator Content hosted thereon), Documentation, and all
+other materials provided by Quantum hereunder, including but not limited to all manuals, reports, records, programs, data and
+other materials, and all intellectual property rights in each of the foregoing, are the exclusive property of Quantum and its
+suppliers. Evaluator agrees that it will not, and will not permit any other party to: (a) permit any party to access the Services
+or any accompanying documentation ("**Documentation**"); (b) modify, adapt, alter or translate the Services or
+Documentation; (c) sublicense, lease, rent, loan, distribute, or otherwise transfer the Services or Documentation to any third
+party; (d) reverse engineer, decompile, disassemble, or otherwise derive or determine or attempt to derive or determine the
+source code (or the underlying ideas, algorithms, structure or organization) of the Services; (e) use or copy the Services or
+Documentation except for the Limited Purpose; or (f) publish or disclose to any third party any performance benchmark tests
+or analyses or other non-public information relating to the Services or the use thereof.
+
+3. **FEEDBACK.** Evaluator understands and agrees that the Services represent a beta test version of unreleased software
+and services that may contain bugs, defects, and errors. In exchange for the licenses granted to Evaluator to use such
+software, Evaluator agrees to use good faith efforts to test, use, and evaluate the Services in live operations, and to promptly
+report to Quantum, either orally or in writing, any errors, problems, defects, or suggestions for changes and improvements to
+the Services (collectively, "**Feedback**"). Evaluator acknowledges and agrees that all Feedback and all intellectual property
+rights therein are the exclusive property of Quantum, and hereby assigns to Quantum, all right, title and interest to any and all
+Feedback. Further, Evaluator acknowledges and agrees that Feedback may be used by Quantum in Quantum's development
+of and be incorporated into a version of the Services Quantum may make available for commercial distribution
+("**Commercial Release**") or any other software or intellectual property created by Quantum. Without limiting the foregoing,
+Quantum may incorporate Feedback into its products and services and Evaluator will gain no rights in such products or
+services by virtue of having disclosed Feedback. Evaluator agrees and acknowledges that the products and services
+incorporating such Feedback will be the sole and exclusive property of Quantum, and Evaluator will gain no right, title or
+interest in or to the Services, Documentation or any Commercial Release by virtue of Evaluator's provision of Feedback to
+Quantum or for any other reason. Quantum has no obligation to create, distribute or otherwise offer a Commercial Release,
+and in the event of such Commercial Release, Quantum has no obligation to offer the Commercial Release to Evaluator or to
+offer Evaluator any discounted pricing schedules or special terms. Evaluator understands and agrees that the Commercial
+Release may contain functions and functionality, and perform in a manner significantly different from the current beta version
+of the Services. Accordingly, Evaluator acknowledges that any research or development performed, or business plans made,
+by Evaluator regarding or in reliance upon the Services are done entirely at Evaluator's own risk.
+
+4. **DISCLAIMERS OF WARRANTIES.** Evaluator acknowledges that the Services contain prerelease code for testing
+purposes only and are not at the level of performance and compatibility of a final, generally available product offering.
+Furthermore, Evaluator acknowledges that the Services may contain bugs, errors, omissions and other problems that could
+cause system or other failures and data loss. Evaluator acknowledges that Quantum may not introduce a product similar to or
+compatible with the Services. Accordingly, Evaluator acknowledges that any research, development or other work that
+
+
+Evaluator performs regarding the Services is done entirely at Evaluator's own risk. To the maximum extent permitted by law,
+the Services, and all other documentation and materials are provided "AS IS" AND WITH ALL FAULTS. QUANTUM
+MAKES NO WARRANTIES WITH RESPECT TO THE SERVICES OR DOCUMENTATION, WHETHER EXPRESS OR
+IMPLIED, INCLUDING WARRANTIES OF TITLE, ACCURACY, INTERFERENCE WITH EVALUATOR'S QUIET
+ENJOYMENT, SYSTEM INTEGRATION, NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A
+PARTICULAR PURPOSE. THE ENTIRE RISK ARISING OUT OF THE USE OR PERFORMANCE OF THE SERVICES
+IS WITH EVALUATOR NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY QUANTUM OR ITS
+AGENTS OR EMPLOYEES SHALL IN ANY WAY INCREASE THE SCOPE OF THIS WARRANTY.
+
+5. **LIMITATION OF LIABILITY.** IN NO EVENT WILL QUANTUM OR ITS LICENSORS (IF ANY) BE LIABLE TO
+EVALUATOR OR ANY THIRD PARTY FOR THE COST OF PROCUREMENT OF SUBSTITUTE SERVICES, LOST
+PROFITS, LOST DATA, OR ANY SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE
+DAMAGES, HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY ARISING IN ANY WAY OUT OF THIS
+AGREEMENT OR EVALUATOR'S USE OF THE SERVICES, EVEN IF QUANTUM HAS BEEN ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGES. THE TOTAL CUMULATIVE LIABILITY, RELATED TO THIS AGREEMENT,
+OF QUANTUM AND ITS LICENSORS (IF ANY) SHALL BE LIMITED TO FIFTY DOLLARS (U.S. $50). The parties
+agree that the limitations of liability set forth in this section shall survive and continue in full force and effect despite any
+failure of consideration or of an exclusive remedy. The parties acknowledge that the prices have been set and the Agreement
+entered into in reliance upon these limitations of liability and that all such limitations form an essential basis of the bargain
+between the parties.
+
+6. **CONFIDENTIALITY.** The structure, sequence, organization and code of the software used to provide the Services
+constitute valuable trade secrets of Quantum and its suppliers. Evaluator will not disclose to any third party: any information
+about the Services, including its existence, design, performance characteristics, feedback, and test results. Evaluator will use
+reasonable efforts to prevent any access to the Services by anyone other than its employees who are obligated to comply with
+the terms hereof.
+
+7. **PRODUCT DIAGNOSTIC REPORTING.** Evaluator acknowledges that the Services will store certain diagnostic information
+about the routine operations of the Services (including, without limitation, its performance, data reduction ratios,
+configuration data, and any software faults) and will periodically transmit this diagnostic information to Quantum. Evaluator
+agrees that Quantum has a perpetual, irrevocable, worldwide, sublicenseable, and royalty-free right to use this diagnostic
+information in any manner and that Evaluator will not interfere with the collection or transmission of such information to
+Quantum. For clarification, there is no actual user data of Evaluator that is transmitted or provided to Quantum.
+
+8. **TERM AND TERMINATION.** This Agreement commences upon the Effective Date and will continue in effect until the
+end of the Term. Either party may terminate this Agreement upon written notice to the other party. Upon termination,
+Evaluator shall immediately cease all use of Services, and delete or destroy all copies of the Documentation in the possession
+or control of Evaluator.
+
+9. **GENERAL PROVISIONS.** This Agreement will be governed by the laws of the State of Colorado. Evaluator submits to
+the exclusive jurisdiction and venue of the federal and state courts located in Denver County, Colorado for any disputes
+arising out of or related to this Agreement. Evaluator may not assign or transfer, by operation of law, change of control or
+otherwise, any of its rights under this Agreement to any third party without Quantum's prior written consent. Any attempted
+assignment or transfer in violation of the foregoing will be void. All waivers must be in writing. Any waiver or failure to
+enforce any provision of this Agreement on one occasion will not be deemed a waiver of any other provision or of such
+provision on any other occasion. If any part of this Agreement is found void and unenforceable, it will not affect the validity
+of the balance of this Agreement, which shall remain valid and enforceable according to its terms. If any provision of this
+Agreement is, for any reason, held to be invalid or unenforceable, the other provisions of this Agreement will remain
+enforceable and the invalid or unenforceable provision will be deemed modified so that it is valid and enforceable to the
+maximum extent permitted by law.

quantumrings-0.11.2000.dist-info/top_level.txt

@@ -0,0 +1 @@
+