The name of the operator within a domain. This field MUST be present in this version of the IR.
The version of the operator set that first introduced this operator. This value MUST be the same value as the opset_version of the operator set that first published this operator. Subsequent versions of the operator set MUST NOT alter the signature or semantics of the operator once published as STABLE. This field MUST be present in this version of the IR.
This field indicates whether the syntax, semantics, or presence of this operator is in an experimental or stable stage. Once an operator is published as STABLE, it's syntax and semantics MUST NOT change in subsequent versions of the operator set. When an operator is published as EXPERIMENTAL, the syntax and semantics of the operator MAY change across operator set versions. Operators "become" stable by deprecating the experimental version and introducing a new stable operator with the same op_type.
A human-readable documentation for this operator. Markdown is allowed.
A human-readable documentation for this operator.
A human-readable documentation for this operator. Markdown is allowed.
The name of the operator within a domain.
The name of the operator within a domain. This field MUST be present in this version of the IR.
The version of the operator set that first introduced this operator.
The version of the operator set that first introduced this operator. This value MUST be the same value as the opset_version of the operator set that first published this operator. Subsequent versions of the operator set MUST NOT alter the signature or semantics of the operator once published as STABLE. This field MUST be present in this version of the IR.
This field indicates whether the syntax, semantics, or presence of this operator is in an experimental or stable stage.
This field indicates whether the syntax, semantics, or presence of this operator is in an experimental or stable stage. Once an operator is published as STABLE, it's syntax and semantics MUST NOT change in subsequent versions of the operator set. When an operator is published as EXPERIMENTAL, the syntax and semantics of the operator MAY change across operator set versions. Operators "become" stable by deprecating the experimental version and introducing a new stable operator with the same op_type.
(Since version 0.6.0) Use toPMessage
(Since version 0.6.0) Use getField that accepts a ScalaPB descriptor and returns PValue
An OperatorProto represents the immutable specification of the signature and semantics of an operator.
Operators are declared as part of an OperatorSet, which also defines the domain name for the set.
Operators are uniquely identified by a three part identifier (domain, op_type, since_version) where *domain* is the domain of an operator set that contains this operator specification.
*op_type* is the name of the operator as referenced by a NodeProto.op_type
*since_version* is the version of the operator set that this operator was initially declared in.
The name of the operator within a domain. This field MUST be present in this version of the IR.
The version of the operator set that first introduced this operator. This value MUST be the same value as the opset_version of the operator set that first published this operator. Subsequent versions of the operator set MUST NOT alter the signature or semantics of the operator once published as STABLE. This field MUST be present in this version of the IR.
This field indicates whether the syntax, semantics, or presence of this operator is in an experimental or stable stage. Once an operator is published as STABLE, it's syntax and semantics MUST NOT change in subsequent versions of the operator set. When an operator is published as EXPERIMENTAL, the syntax and semantics of the operator MAY change across operator set versions. Operators "become" stable by deprecating the experimental version and introducing a new stable operator with the same op_type.
A human-readable documentation for this operator. Markdown is allowed.