Name | qubots JSON |
Version |
0.1.2
JSON |
| download |
home_page | None |
Summary | A collaborative optimization framework. |
upload_time | 2025-02-15 22:12:06 |
maintainer | None |
docs_url | None |
author | None |
requires_python | >=3.9 |
license | Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
|
keywords |
optimization
quantum
classical
cli
community
operation research
decision variables
qubo
|
VCS |
 |
bugtrack_url |
|
requirements |
python-dotenv
Requests
typer
|
Travis-CI |
No Travis.
|
coveralls test coverage |
No coveralls.
|
# Qubots: A Collaborative Optimization Framework
[](https://test.pypi.org/project/qubots/)
[](https://github.com/leonidas1312/qubots/actions)
[](./LICENSE)
[](https://github.com/leonidas1312/qubots/issues)
[](https://github.com/leonidas1312/qubots/network)
Qubots is a Python library that turns optimization problems and optimization algorithms (optimizers) into shareable, modular “qubots”. Whether you’re developing a new optimizer or formulating a complex problem, qubots makes it easy to package, share, and run your work. Through our central hub, Rastion, you can browse, download, and contribute to a growing ecosystem of GitHub repositories dedicated to cutting-edge optimization – spanning classical, quantum, and hybrid methods.
## Rastion
Rastion serves as the central repository hub for all qubots-related projects. On the Rastion page you’ll find detailed documentation, guides on usage, contribution instructions, and real-world use cases that demonstrate how to combine and chain qubots for advanced optimization workflows. Visit the demo page here: https://repo-bloom-portal.lovable.app/
## Table of Contents
- [Features](#features)
- [Installation](#installation)
- [Getting Started](#getting-started)
- [Technical Overview](#technical-overview)
- [Base Classes](#base-classes)
- [Dynamic Qubot Loading: AutoProblem & AutoOptimizer](#dynamic-qubot-loading-autoproblem--autooptimizer)
- [Chaining and Pipelines](#chaining-and-pipelines)
- [CLI Tools](#cli-tools)
- [Use Cases & Examples](#use-cases--examples)
- [Contributing](#contributing)
- [License](#license)
## Features
- **Modular Design**: Formulate your optimization problems and solvers as independent “qubots” that follow a simple interface.
- **Dynamic Loading**: Use the built-in `AutoProblem` and `AutoOptimizer` classes to dynamically load and execute GitHub repositories containing your qubots.
- **Hybrid Optimization**: Seamlessly combine quantum and classical optimizers using our quantum-classical pipeline.
- **CLI Integration**: Manage repositories (create, update, delete, push) via command-line tools for smooth collaboration.
- **Extensive Examples**: Learn from a rich collection of examples covering classical optimization (e.g., Particle Swarm, Tabu Search), quantum approaches (e.g., QAOA, VQE), and continuous problem solvers.
## Installation
Qubots is available on PyPI. To install, simply run:
```bash
pip install qubots
```
For full documentation and guides, please visit the Rastion Hub demo page https://repo-bloom-portal.lovable.app/docs .
## Getting Started
Here’s a brief example showing how to load a problem and a solver from the Rastion hub, then run the optimization:
```python
from qubots.auto_problem import AutoProblem
from qubots.auto_optimizer import AutoOptimizer
# Load the portfolio optimization problem from the Rastion GitHub repository.
problem = AutoProblem.from_repo("Rastion/portfolio-optimization")
# Load the Particle Swarm Optimizer with overridden parameters.
optimizer = AutoOptimizer.from_repo(
"Rastion/particle-swarm",
override_params={"swarm_size": 60, "max_iters": 500}
)
# Run the optimization and print results.
best_solution, best_cost = optimizer.optimize(problem)
print("Portfolio Optimization with PSO")
print("Best Solution:", best_solution)
print("Best Cost:", best_cost)
```
This simple workflow demonstrates how qubots allow you to plug and play various optimization modules with minimal boilerplate.
## Technical Overview
### Base Classes
At the core of qubots are two abstract base classes:
- **BaseProblem**
- Defines the interface for any optimization problem. Every problem qubot must implement:
- `evaluate_solution(solution) -> float`
- Computes the objective value (or cost) for a given candidate solution.
- `random_solution() (optional)`
- Generates a random feasible solution for the problem.
- **BaseOptimizer**
- Provides the interface for optimization algorithms. Every optimizer qubot must implement:
- `optimize(problem, initial_solution=None, **kwargs) -> (solution, cost)`
- Runs the optimization on a given problem, optionally starting from an initial solution.
These interfaces ensure that every qubot—whether problem or solver—can be seamlessly interchanged and composed.
### Dynamic Qubot Loading: AutoProblem & AutoOptimizer
To encourage modularity and collaboration, qubots can be dynamically loaded from GitHub repositories. This is accomplished using:
- **AutoProblem**
- Clones (or pulls) a repository from GitHub.
- Installs required packages (via `requirements.txt`).
- Reads a `problem_config.json` file that specifies an `entry_point` (formatted as `module:ClassName`) and default parameters.
- Dynamically imports and instantiates the problem qubot.
- **AutoOptimizer**
- Follows a similar process using a `solver_config.json` file.
- Installs required packages (via `requirements.txt`).
- Merges default parameters with any user-supplied `override_params`.
- Dynamically loads the optimizer class and returns an instance ready for use.
This design allows developers to share their work as self-contained GitHub repos that anyone can load, test, and incorporate into larger workflows. **Remote execution of python code files, including installing packages via requirements.txt, is not a good practice**. For this reason it is suggested to use Rastion & Qubots in a secure environment using `python -m venv` or `conda create --name my_rastion_env python=3.9`. Developing a sandbox environment & shareable object for qubots should definitely be in the future plans.
### Chaining and Pipelines
Qubots also supports more advanced patterns:
- **Independent Runs**: Use helper functions (in `optimizer_runner.py`) to run several optimizers independently on the same problem, then compare their results.
- **Chained Refinement**: Sequentially refine a solution by passing the output of one optimizer as the initial solution for the next.
- **Quantum-Classical Pipelines**: The `QuantumClassicalPipeline` class (and its helper function `create_quantum_classical_pipeline`) enables you to combine a quantum routine with a classical optimizer. For example, a quantum solver might generate a candidate solution which is then refined by a classical optimizer.
### CLI Tools
The package includes a set of command-line utilities (via the `rastion` script) to:
- **Create, Update, and Delete Repositories**: Easily manage GitHub repositories under the Rastion organization.
- **Push Solver and Problem Code**: Automate the process of packaging your qubot (along with its configuration and dependencies) and pushing it to GitHub.
- **Run Solvers Directly**: Load a solver and a problem from GitHub repositories and run the optimization in one command.
For example, to run a solver from the command line:
```bash
rastion run_solver Rastion/particle-swarm --problem-repo Rastion/max-cut
```
Most CLI tools need a verified github token to work. Currently this github token must be from a member of the Rastion org. We are working on a way to make Rastion automate this process (via a login option to the website).
## Examples
The `examples/` directory contains some examples and test cases, including:
- **Implemented tests**: Tests about the qubots library that have been tested to working locally.
- **Testing to do**: Tests that fail locally.
## Contributing
We welcome contributions to expand the qubots ecosystem! Here’s how you can get involved:
- **Report Issues**: If you encounter bugs or have feature suggestions, please open an issue on the GitHub repository.
- **Submit Pull Requests**: Follow the coding guidelines and ensure that your changes include tests and documentation updates as needed.
- **Share Your Qubots**: Have an innovative optimizer or an interesting problem formulation? Create a GitHub repo under the Rastion organization and share it via the Rastion hub.
- **Improve Documentation**: Enhance guides, tutorials, and examples to help others get started with qubots.
For more detailed contribution guidelines, please refer to our `CONTRIBUTING.md`.
## License
This project is licensed under the [Apache License 2.0](./LICENSE).
By leveraging the flexible design of qubots and the collaborative power of Rastion, you can rapidly prototype, share, and improve optimization solutions—be it for classical problems, quantum algorithms, or hybrid systems.
For more information, contact gleonidas303@gmail.com.
Raw data
{
"_id": null,
"home_page": null,
"name": "qubots",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.9",
"maintainer_email": null,
"keywords": "optimization, quantum, classical, cli, community, operation research, decision variables, QUBO",
"author": null,
"author_email": "\"Ioannis D. Leonidas\" <gleonidas303@gmail.com>",
"download_url": "https://files.pythonhosted.org/packages/7d/94/42e8fabf1ff453d57830655a4ce007b9488fdbc6d20425bc977107588911/qubots-0.1.2.tar.gz",
"platform": null,
"description": "# Qubots: A Collaborative Optimization Framework\n\n[](https://test.pypi.org/project/qubots/)\n[](https://github.com/leonidas1312/qubots/actions)\n[](./LICENSE)\n[](https://github.com/leonidas1312/qubots/issues)\n[](https://github.com/leonidas1312/qubots/network)\n\nQubots is a Python library that turns optimization problems and optimization algorithms (optimizers) into shareable, modular \u201cqubots\u201d. Whether you\u2019re developing a new optimizer or formulating a complex problem, qubots makes it easy to package, share, and run your work. Through our central hub, Rastion, you can browse, download, and contribute to a growing ecosystem of GitHub repositories dedicated to cutting-edge optimization \u2013 spanning classical, quantum, and hybrid methods.\n\n## Rastion\n\nRastion serves as the central repository hub for all qubots-related projects. On the Rastion page you\u2019ll find detailed documentation, guides on usage, contribution instructions, and real-world use cases that demonstrate how to combine and chain qubots for advanced optimization workflows. Visit the demo page here: https://repo-bloom-portal.lovable.app/\n\n## Table of Contents\n\n- [Features](#features)\n- [Installation](#installation)\n- [Getting Started](#getting-started)\n- [Technical Overview](#technical-overview)\n - [Base Classes](#base-classes)\n - [Dynamic Qubot Loading: AutoProblem & AutoOptimizer](#dynamic-qubot-loading-autoproblem--autooptimizer)\n - [Chaining and Pipelines](#chaining-and-pipelines)\n - [CLI Tools](#cli-tools)\n- [Use Cases & Examples](#use-cases--examples)\n- [Contributing](#contributing)\n- [License](#license)\n\n## Features\n\n- **Modular Design**: Formulate your optimization problems and solvers as independent \u201cqubots\u201d that follow a simple interface.\n- **Dynamic Loading**: Use the built-in `AutoProblem` and `AutoOptimizer` classes to dynamically load and execute GitHub repositories containing your qubots.\n- **Hybrid Optimization**: Seamlessly combine quantum and classical optimizers using our quantum-classical pipeline.\n- **CLI Integration**: Manage repositories (create, update, delete, push) via command-line tools for smooth collaboration.\n- **Extensive Examples**: Learn from a rich collection of examples covering classical optimization (e.g., Particle Swarm, Tabu Search), quantum approaches (e.g., QAOA, VQE), and continuous problem solvers.\n\n## Installation\n\nQubots is available on PyPI. To install, simply run:\n\n```bash\npip install qubots\n```\n\nFor full documentation and guides, please visit the Rastion Hub demo page https://repo-bloom-portal.lovable.app/docs .\n\n## Getting Started\n\nHere\u2019s a brief example showing how to load a problem and a solver from the Rastion hub, then run the optimization:\n\n```python\nfrom qubots.auto_problem import AutoProblem\nfrom qubots.auto_optimizer import AutoOptimizer\n\n# Load the portfolio optimization problem from the Rastion GitHub repository.\nproblem = AutoProblem.from_repo(\"Rastion/portfolio-optimization\")\n\n# Load the Particle Swarm Optimizer with overridden parameters.\noptimizer = AutoOptimizer.from_repo(\n \"Rastion/particle-swarm\",\n override_params={\"swarm_size\": 60, \"max_iters\": 500}\n)\n\n# Run the optimization and print results.\nbest_solution, best_cost = optimizer.optimize(problem)\nprint(\"Portfolio Optimization with PSO\")\nprint(\"Best Solution:\", best_solution)\nprint(\"Best Cost:\", best_cost)\n```\n\nThis simple workflow demonstrates how qubots allow you to plug and play various optimization modules with minimal boilerplate.\n\n## Technical Overview\n\n### Base Classes\n\nAt the core of qubots are two abstract base classes:\n\n- **BaseProblem**\n - Defines the interface for any optimization problem. Every problem qubot must implement:\n - `evaluate_solution(solution) -> float`\n - Computes the objective value (or cost) for a given candidate solution.\n - `random_solution() (optional)`\n - Generates a random feasible solution for the problem.\n\n- **BaseOptimizer**\n - Provides the interface for optimization algorithms. Every optimizer qubot must implement:\n - `optimize(problem, initial_solution=None, **kwargs) -> (solution, cost)`\n - Runs the optimization on a given problem, optionally starting from an initial solution.\n\nThese interfaces ensure that every qubot\u2014whether problem or solver\u2014can be seamlessly interchanged and composed.\n\n### Dynamic Qubot Loading: AutoProblem & AutoOptimizer\n\nTo encourage modularity and collaboration, qubots can be dynamically loaded from GitHub repositories. This is accomplished using:\n\n- **AutoProblem**\n - Clones (or pulls) a repository from GitHub.\n - Installs required packages (via `requirements.txt`).\n - Reads a `problem_config.json` file that specifies an `entry_point` (formatted as `module:ClassName`) and default parameters.\n - Dynamically imports and instantiates the problem qubot.\n\n- **AutoOptimizer**\n - Follows a similar process using a `solver_config.json` file.\n - Installs required packages (via `requirements.txt`).\n - Merges default parameters with any user-supplied `override_params`.\n - Dynamically loads the optimizer class and returns an instance ready for use.\n\nThis design allows developers to share their work as self-contained GitHub repos that anyone can load, test, and incorporate into larger workflows. **Remote execution of python code files, including installing packages via requirements.txt, is not a good practice**. For this reason it is suggested to use Rastion & Qubots in a secure environment using `python -m venv` or `conda create --name my_rastion_env python=3.9`. Developing a sandbox environment & shareable object for qubots should definitely be in the future plans.\n\n### Chaining and Pipelines\n\nQubots also supports more advanced patterns:\n\n- **Independent Runs**: Use helper functions (in `optimizer_runner.py`) to run several optimizers independently on the same problem, then compare their results.\n\n- **Chained Refinement**: Sequentially refine a solution by passing the output of one optimizer as the initial solution for the next.\n\n- **Quantum-Classical Pipelines**: The `QuantumClassicalPipeline` class (and its helper function `create_quantum_classical_pipeline`) enables you to combine a quantum routine with a classical optimizer. For example, a quantum solver might generate a candidate solution which is then refined by a classical optimizer.\n\n### CLI Tools\n\nThe package includes a set of command-line utilities (via the `rastion` script) to:\n\n- **Create, Update, and Delete Repositories**: Easily manage GitHub repositories under the Rastion organization.\n- **Push Solver and Problem Code**: Automate the process of packaging your qubot (along with its configuration and dependencies) and pushing it to GitHub.\n- **Run Solvers Directly**: Load a solver and a problem from GitHub repositories and run the optimization in one command.\n\nFor example, to run a solver from the command line:\n\n```bash\nrastion run_solver Rastion/particle-swarm --problem-repo Rastion/max-cut\n```\n\nMost CLI tools need a verified github token to work. Currently this github token must be from a member of the Rastion org. We are working on a way to make Rastion automate this process (via a login option to the website).\n\n## Examples\n\nThe `examples/` directory contains some examples and test cases, including:\n\n- **Implemented tests**: Tests about the qubots library that have been tested to working locally.\n- **Testing to do**: Tests that fail locally.\n\n## Contributing\n\nWe welcome contributions to expand the qubots ecosystem! Here\u2019s how you can get involved:\n\n- **Report Issues**: If you encounter bugs or have feature suggestions, please open an issue on the GitHub repository.\n- **Submit Pull Requests**: Follow the coding guidelines and ensure that your changes include tests and documentation updates as needed.\n- **Share Your Qubots**: Have an innovative optimizer or an interesting problem formulation? Create a GitHub repo under the Rastion organization and share it via the Rastion hub.\n- **Improve Documentation**: Enhance guides, tutorials, and examples to help others get started with qubots.\n\nFor more detailed contribution guidelines, please refer to our `CONTRIBUTING.md`.\n\n## License\n\nThis project is licensed under the [Apache License 2.0](./LICENSE).\n\nBy leveraging the flexible design of qubots and the collaborative power of Rastion, you can rapidly prototype, share, and improve optimization solutions\u2014be it for classical problems, quantum algorithms, or hybrid systems.\n\n\nFor more information, contact gleonidas303@gmail.com.\n\n",
"bugtrack_url": null,
"license": "Apache License\n Version 2.0, January 2004\n http://www.apache.org/licenses/\n \n TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION\n \n 1. Definitions.\n \n \"License\" shall mean the terms and conditions for use, reproduction,\n and distribution as defined by Sections 1 through 9 of this document.\n \n \"Licensor\" shall mean the copyright owner or entity authorized by\n the copyright owner that is granting the License.\n \n \"Legal Entity\" shall mean the union of the acting entity and all\n other entities that control, are controlled by, or are under common\n control with that entity. For the purposes of this definition,\n \"control\" means (i) the power, direct or indirect, to cause the\n direction or management of such entity, whether by contract or\n otherwise, or (ii) ownership of fifty percent (50%) or more of the\n outstanding shares, or (iii) beneficial ownership of such entity.\n \n \"You\" (or \"Your\") shall mean an individual or Legal Entity\n exercising permissions granted by this License.\n \n \"Source\" form shall mean the preferred form for making modifications,\n including but not limited to software source code, documentation\n source, and configuration files.\n \n \"Object\" form shall mean any form resulting from mechanical\n transformation or translation of a Source form, including but\n not limited to compiled object code, generated documentation,\n and conversions to other media types.\n \n \"Work\" shall mean the work of authorship, whether in Source or\n Object form, made available under the License, as indicated by a\n copyright notice that is included in or attached to the work\n (an example is provided in the Appendix below).\n \n \"Derivative Works\" shall mean any work, whether in Source or Object\n form, that is based on (or derived from) the Work and for which the\n editorial revisions, annotations, elaborations, or other modifications\n represent, as a whole, an original work of authorship. For the purposes\n of this License, Derivative Works shall not include works that remain\n separable from, or merely link (or bind by name) to the interfaces of,\n the Work and Derivative Works thereof.\n \n \"Contribution\" shall mean any work of authorship, including\n the original version of the Work and any modifications or additions\n to that Work or Derivative Works thereof, that is intentionally\n submitted to Licensor for inclusion in the Work by the copyright owner\n or by an individual or Legal Entity authorized to submit on behalf of\n the copyright owner. For the purposes of this definition, \"submitted\"\n means any form of electronic, verbal, or written communication sent\n to the Licensor or its representatives, including but not limited to\n communication on electronic mailing lists, source code control systems,\n and issue tracking systems that are managed by, or on behalf of, the\n Licensor for the purpose of discussing and improving the Work, but\n excluding communication that is conspicuously marked or otherwise\n designated in writing by the copyright owner as \"Not a Contribution.\"\n \n \"Contributor\" shall mean Licensor and any individual or Legal Entity\n on behalf of whom a Contribution has been received by Licensor and\n subsequently incorporated within the Work.\n \n 2. Grant of Copyright License. Subject to the terms and conditions of\n this License, each Contributor hereby grants to You a perpetual,\n worldwide, non-exclusive, no-charge, royalty-free, irrevocable\n copyright license to reproduce, prepare Derivative Works of,\n publicly display, publicly perform, sublicense, and distribute the\n Work and such Derivative Works in Source or Object form.\n \n 3. Grant of Patent License. Subject to the terms and conditions of\n this License, each Contributor hereby grants to You a perpetual,\n worldwide, non-exclusive, no-charge, royalty-free, irrevocable\n (except as stated in this section) patent license to make, have made,\n use, offer to sell, sell, import, and otherwise transfer the Work,\n where such license applies only to those patent claims licensable\n by such Contributor that are necessarily infringed by their\n Contribution(s) alone or by combination of their Contribution(s)\n with the Work to which such Contribution(s) was submitted. If You\n institute patent litigation against any entity (including a\n cross-claim or counterclaim in a lawsuit) alleging that the Work\n or a Contribution incorporated within the Work constitutes direct\n or contributory patent infringement, then any patent licenses\n granted to You under this License for that Work shall terminate\n as of the date such litigation is filed.\n \n 4. Redistribution. You may reproduce and distribute copies of the\n Work or Derivative Works thereof in any medium, with or without\n modifications, and in Source or Object form, provided that You\n meet the following conditions:\n \n (a) You must give any other recipients of the Work or\n Derivative Works a copy of this License; and\n \n (b) You must cause any modified files to carry prominent notices\n stating that You changed the files; and\n \n (c) You must retain, in the Source form of any Derivative Works\n that You distribute, all copyright, patent, trademark, and\n attribution notices from the Source form of the Work,\n excluding those notices that do not pertain to any part of\n the Derivative Works; and\n \n (d) If the Work includes a \"NOTICE\" text file as part of its\n distribution, then any Derivative Works that You distribute must\n include a readable copy of the attribution notices contained\n within such NOTICE file, excluding those notices that do not\n pertain to any part of the Derivative Works, in at least one\n of the following places: within a NOTICE text file distributed\n as part of the Derivative Works; within the Source form or\n documentation, if provided along with the Derivative Works; or,\n within a display generated by the Derivative Works, if and\n wherever such third-party notices normally appear. The contents\n of the NOTICE file are for informational purposes only and\n do not modify the License. You may add Your own attribution\n notices within Derivative Works that You distribute, alongside\n or as an addendum to the NOTICE text from the Work, provided\n that such additional attribution notices cannot be construed\n as modifying the License.\n \n You may add Your own copyright statement to Your modifications and\n may provide additional or different license terms and conditions\n for use, reproduction, or distribution of Your modifications, or\n for any such Derivative Works as a whole, provided Your use,\n reproduction, and distribution of the Work otherwise complies with\n the conditions stated in this License.\n \n 5. Submission of Contributions. Unless You explicitly state otherwise,\n any Contribution intentionally submitted for inclusion in the Work\n by You to the Licensor shall be under the terms and conditions of\n this License, without any additional terms or conditions.\n Notwithstanding the above, nothing herein shall supersede or modify\n the terms of any separate license agreement you may have executed\n with Licensor regarding such Contributions.\n \n 6. Trademarks. This License does not grant permission to use the trade\n names, trademarks, service marks, or product names of the Licensor,\n except as required for reasonable and customary use in describing the\n origin of the Work and reproducing the content of the NOTICE file.\n \n 7. Disclaimer of Warranty. Unless required by applicable law or\n agreed to in writing, Licensor provides the Work (and each\n Contributor provides its Contributions) on an \"AS IS\" BASIS,\n WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or\n implied, including, without limitation, any warranties or conditions\n of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A\n PARTICULAR PURPOSE. You are solely responsible for determining the\n appropriateness of using or redistributing the Work and assume any\n risks associated with Your exercise of permissions under this License.\n \n 8. Limitation of Liability. In no event and under no legal theory,\n whether in tort (including negligence), contract, or otherwise,\n unless required by applicable law (such as deliberate and grossly\n negligent acts) or agreed to in writing, shall any Contributor be\n liable to You for damages, including any direct, indirect, special,\n incidental, or consequential damages of any character arising as a\n result of this License or out of the use or inability to use the\n Work (including but not limited to damages for loss of goodwill,\n work stoppage, computer failure or malfunction, or any and all\n other commercial damages or losses), even if such Contributor\n has been advised of the possibility of such damages.\n \n 9. Accepting Warranty or Additional Liability. While redistributing\n the Work or Derivative Works thereof, You may choose to offer,\n and charge a fee for, acceptance of support, warranty, indemnity,\n or other liability obligations and/or rights consistent with this\n License. However, in accepting such obligations, You may act only\n on Your own behalf and on Your sole responsibility, not on behalf\n of any other Contributor, and only if You agree to indemnify,\n defend, and hold each Contributor harmless for any liability\n incurred by, or claims asserted against, such Contributor by reason\n of your accepting any such warranty or additional liability.\n \n END OF TERMS AND CONDITIONS\n \n APPENDIX: How to apply the Apache License to your work.\n \n To apply the Apache License to your work, attach the following\n boilerplate notice, with the fields enclosed by brackets \"[]\"\n replaced with your own identifying information. (Don't include\n the brackets!) The text should be enclosed in the appropriate\n comment syntax for the file format. We also recommend that a\n file or class name and description of purpose be included on the\n same \"printed page\" as the copyright notice for easier\n identification within third-party archives.\n \n Copyright [yyyy] [name of copyright owner]\n \n Licensed under the Apache License, Version 2.0 (the \"License\");\n you may not use this file except in compliance with the License.\n You may obtain a copy of the License at\n \n http://www.apache.org/licenses/LICENSE-2.0\n \n Unless required by applicable law or agreed to in writing, software\n distributed under the License is distributed on an \"AS IS\" BASIS,\n WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n See the License for the specific language governing permissions and\n limitations under the License.\n ",
"summary": "A collaborative optimization framework.",
"version": "0.1.2",
"project_urls": {
"Source": "https://github.com/leonidas1312/qubots/tree/main"
},
"split_keywords": [
"optimization",
" quantum",
" classical",
" cli",
" community",
" operation research",
" decision variables",
" qubo"
],
"urls": [
{
"comment_text": null,
"digests": {
"blake2b_256": "57db497fc68b9dafaf31493fac17b28fda7b04ce6100c39b3e99a84dead5d35c",
"md5": "5739cd0234ebdd362df2bf41416198dc",
"sha256": "73ef3f20e6e078adb3908949711e956d9bfa695abb6a5fc049d48e19769e5fa5"
},
"downloads": -1,
"filename": "qubots-0.1.2-py3-none-any.whl",
"has_sig": false,
"md5_digest": "5739cd0234ebdd362df2bf41416198dc",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.9",
"size": 23365,
"upload_time": "2025-02-15T22:12:05",
"upload_time_iso_8601": "2025-02-15T22:12:05.643537Z",
"url": "https://files.pythonhosted.org/packages/57/db/497fc68b9dafaf31493fac17b28fda7b04ce6100c39b3e99a84dead5d35c/qubots-0.1.2-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": null,
"digests": {
"blake2b_256": "7d9442e8fabf1ff453d57830655a4ce007b9488fdbc6d20425bc977107588911",
"md5": "5851b88aa6eb2b39d01cf2ed69f1dd36",
"sha256": "0172c1213d73bfd3517c948ececff8253ceb7c2db8576dbcd6e49fc4af7f2bc4"
},
"downloads": -1,
"filename": "qubots-0.1.2.tar.gz",
"has_sig": false,
"md5_digest": "5851b88aa6eb2b39d01cf2ed69f1dd36",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.9",
"size": 23573,
"upload_time": "2025-02-15T22:12:06",
"upload_time_iso_8601": "2025-02-15T22:12:06.946782Z",
"url": "https://files.pythonhosted.org/packages/7d/94/42e8fabf1ff453d57830655a4ce007b9488fdbc6d20425bc977107588911/qubots-0.1.2.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2025-02-15 22:12:06",
"github": true,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"github_user": "leonidas1312",
"github_project": "qubots",
"travis_ci": false,
"coveralls": false,
"github_actions": true,
"requirements": [
{
"name": "python-dotenv",
"specs": []
},
{
"name": "Requests",
"specs": []
},
{
"name": "typer",
"specs": []
}
],
"lcname": "qubots"
}