-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[Good First Issue]: Extend ONNX Frontend with BitwiseNot-18 operator #20793
Comments
.take |
Thank you for looking into this issue! Please let us know if you have any questions or require any help. |
Hello @rupeshs! Thank you for taking a look, please let us know if you have any questions. Just yesterday our |
Hello @p-wysocki , created PR #21698 |
Hello @rupeshs, sorry for the late reply - the holiday season just ended. We'll take a look at your PR as soon as possible, thank you for your contribution! Also, I am happy to announce that we have created a channel dedicated to Good First Issues support on our Intel DevHub Discord server! Join it to receive support, engage in discussions, ask questions and talk to OpenVINO developers. |
Context
Neural networks are graphs consisting of nodes called operators. Each operator corresponds to a mathematical function, usually described in framework's documentation or an AI standard, such as ONNX.
OpenVINO ONNX Frontend is a component responsible for working with ONNX graphs and requires implementation of different ONNX operators in order to use ONNX models.
This task requires extending OpenVINO ONNX Frontend with
BitwiseNot
operator, using the existing ov::op::v13::BitwiseNot.Necessary help will be provided by ONNX Fronted team.
What needs to be done?
Operator details can be found in ONNX Operators
More details can be found in ONNX Changelog
.hpp
and.cpp
files herebitwise_not
should be placed in opset 1 namespace.More details in adding operators to ONNX Frontend guide
Example Pull Requests
Resources
Contact points
@mitruska
@gkrivor
@p-wysocki
Ticket
118961
The text was updated successfully, but these errors were encountered: