Is your feature request related to a problem? Please describe.
Existing graph ops represented as function only and the graph registry method is clunky. This makes graph ops less flexible when calling/creating graph_ops outside exporter. For example we want to specify list of ops to be performed on model, from another function/class.
Describe the solution you'd like
Represent graph ops as callable class, clean up graph ops registry.
Is your feature request related to a problem? Please describe. Existing graph ops represented as function only and the graph registry method is clunky. This makes graph ops less flexible when calling/creating graph_ops outside exporter. For example we want to specify list of ops to be performed on model, from another function/class.
Describe the solution you'd like Represent graph ops as callable class, clean up graph ops registry.