You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use-case: I want to move custom data through the graph.
I want to reuse onnx graph scheduling capabilites to add pre- and post-processing custom ops. In particular post-processing nodes will produce non-tensor objects (e.g. cv::Mat). Therefore I need a way to extend onnxruntime with custom input/output types or a way to extend ort::Custom::Tensor.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I can extend onnxruntime with custom ops.
Example:
Although this works, I'm currently limited to use
Ort::Custom::Tensor<T>
for input/output types.Can I also extend onnxruntime with custom data-types?
E.g.
Use-case: I want to move custom data through the graph.
I want to reuse onnx graph scheduling capabilites to add pre- and post-processing custom ops. In particular post-processing nodes will produce non-tensor objects (e.g.
cv::Mat
). Therefore I need a way to extend onnxruntime with custom input/output types or a way to extend ort::Custom::Tensor.Beta Was this translation helpful? Give feedback.
All reactions