Global explanations containing the top most important features after training.
A list of the top global explanations. Sorted by absolute value of attribution in descending order.
Class label for this set of global explanations. Will be empty/null for binary logistic and linear regression models. Sorted alphabetically in descending order.
Inheritancebuiltins.object > proto.message.Message > GlobalExplanation
Explanation(mapping=None, *, ignore_unknown_fields=False, **kwargs)
Explanation for a single feature.
Return True if any field is truthy, False otherwise.
Return True if this field was set to something non-zero on the wire.
In most cases, this method will return True when
would return a truthy value and False when it would return a falsy
value, so explicitly calling this is not useful.
The exception case is empty messages explicitly set on the wire,
which are falsy from
__getattr__. This method allows to
distinguish between an explicitly provided empty message and the
absence of that message, which is useful in some edge cases.
The most common edge case is the use of
to get a boolean that distinguishes between
(or the same for a string, int, etc.). This library transparently
handles that case for you, but this method remains available to
accommodate cases not automatically covered.
The name of the field.
|bool||Whether the field's value corresponds to a non-empty wire serialization.|
Delete the value on the given field.
This is generally equivalent to setting a falsy value.
Return True if the messages are equal, False otherwise.
Retrieve the given field's value.
In protocol buffers, the presence of a field on a message is sufficient for it to always be "present".
For primitives, a value of the correct type will always be returned (the "falsy" values in protocol buffers consistently match those in Python). For repeated fields, the falsy value is always an empty sequence.
For messages, protocol buffers does distinguish between an empty
message and absence, but this distinction is subtle and rarely
relevant. Therefore, this method always returns an empty message
(following the official implementation). To check for message
key in self (in other words,
Some well-known protocol buffer types (e.g. ``google.protobuf.Timestamp``) will be converted to their Python equivalents. See the ``marshal`` module for more details.
Return True if the messages are unequal, False otherwise.
Set the value on the given field.
For well-known protocol buffer types which are marshalled, either the protocol buffer object or the Python equivalent is accepted.