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
The goal is to create an infrastructure via which these custom-ops can be stored as functions for ease of usage with the optimizer and rewriter tools. If the functions are not desired in the graph, the graph can be simply inlined to get back to the original form.
Road-map for this task:
The content you are editing has changed. Please copy your edits and refresh the page.
Define these as ONNX functions (and test/validate them)
Extend the ONNX standard by adding these as function-ops
Potentially use these in a rewriting-optimizer (that identifies matches to the function-body and extracts them out as either model-local functions or standard ONNX ops, if they have been added to the ONNX standard as in step 2).
For steps 1 and 2, the corresponding custom op definition in ORT is also a helpful starting point.
There are a few commonly used transformer-based optimizations using custom-ops in onnxruntime some of which are listed.
Custom ops to be converted to functions for ONNX Script (will add more custom ops based on findings and priority) :
Tasks
The goal is to create an infrastructure via which these custom-ops can be stored as functions for ease of usage with the optimizer and rewriter tools. If the functions are not desired in the graph, the graph can be simply inlined to get back to the original form.
Road-map for this task:
Tasks
@gramalingam Feel free to edit/add any more information that I might have missed regarding this item.
The text was updated successfully, but these errors were encountered: