New PR due to merge
conflicts(https://github.com/openvinotoolkit/openvino/pull/22917)
Updated the copyright year from 2018-2023 to 2018-2024 in all openvino
files
Ref. to script: CVS-101144
Command used:
```bash
git grep -lz '2018-2023 Intel Corporation' | xargs -0 sed -i '' -e 's/2018-2023 Intel Corporation/2018-2024 Intel Corporation/g'
```
- Updated paths in an entire documentation,
- updated scripts used in docs building process,
- updated docs cmake to handle new scripts,
- fixed links,
- fixed other errors found in docs.
---------
Co-authored-by: Maciej Smyk <maciejx.smyk@intel.com>
Co-authored-by: Sebastian Golebiewski <sebastianx.golebiewski@intel.com>
Co-authored-by: Karol Blaszczak <karol.blaszczak@intel.com>
Co-authored-by: Andrzej Kopytko <andrzejx.kopytko@intel.com>
Co-authored-by: Tatiana Savina <tatiana.savina@intel.com>
Co-authored-by: Vishniakov Nikolai <nikolai.vishniakov@intel.com>
### Details:
- Extended `Core` class to interact with Remote API via `compile_model`,
`create_context` and `get_default_context`.
- Added `RemoteContext` and `RemoteTensor` classes to Python API.
- Added `ClContext` and `ClImage2DTensor` classes placeholders.
- Added `VADisplayWrapper`, `VAContext` and `VASurfaceTensor` classes.
- Added utility function to raise `NotImplemented` errors.
**TODO list (with cc's):**
- [x] Decide which `VADisplayWrapper` constructors stay.
`VADisplayWrapper(VADisplay device)` (which translates to `void*`) is
quite necessary to pass memory pointers from/to external libraries.
`VADisplayWrapper(std::string& device)` is not necessary as it
introduces additional build dependency on libva itself. However, there
are no standard libva bindings that expose such functionalities.
- [ ] Proposal: change of `create_tensor` to `create_device_tensor ->
RemoteTensor` to make difference clear while API expose
`create_host_tensor -> Tensor`. (cc @ilya-lavrenov @slyalin)
- [x] Question: move CL and libva related classes to specific submodules
`openvino.intel_gpu` or keep it as-is in flat namespace? (cc
@ilya-lavrenov @slyalin @akuporos)
- [x] Decide on how memory management should work. My draft proposal:
expose in future PR as "read-only" via custom bindings to `cl_mem` in
case of accessing `ClImage2DTensor`.
- [x] Add test cases.
### Tickets:
- *129468 and 129469*
---------
Co-authored-by: Michal Lukaszewski <michal.lukaszewski@intel.com>
* link update
* link update
* link update
* Update dev_api_references.rst
* Update dev_api_references.rst
* Update apidoc.py
* notebooks links
* notebook link update
* filename update
* link update
* link update api
It's possible now to have in main.py:
parser = parse_args()
import argparse, openvino
core = openvino.Core()
class print_help(argparse.Action):
def __call__(self, parser, namespace, values, option_string):
parser.print_help()
print("\nAvailable target devices: ", (" ".join(core.available_devices)))
sys.exit()
parser.add_argument('-h', '--help', action=print_help, nargs='?', default=argparse.SUPPRESS, help='Show this help message and exit.')
args = parser.parse_args()
The details are in https://github.com/openvinotoolkit/openvino/pull/20098
* Fixed output_model logic.
* Removed InputCutInfo, disabled input cut in ovc.
* Disabled output cut, added tests for setting shapes or types for not all inputs.
* Returned support of numpy type.
* Separated MO and OVC python API tests.
* Small corrections.
* Added output dir test, exceptions test.
* Tests fixed.
* Corrected extension param description.
* Corrected input description, minor code corrections.
* Change `VPUX`/`VPU` occurrences to `NPU`
* Switch `HARDWARE_AWARE_IGNORED_PATTERNS` VPU to NPU
* Rename `MYRIAD plugin`
* Rename vpu_patterns to npu_patterns in tools/pot
* Rename vpu.json to npu.json in tools/pot
* Rename restrict_for_vpu to restrict_for_npu in tools/pot
* Change keembayOptimalBatchNum to npuOptimalBatchNum
---------
Co-authored-by: Dan <mircea-aurelian.dan@intel.com>
* Remove inits, update main one
* Fix stacklevel
* Testing wrong solution
* Testing test test
* Fix test test test test
* mo modules mo problems
* Xfail test that check stdout/err?
* not so correct solution to circular imports
* Fix or not to fix
* CMake magic, co-authors: my best team
* Fix package imports
* Fix tools inits
* Fix ovc tf
* Fix Q000
* Fix F401
* Fix linters
* Add save_model
* Remove LayoutMap
* Move test_utils to 'internal modules'
* First testing
* Missing Type
* Expand main namespace
* Change some more tests
* Add OVAny to namespace
* Add Constant and Parameter to namespace
* More tests changes
* Fix inits
* Add layout_helpers to main namespace
* Revert CMake and linux.yml with ovc
* Update main inits
* Remove MO from tools inits
* changes to init files
* Fix tests
---------
Co-authored-by: Sergey Lyalin <sergey.lyalin@intel.com>
* Fix -api sync for single -data_shape
Tickets 111187 and 111185
I wasn’t able to find C++ equivalent of Python’s `info.original_shape.is_static`. Later I realized that it shouldn’t be considered because -shape cmd arg should have higher priority for shape inference than model’s shape. So I removed it from Python.
Replace
`if benchmark.inference_only and batch_size.is_dynamic:`
with
`if allow_inference_only_or_sync and batch_size.is_dynamic:`
to reset batch_size to static in case of dynamic shape with single -data_shape
* Check only app_input_info.size() == 1 because if it's gretaer than 1, input shape is dynamic and there are more that one static shapes. Apply TODO
* Used pip wheel to build OpenVINO wheel
* Improvements
* Added python api properly into deb / rpm packages
* Use cmake -E variant from cmake 3.13
* Improvements to fix CI
* Some refactoring
* Don't use developer package for scripts projects
* Final fixes
* benchmark_app: except ALLOW_AUTO_BATCHING
Running benchmark_app.py with -b 1 -d CPU fails with
`Unsupported property ALLOW_AUTO_BATCHING by CPU plugin`.
C++ benchmark_app sets ALLOW_AUTO_BATCHING in
ov::Core::compile_model() call, which doesn't trigger the error.
* Move `ALLOW_AUTO_BATCHING` to `device_config`
* 1. refine the logic to ov::device::properties setting.
2. the config overrides will be performed if same config setting is came from CMD line.-a
Signed-off-by: Wang, Yang <yang4.wang@intel.com>
* Update configuration sample file within README.md.
* Update.
* Update.
* 1. Update configuration example file within REAMDME.md for Python version.
2. implement the config DEVICE_PROPERTIES value convertation between the string type and dictionary of Python type.
3. Update the configuration file loading and dumping logic.
Signed-off-by: Wang, Yang <yang4.wang@intel.com>
* Update.
* Update.
* Update.
* Update.
* Update.
* 1. Enable configs to be interchangeable between C++ and Python.
2. Update perf_count showing logic.
Signed-off-by: Wang, Yang <yang4.wang@intel.com>
* Revert the logic of showing show performance counters.
* Update help msg for loading config option.
---------
Signed-off-by: Wang, Yang <yang4.wang@intel.com>
* py/benchmark_app: fix -hint
Don't warn about values which are explicitly set in -hint.
That aligns C++ and Python implementations.
Ticket 106544
* Remove extra throw
* Fix code style
Jacek Pawlak