Bumps [jsonschema](https://github.com/python-jsonschema/jsonschema) from 4.17.0 to 4.22.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/python-jsonschema/jsonschema/releases">jsonschema's releases</a>.</em></p> <blockquote> <h2>v4.22.0</h2> <!-- raw HTML omitted --> <h2>What's Changed</h2> <ul> <li>Improve <code>best_match</code> (and thereby error messages from <code>jsonschema.validate</code>) in cases where there are multiple <em>sibling</em> errors from applying <code>anyOf</code> / <code>allOf</code> -- i.e. when multiple elements of a JSON array have errors, we now do prefer showing errors from earlier elements rather than simply showing an error for the full array (<a href="https://redirect.github.com/python-jsonschema/jsonschema/issues/1250">#1250</a>).</li> <li>(Micro-)optimize equality checks when comparing for JSON Schema equality by first checking for object identity, as <code>==</code> would.</li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/shinnar"><code>@shinnar</code></a> made their first contribution in <a href="https://redirect.github.com/python-jsonschema/jsonschema/pull/1224">python-jsonschema/jsonschema#1224</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/python-jsonschema/jsonschema/compare/v4.21.1...v4.22.0">https://github.com/python-jsonschema/jsonschema/compare/v4.21.1...v4.22.0</a></p> <h2>v4.21.1</h2> <!-- raw HTML omitted --> <ul> <li>Slightly speed up the <code>contains</code> keyword by removing some unnecessary validator (re-)creation.</li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/python-jsonschema/jsonschema/compare/v4.21.0...v4.21.1">https://github.com/python-jsonschema/jsonschema/compare/v4.21.0...v4.21.1</a></p> <h2>v4.21.0</h2> <!-- raw HTML omitted --> <h2>What's Changed</h2> <ul> <li>Fix the behavior of <code>enum</code> in the presence of <code>0</code> or <code>1</code> to properly consider <code>True</code> and <code>False</code> unequal (<a href="https://redirect.github.com/python-jsonschema/jsonschema/issues/1208">#1208</a>).</li> <li>Special case the error message for <code>{min,max}{Items,Length,Properties}</code> when they're checking for emptiness rather than true length.</li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/otto-ifak"><code>@otto-ifak</code></a> made their first contribution in <a href="https://redirect.github.com/python-jsonschema/jsonschema/pull/1208">python-jsonschema/jsonschema#1208</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/python-jsonschema/jsonschema/compare/v4.20.0...v4.21.0">https://github.com/python-jsonschema/jsonschema/compare/v4.20.0...v4.21.0</a></p> <h2>v4.20.0</h2> <ul> <li>Properly consider items (and properties) to be evaluated by <code>unevaluatedItems</code> (resp. <code>unevaluatedProperties</code>) when behind a <code>$dynamicRef</code> as specified by the 2020 and 2019 specifications.</li> <li><code>jsonschema.exceptions.ErrorTree.__setitem__</code> is now deprecated. More broadly, in general users of <code>jsonschema</code> should never be mutating objects owned by the library.</li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/python-jsonschema/jsonschema/compare/v4.19.2...v4.20.0">https://github.com/python-jsonschema/jsonschema/compare/v4.19.2...v4.20.0</a></p> <h2>v4.19.2</h2> <!-- raw HTML omitted --> <ul> <li>Fix the error message for additional items when used with heterogeneous arrays.</li> <li>Don't leak the <code>additionalItems</code> keyword into JSON Schema draft 2020-12, where it was replaced by <code>items</code>.</li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/python-jsonschema/jsonschema/compare/v4.19.1...v4.19.2">https://github.com/python-jsonschema/jsonschema/compare/v4.19.1...v4.19.2</a></p> <h2>v4.19.1</h2> <!-- raw HTML omitted --> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/python-jsonschema/jsonschema/blob/main/CHANGELOG.rst">jsonschema's changelog</a>.</em></p> <blockquote> <h1>v4.22.0</h1> <ul> <li>Improve <code>best_match</code> (and thereby error messages from <code>jsonschema.validate</code>) in cases where there are multiple <em>sibling</em> errors from applying <code>anyOf</code> / <code>allOf</code> -- i.e. when multiple elements of a JSON array have errors, we now do prefer showing errors from earlier elements rather than simply showing an error for the full array (<a href="https://redirect.github.com/python-jsonschema/jsonschema/issues/1250">#1250</a>).</li> <li>(Micro-)optimize equality checks when comparing for JSON Schema equality by first checking for object identity, as <code>==</code> would.</li> </ul> <h1>v4.21.1</h1> <ul> <li>Slightly speed up the <code>contains</code> keyword by removing some unnecessary validator (re-)creation.</li> </ul> <h1>v4.21.0</h1> <ul> <li>Fix the behavior of <code>enum</code> in the presence of <code>0</code> or <code>1</code> to properly consider <code>True</code> and <code>False</code> unequal (<a href="https://redirect.github.com/python-jsonschema/jsonschema/issues/1208">#1208</a>).</li> <li>Special case the error message for <code>{min,max}{Items,Length,Properties}</code> when they're checking for emptiness rather than true length.</li> </ul> <h1>v4.20.0</h1> <ul> <li>Properly consider items (and properties) to be evaluated by <code>unevaluatedItems</code> (resp. <code>unevaluatedProperties</code>) when behind a <code>$dynamicRef</code> as specified by the 2020 and 2019 specifications.</li> <li><code>jsonschema.exceptions.ErrorTree.__setitem__</code> is now deprecated. More broadly, in general users of <code>jsonschema</code> should never be mutating objects owned by the library.</li> </ul> <h1>v4.19.2</h1> <ul> <li>Fix the error message for additional items when used with heterogeneous arrays.</li> <li>Don't leak the <code>additionalItems</code> keyword into JSON Schema draft 2020-12, where it was replaced by <code>items</code>.</li> </ul> <h1>v4.19.1</h1> <ul> <li>Single label hostnames are now properly considered valid according to the <code>hostname</code> format. This is the behavior specified by the relevant RFC (1123). IDN hostname behavior was already correct.</li> </ul> <h1>v4.19.0</h1> <ul> <li>Importing the <code>Validator</code> protocol directly from the package root is deprecated. Import it from <code>jsonschema.protocols.Validator</code> instead.</li> <li>Automatic retrieval of remote references (which is still deprecated) now properly succeeds even if the retrieved resource does not declare which version of JSON Schema it uses. Such resources are assumed to be 2020-12 schemas. This more closely matches the pre-referencing library behavior.</li> </ul> <h1>v4.18.6</h1> <ul> <li>Set a <code>jsonschema</code> specific user agent when automatically retrieving remote references (which is deprecated).</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
||
|---|---|---|
| .github | ||
| cmake | ||
| docs | ||
| licensing | ||
| samples | ||
| scripts | ||
| src | ||
| tests | ||
| thirdparty | ||
| tools | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| CMakeLists.txt | ||
| CONTRIBUTING.md | ||
| CONTRIBUTING_DOCS.md | ||
| CONTRIBUTING_PR.md | ||
| Jenkinsfile | ||
| LICENSE | ||
| README.md | ||
| SECURITY.md | ||
| conan.lock | ||
| conanfile.txt | ||
| cspell.json | ||
| install_build_dependencies.sh | ||
| vcpkg.json | ||
README.md
Welcome to OpenVINO™, an open-source software toolkit for optimizing and deploying deep learning models.
- Inference Optimization: Boost deep learning performance in computer vision, automatic speech recognition, generative AI, natural language processing with large and small language models, and many other common tasks.
- Flexible Model Support: Use models trained with popular frameworks such as TensorFlow, PyTorch, ONNX, Keras, and PaddlePaddle.
- Broad Platform Compatibility: Reduce resource demands and efficiently deploy on a range of platforms from edge to cloud.
- Community and Ecosystem: Join an active community contributing to the enhancement of deep learning performance across various domains.
Check out the OpenVINO Cheat Sheet for a quick reference.
Installation
Get your preferred distribution of OpenVINO or use this command for quick installation:
pip install openvino
Check system requirements and supported devices for detailed information.
Tutorials and Examples
OpenVINO Quickstart example will walk you through the basics of deploying your first model.
Learn how to optimize and deploy popular models with the OpenVINO Notebooks📚:
Here are easy-to-follow code examples demonstrating how to run PyTorch and TensorFlow model inference using OpenVINO:
PyTorch Model
import openvino as ov
import torch
import torchvision
# load PyTorch model into memory
model = torch.hub.load("pytorch/vision", "shufflenet_v2_x1_0", weights="DEFAULT")
# convert the model into OpenVINO model
example = torch.randn(1, 3, 224, 224)
ov_model = ov.convert_model(model, example_input=(example,))
# compile the model for CPU device
core = ov.Core()
compiled_model = core.compile_model(ov_model, 'CPU')
# infer the model on random data
output = compiled_model({0: example.numpy()})
TensorFlow Model
import numpy as np
import openvino as ov
import tensorflow as tf
# load TensorFlow model into memory
model = tf.keras.applications.MobileNetV2(weights='imagenet')
# convert the model into OpenVINO model
ov_model = ov.convert_model(model)
# compile the model for CPU device
core = ov.Core()
compiled_model = core.compile_model(ov_model, 'CPU')
# infer the model on random data
data = np.random.rand(1, 224, 224, 3)
output = compiled_model({0: data})
OpenVINO also supports CPU, GPU, and NPU devices and works with models in TensorFlow, PyTorch, ONNX, TensorFlow Lite, PaddlePaddle model formats. With OpenVINO you can do automatic performance enhancements at runtime customized to your hardware (preserving model accuracy), including: asynchronous execution, batch processing, tensor fusion, load balancing, dynamic inference parallelism, automatic BF16 conversion, and more.
OpenVINO Ecosystem
- 🤗Optimum Intel - a simple interface to optimize Transformers and Diffusers models.
- Neural Network Compression Framework (NNCF) - advanced model optimization techniques including quantization, filter pruning, binarization, and sparsity.
- GenAI Repository and OpenVINO Tokenizers - resources and tools for developing and optimizing Generative AI applications.
- OpenVINO™ Model Server (OVMS) - a scalable, high-performance solution for serving models optimized for Intel architectures.
- Intel® Geti™ - an interactive video and image annotation tool for computer vision use cases.
Check out the Awesome OpenVINO repository to discover a collection of community-made AI projects based on OpenVINO!
Documentation
User documentation contains detailed information about OpenVINO and guides you from installation through optimizing and deploying models for your AI applications.
Developer documentation focuses on how OpenVINO components work and describes building and contributing processes.
Contribution and Support
Check out Contribution Guidelines for more details. Read the Good First Issues section, if you're looking for a place to start contributing. We welcome contributions of all kinds!
You can ask questions and get support on:
- GitHub Issues.
- OpenVINO channels on the Intel DevHub Discord server.
- The
openvinotag on Stack Overflow*.
Additional Resources
License
OpenVINO™ Toolkit is licensed under Apache License Version 2.0. By contributing to the project, you agree to the license and copyright terms therein and release your contribution under these terms.
* Other names and brands may be claimed as the property of others.