Get desktop application:
View/edit binary Protocol Buffers messages
Used in:
Float feature column and split threshold describing the rule feature <= threshold.
If feature column is multivalent, this holds the index of the dimension for the split. Defaults to 0.
default direction for missing values.
Node children indexing into a contiguous vector of nodes starting from the root.
Used in:
Categorical feature column and split describing the rule feature value == value.
If feature column is multivalent, this holds the index of the dimension for the split. Defaults to 0.
Node children indexing into a contiguous vector of nodes starting from the root.
DebugOutput contains outputs useful for debugging/model interpretation, at the individual example-level. Debug outputs that are available to the user are: 1) Directional feature contributions (DFCs) 2) Node IDs for ensemble prediction path 3) Leaf node IDs.
Return the logits and associated feature splits across prediction paths for each tree, for every example, at predict time. We will use these values to compute DFCs in Python, by subtracting each child prediction from its parent prediction and associating this change with its respective feature id.
Used in:
Left is the default direction.
TODO(nponomareva): move out of boosted_trees and rename to trees.proto
Used in:
Float feature column and split threshold describing the rule feature <= threshold.
Node children indexing into a contiguous vector of nodes starting from the root.
Used in:
Number of trees that we have attempted to build. After pruning, these trees might have been removed.
Number of layers that we have attempted to build. After pruning, these layers might have been removed.
The start (inclusive) and end (exclusive) ids of the nodes in the latest layer of the latest tree.
Leaves can either hold dense or sparse information.
Used in:
,See third_party/tensorflow/contrib/decision_trees/ proto/generic_tree_model.proto for a description of how vector and sparse_vector might be used.
Node describes a node in a tree.
Used in:
NodeMetadata encodes metadata associated with each node in a tree.
Used in:
The gain associated with this node.
The original leaf node before this node was split.
Used in:
Tree describes a list of connected nodes. Node 0 must be the root and can carry any payload including a leaf in the case of representing the bias. Note that each node id is implicitly its index in the list of nodes.
Used in:
TreeEnsemble describes an ensemble of decision trees.
Metadata that is used during the training.
Used in:
Number of layers grown for this tree.
Whether the tree is finalized in that no more layers can be grown.
If tree was finalized and post pruning happened, it is possible that cache still refers to some nodes that were deleted or that the node ids changed (e.g. node id 5 became node id 2 due to pruning of the other branch). The mapping below allows us to understand where the old ids now map to and how the values should be adjusted due to post-pruning. The size of the list should be equal to the number of nodes in the tree before post-pruning happened. If the node was pruned, it will have new_node_id equal to the id of a node that this node was collapsed into. For a node that didn't get pruned, it is possible that its id still changed, so new_node_id will have the corresponding id in the pruned tree. If post-pruning didn't happen, or it did and it had no effect (e.g. no nodes got pruned), this list will be empty.
Used in:
Used in: