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
In the provided documents, it showed an example of custom operator with attribute "padding_length", which has type int64. (code listed below.) What if this attribute is a list? How should I modify the example code to accommadate this change?
Since attribute with list type is pretty common, such as the kernel of a conv op, I assume the list type attribute is already supported.
@wenbingl I found that in the function cast_attributes, only int, float and string types are supported. Is it true that list of ints/floats is not supported?
@wenbingl I found that in the function cast_attributes, only int, float and string types are supported. Is it true that list of ints/floats is not supported?
Yes, if they are vector, they can be input as an ONNX initializer, i.e. a tensor-like type.
Yes, if they are vector, they can be input as an ONNX initializer, i.e. a tensor-like type.
@wenbingl What if the operator attribute need to be a vector? Since it is quite common to have vector attributes(such as conv kernel & paddings), will this feature be supported soon?
In the provided documents, it showed an example of custom operator with attribute "padding_length", which has type int64. (code listed below.) What if this attribute is a list? How should I modify the example code to accommadate this change?
Since attribute with list type is pretty common, such as the kernel of a conv op, I assume the list type attribute is already supported.
The text was updated successfully, but these errors were encountered: