-
Notifications
You must be signed in to change notification settings - Fork 682
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Test OpenVINO export #1681
Test OpenVINO export #1681
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @adrianboguszewski. I have one suggestion to rename framework to export_type. Since framework term is not used in the main code base, the code might flow better if we stick to the export_type
term that is used throughout the codebase
9def7d5
to
cf0da5d
Compare
cf0da5d
to
ab5a35f
Compare
Signed-off-by: Adrian Boguszewski <adrian.boguszewski@intel.com>
deeecbb
to
fb696df
Compare
@samet-akcay your review has been incorporated :) |
@adrianboguszewski @samet-akcay This my command: mvtec.yaml:
and efficient_ad.yaml:
|
I believe @samet-akcay can answer this question better |
π Description
@samet-akcay @ashwinvaidya17 is it the right place to test if all models are exportable to OpenVINO?
β¨ Changes
Select what type of change your PR is:
β Checklist
Before you submit your pull request, please make sure you have completed the following steps: