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
Hi, what do you think of the idea of having a parameter in the convert function were the user can pass a function that handles potential unsupported layers?
What I have in mind is something like torch2coreml has with the unknown_layer_converter_fn parameter.
The text was updated successfully, but these errors were encountered:
Actually I think there are two types of unknown layers. First, the one you mention which tackles those layers that CoreML does not support so that they have to be implemented in Swift. The other is for those layers that tf-coreml doesn't support, i.e. does not convert to CoreML. I think both cases would be helpful.
Hi, what do you think of the idea of having a parameter in the
convert
function were the user can pass a function that handles potential unsupported layers?What I have in mind is something like torch2coreml has with the
unknown_layer_converter_fn
parameter.The text was updated successfully, but these errors were encountered: