* Changed C++ OpenVINO Runtime User Guide integration * Remove IE from C++ guide * Fixed comments * Additional fix * Fixed some comments * Some new documents * Fixed some comments * Added Python snippets * Added sphinx tabs * Removed tabs * Removed group-tab * Added additional lines * Fixed typo * Fixed comments and build * Try to fix complex tabs * Fixed some typos * Added python code for model representation * Added more python code * Added serialize/visualize python examples * Simplify integration pipeline * Fixed typo * Try to fix tabs * Extend CompiledModel guide * Resolve merge conflict * Added separate infer request guide * Fixed build * Added cancel infer request method * Update docs/snippets/ov_model_snippets.py Co-authored-by: Jan Iwaszkiewicz <jan.iwaszkiewicz@intel.com> * Fixed comments * Fixed typo * Extend visualize pass * Fixed comments * Fixed build * Fixed typo * Update docs/snippets/ov_infer_request.py Co-authored-by: Jan Iwaszkiewicz <jan.iwaszkiewicz@intel.com> * Update docs/snippets/ov_infer_request.py Co-authored-by: Jan Iwaszkiewicz <jan.iwaszkiewicz@intel.com> * Update docs/OV_Runtime_UG/integrate_with_your_application.md Co-authored-by: Andrey Zaytsev <andrey.zaytsev@intel.com> * Update docs/OV_Runtime_UG/integrate_with_your_application.md Co-authored-by: Andrey Zaytsev <andrey.zaytsev@intel.com> * Update docs/OV_Runtime_UG/integrate_with_your_application.md Co-authored-by: Andrey Zaytsev <andrey.zaytsev@intel.com> * Update docs/OV_Runtime_UG/integrate_with_your_application.md Co-authored-by: Andrey Zaytsev <andrey.zaytsev@intel.com> * Update docs/OV_Runtime_UG/integrate_with_your_application.md Co-authored-by: Andrey Zaytsev <andrey.zaytsev@intel.com> * Update docs/OV_Runtime_UG/integrate_with_your_application.md Co-authored-by: Andrey Zaytsev <andrey.zaytsev@intel.com> * Update docs/OV_Runtime_UG/integrate_with_your_application.md Co-authored-by: Andrey Zaytsev <andrey.zaytsev@intel.com> * Update docs/OV_Runtime_UG/integrate_with_your_application.md Co-authored-by: Andrey Zaytsev <andrey.zaytsev@intel.com> * Update docs/OV_Runtime_UG/integrate_with_your_application.md Co-authored-by: Andrey Zaytsev <andrey.zaytsev@intel.com> * Update docs/OV_Runtime_UG/integrate_with_your_application.md Co-authored-by: Andrey Zaytsev <andrey.zaytsev@intel.com> * Update docs/OV_Runtime_UG/integrate_with_your_application.md Co-authored-by: Andrey Zaytsev <andrey.zaytsev@intel.com> * Update docs/OV_Runtime_UG/integrate_with_your_application.md Co-authored-by: Andrey Zaytsev <andrey.zaytsev@intel.com> * Update docs/OV_Runtime_UG/integrate_with_your_application.md Co-authored-by: Andrey Zaytsev <andrey.zaytsev@intel.com> * Update docs/OV_Runtime_UG/integrate_with_your_application.md Co-authored-by: Andrey Zaytsev <andrey.zaytsev@intel.com> * Update docs/OV_Runtime_UG/integrate_with_your_application.md Co-authored-by: Andrey Zaytsev <andrey.zaytsev@intel.com> * Update docs/OV_Runtime_UG/model_representation.md Co-authored-by: Andrey Zaytsev <andrey.zaytsev@intel.com> * Update docs/OV_Runtime_UG/model_representation.md Co-authored-by: Andrey Zaytsev <andrey.zaytsev@intel.com> * Fixed comments * Fixed doc * Fixed merge Co-authored-by: Jan Iwaszkiewicz <jan.iwaszkiewicz@intel.com> Co-authored-by: Andrey Zaytsev <andrey.zaytsev@intel.com>
6.6 KiB
Model Representation in OpenVINO™ Runtime
In OpenVINO™ Runtime a model is represented by the ov::Model class.
The ov::Model object stores shared pointers to ov::op::v0::Parameter, ov::op::v0::Result and ov::op::Sink operations that are inputs, outputs and sinks of the graph.
Sinks of the graph have no consumers and are not included in the results vector. All other operations hold each other via shared pointers: child operation holds its parent (hard link). If an operation has no consumers and it's not the Result or Sink operation
(shared pointer counter is zero), then it will be destructed and won't be accessible anymore.
Each operation in ov::Model has the std::shared_ptr<ov::Node> type.
For details on how to build a model in OpenVINO™ Runtime, see the [Build a Model in OpenVINO™ Runtime](@ref build_model) section.
OpenVINO™ Runtime allows using tensor names or indexes to work wit model inputs/outputs. To get model input/output ports, use the ov::Model::inputs() or ov::Model::outputs() methods respectively.
@sphinxdirective
.. tab:: C++
.. doxygensnippet:: docs/snippets/ov_model_snippets.cpp
:language: cpp
:fragment: [all_inputs_ouputs]
.. tab:: Python
.. doxygensnippet:: docs/snippets/ov_model_snippets.py
:language: python
:fragment: [all_inputs_ouputs]
@endsphinxdirective
OpenVINO™ Runtime model representation uses special classes to work with model data types and shapes. For data types the ov::element::Type is used.
Shapes Representation
OpenVINO™ Runtime provides two types for shape representation:
-
ov::Shape- Represents static (fully defined) shapes. -
ov::PartialShape- Represents dynamic shapes. That means that the rank or some of dimensions are dynamic (dimension defines an interval or undefined).ov::PartialShapecan be converted toov::Shapeusing theget_shape()method if all dimensions are static; otherwise the conversion raises an exception.
@sphinxdirective
.. tab:: C++
.. doxygensnippet:: docs/snippets/ov_model_snippets.cpp :language: cpp :fragment: [ov:partial_shape]
.. tab:: Python
.. doxygensnippet:: docs/snippets/ov_model_snippets.py :language: python :fragment: [ov:partial_shape]
@endsphinxdirective
But in most cases before getting static shape using get_shape() method, you need to check that shape is static.
Operations
The ov::Op class represents any abstract operation in the model representation. Use this class to create custom operations.
Operation Sets
Operation set (opset) is a collection of operations that can be used to construct a model. The ov::OpSet class provides a functionality to work with operation sets.
For each operation set, OpenVINO™ Runtime provides a separate namespace, for example opset8.
Each OpenVINO™ Release release introduces new operations and add these operations to a new operation set. New operation sets help to introduce a new version of operations that change behavior of previous operations. Using operation sets allows you to avoid changes in your application if new operations have been introduced.
For a complete list of operation sets supported in OpenVINO™ toolkit, see Available Operations Sets.
To add support of custom operations, see the Add Custom OpenVINO Operations document.
Build a Model in OpenVINO™ Runtime
You can create a model from source. This section illustrates how to construct a model composed of operations from an available operation set.
Operation set opsetX integrates a list of pre-compiled operations that work for this purpose. In other words, opsetX defines a set of operations for building a graph.
To build an ov::Model instance from opset8 operations, include the following files:
@sphinxdirective
.. tab:: C++
.. doxygensnippet:: docs/snippets/ov_model_snippets.cpp
:language: cpp
:fragment: [ov:include]
.. tab:: Python
.. doxygensnippet:: docs/snippets/ov_model_snippets.py
:language: python
:fragment: [import]
@endsphinxdirective
The following code demonstrates how to create a simple model:
@sphinxdirective
.. tab:: C++
.. doxygensnippet:: docs/snippets/ov_model_snippets.cpp
:language: cpp
:fragment: [ov:create_simple_model]
.. tab:: Python
.. doxygensnippet:: docs/snippets/ov_model_snippets.py
:language: python
:fragment: [ov:create_simple_model]
@endsphinxdirective
The following code creates a model with several outputs:
@sphinxdirective
.. tab:: C++
.. doxygensnippet:: docs/snippets/ov_model_snippets.cpp
:language: cpp
:fragment: [ov:create_advanced_model]
.. tab:: Python
.. doxygensnippet:: docs/snippets/ov_model_snippets.py
:language: python
:fragment: [ov:create_advanced_model]
@endsphinxdirective
Model debug capabilities
OpenVINO™ provides several debug capabilities:
- To receive additional messages about applied model modifications, rebuild the OpenVINO™ Runtime library with the
-DENABLE_OPENVINO_DEBUG=ONoption. - Model can be visualized to image from the xDot format: @sphinxdirective
.. tab:: C++
.. doxygensnippet:: docs/snippets/ov_model_snippets.cpp
:language: cpp
:fragment: [ov:visualize]
.. tab:: Python
.. doxygensnippet:: docs/snippets/ov_model_snippets.py
:language: python
:fragment: [ov:visualize]
@endsphinxdirective
`ov::pass::VisualizeTree` can be parametrized via environment variables:
OV_VISUALIZE_TREE_OUTPUT_SHAPES=1 - visualize shapes
OV_VISUALIZE_TREE_OUTPUT_TYPES=1 - visualize types
OV_VISUALIZE_TREE_MIN_MAX_DENORMAL=1 - pretty denormal values
OV_VISUALIZE_TREE_RUNTIME_INFO=1 - print runtime information
OV_VISUALIZE_TREE_IO=1 - print I/O ports
OV_VISUALIZE_TREE_MEMBERS_NAME=1 - print member names
- Also model can be serialized to IR: @sphinxdirective
.. tab:: C++
.. doxygensnippet:: docs/snippets/ov_model_snippets.cpp
:language: cpp
:fragment: [ov:serialize]
.. tab:: Python
.. doxygensnippet:: docs/snippets/ov_model_snippets.py
:language: python
:fragment: [ov:serialize]
@endsphinxdirective