package tensorboard

Mouse Melon logoGet desktop application:
View/edit binary Protocol Buffers messages

message AllocationDescription

allocation_description.proto:11

Used in: NodeExecStats, TensorDescription

message AllocationRecord

step_stats.proto:15

An allocation/de-allocation operation performed by the allocator.

Used in: AllocatorMemoryUsed, ExecProfile

message AllocatorMemoryUsed

step_stats.proto:22

Used in: NodeExecStats

message ApiDef

api_def.proto:30

Used to specify and override the default API & behavior in the generated code for client languages, from what you would get from the OpDef alone. There will be a set of ApiDefs that are common to all client languages, and another set per client language. The per-client-language ApiDefs will inherit values from the common ApiDefs which it can either replace or modify. We separate the API definition from the OpDef so we can evolve the API while remaining backwards compatible when interpretting old graphs. Overrides go in an "api_def.pbtxt" file with a text-format ApiDefs message. WARNING: Be *very* careful changing the API for any existing op -- you can change the semantics of existing code. These changes may need to wait until a major release of TensorFlow to avoid breaking our compatibility promises.

Used in: ApiDefs

message ApiDef.Arg

api_def.proto:79

Used in: ApiDef

message ApiDef.Attr

api_def.proto:102

Description of the graph-construction-time configuration of this Op. That is to say, this describes the attr fields that will be specified in the NodeDef.

Used in: ApiDef

message ApiDef.Endpoint

api_def.proto:61

If you specify any endpoint, this will replace all of the inherited endpoints. The first endpoint should be the "canonical" endpoint, and should not be deprecated (unless all endpoints are deprecated).

Used in: ApiDef

enum ApiDef.Visibility

api_def.proto:42

Used in: ApiDef

message ApiDefs

api_def.proto:134

message AssetFileDef

meta_graph.proto:335

An asset file def for a single file or a set of sharded files with the same name.

Used in: MetaGraphDef

message AttrValue

attr_value.proto:18

Protocol buffer representing the value for an attr used to configure an Op. Comment indicates the corresponding attr type. Only the field matching the attr type may be filled.

Used in: ApiDef.Attr, FunctionDef, FunctionDef.ArgAttrs, NameAttrList, NodeDef, OpDef.AttrDef, ProfileNode, RewriterConfig.CustomGraphOptimizer

message AttrValue.ListValue

attr_value.proto:20

LINT.IfChange

Used in: AttrValue

message AudioPluginData

plugin_data.proto:24

Audio summaries created by the `tensorboard.plugins.audio.summary` module will include `SummaryMetadata` whose `plugin_data` field has as `content` a binary string that is the encoding of an `AudioPluginData` proto.

enum AudioPluginData.Encoding

plugin_data.proto:25

Used in: AudioPluginData

message AutoParallelOptions

rewriter_config.proto:14

Used in: RewriterConfig

message BoundedTensorSpecProto

struct.proto:117

A protobuf to represent tf.BoundedTensorSpec.

Used in: StructuredValue

message CallableOptions

config.proto:724

Defines a subgraph in another `GraphDef` as a set of feed points and nodes to be fetched or executed. Compare with the arguments to `Session::Run()`.

message Category

layout.proto:74

* A category contains a group of charts. Each category maps to a collapsible within the dashboard.

Used in: Layout

message Chart

layout.proto:23

* Encapsulates information on a single chart. Many charts appear in a category.

Used in: Category

message ClusterDef

cluster.proto:81

Defines a TensorFlow cluster as a set of jobs.

Used in: ConfigProto

message CodeDef

tfprof_log.proto:10

It specifies the Python callstack that creates an op.

Used in: OpLogEntry, ProfileNode

message CodeDef.Trace

tfprof_log.proto:12

Used in: CodeDef

message CollectionDef

meta_graph.proto:160

CollectionDef should cover most collections. To add a user-defined collection, do one of the following: 1. For simple data types, such as string, int, float: tf.add_to_collection("your_collection_name", your_simple_value) strings will be stored as bytes_list. 2. For Protobuf types, there are three ways to add them: 1) tf.add_to_collection("your_collection_name", your_proto.SerializeToString()) collection_def { key: "user_defined_bytes_collection" value { bytes_list { value: "queue_name: \"test_queue\"\n" } } } or 2) tf.add_to_collection("your_collection_name", str(your_proto)) collection_def { key: "user_defined_string_collection" value { bytes_list { value: "\n\ntest_queue" } } } or 3) any_buf = any_pb2.Any() tf.add_to_collection("your_collection_name", any_buf.Pack(your_proto)) collection_def { key: "user_defined_any_collection" value { any_list { value { type_url: "type.googleapis.com/tensorflow.QueueRunnerDef" value: "\n\ntest_queue" } } } } 3. For Python objects, implement to_proto() and from_proto(), and register them in the following manner: ops.register_proto_function("your_collection_name", proto_type, to_proto=YourPythonObject.to_proto, from_proto=YourPythonObject.from_proto) These functions will be invoked to serialize and de-serialize the collection. For example, ops.register_proto_function(ops.GraphKeys.GLOBAL_VARIABLES, proto_type=variable_pb2.VariableDef, to_proto=Variable.to_proto, from_proto=Variable.from_proto)

Used in: MetaGraphDef

message CollectionDef.AnyList

meta_graph.proto:203

AnyList is used for collecting Any protos.

Used in: CollectionDef

message CollectionDef.BytesList

meta_graph.proto:188

BytesList is used for collecting strings and serialized protobufs. For example: collection_def { key: "trainable_variables" value { bytes_list { value: "\n\017conv1/weights:0\022\024conv1/weights/Assign \032\024conv1/weights/read:0" value: "\n\016conv1/biases:0\022\023conv1/biases/Assign\032 \023conv1/biases/read:0" } } }

Used in: CollectionDef

message CollectionDef.FloatList

meta_graph.proto:198

FloatList is used for collecting float values.

Used in: CollectionDef

message CollectionDef.Int64List

meta_graph.proto:193

Int64List is used for collecting int, int64 and long values.

Used in: CollectionDef

message CollectionDef.NodeList

meta_graph.proto:171

NodeList is used for collecting nodes in graph. For example collection_def { key: "summaries" value { node_list { value: "input_producer/ScalarSummary:0" value: "shuffle_batch/ScalarSummary:0" value: "ImageSummary:0" } }

Used in: CollectionDef

message ConfigProto

config.proto:372

Session configuration parameters. The system picks appropriate values for fields that are not set.

message ConfigProto.Experimental

config.proto:491

Everything inside Experimental is subject to change and is not subject to API stability guarantees in https://www.tensorflow.org/guide/version_compat.

Used in: ConfigProto

message CostGraphDef

cost_graph.proto:14

Used in: RunMetadata

message CostGraphDef.AggregatedCost

cost_graph.proto:81

Total cost of this graph, typically used for balancing decisions.

Used in: CostGraphDef

message CostGraphDef.Node

cost_graph.proto:15

Used in: CostGraphDef

message CostGraphDef.Node.InputInfo

cost_graph.proto:29

Inputs of this node. They must be executed before this node can be executed. An input is a particular output of another node, specified by the node id and the output index.

Used in: Node

message CostGraphDef.Node.OutputInfo

cost_graph.proto:36

Outputs of this node.

Used in: Node

message CppShapeInferenceInputsNeeded

cpp_shape_inference.proto:28

message CppShapeInferenceResult

cpp_shape_inference.proto:10

message CppShapeInferenceResult.HandleData

cpp_shape_inference.proto:15

Used in: CppShapeInferenceResult

message CppShapeInferenceResult.HandleShapeAndType

cpp_shape_inference.proto:11

Used in: HandleData

enum DataClass

summary.proto:66

Used in: SummaryMetadata

enum DataType

types.proto:12

(== suppress_warning documentation-presence ==) LINT.IfChange

Used in: AttrValue, AttrValue.ListValue, BoundedTensorSpecProto, CostGraphDef.Node.OutputInfo, CppShapeInferenceResult.HandleShapeAndType, OpDef.ArgDef, ResourceHandleProto.DtypeAndShape, SavedVariable, StructuredValue, TensorDescription, TensorInfo, TensorProto, TensorSpecProto

message DebugOptions

debug.proto:58

Options for initializing DebuggerState in TensorFlow Debugger (tfdbg).

Used in: RunOptions

message DebugTensorWatch

debug.proto:12

Option for watching a node in TensorFlow Debugger (tfdbg).

Used in: DebugOptions

message DebuggedSourceFile

debug.proto:74

Used in: DebuggedSourceFiles

message DebuggedSourceFiles

debug.proto:91

message DeviceStepStats

step_stats.proto:79

Used in: StepStats

message DictValue

struct.proto:93

Represents a Python dict keyed by `str`. The comment on Unicode from Value.string_value applies analogously.

Used in: StructuredValue

message Event

event.proto:15

Protocol buffer representing an event that happened during the execution of a Brain model.

Used in: WorkerHeartbeatResponse

message ExecMemory

tfprof_log.proto:126

Used in: ExecProfile

message ExecProfile

tfprof_log.proto:97

Used in: ProfileNode

message ExecTime

tfprof_log.proto:122

Used in: ExecProfile

message FunctionDef

function.proto:27

A function can be instantiated when the runtime can bind every attr with a value. When a GraphDef has a call to a function, it must have binding for every attr defined in the signature. TODO(zhifengc): * device spec, etc.

Used in: FunctionDefLibrary

message FunctionDef.ArgAttrs

function.proto:37

Attributes for function arguments. These attributes are the same set of valid attributes as to _Arg nodes.

Used in: FunctionDef

message FunctionDefLibrary

function.proto:16

A library is a set of named functions.

Used in: GraphDef

message FunctionSpec

saved_object_graph.proto:148

Represents `FunctionSpec` used in `Function`. This represents a function that has been wrapped as a TensorFlow `Function`.

Used in: SavedFunction

message GPUOptions

config.proto:18

Used in: ConfigProto

message GPUOptions.Experimental

config.proto:100

Used in: GPUOptions

message GPUOptions.Experimental.VirtualDevices

config.proto:103

Configuration for breaking down a visible GPU into multiple "virtual" devices.

Used in: Experimental

message GradientDef

function.proto:123

GradientDef defines the gradient function of a function defined in a function library. A gradient function g (specified by gradient_func) for a function f (specified by function_name) must follow the following: The function 'f' must be a numerical function which takes N inputs and produces M outputs. Its gradient function 'g', which is a function taking N + M inputs and produces N outputs. I.e. if we have (y1, y2, ..., y_M) = f(x1, x2, ..., x_N), then, g is (dL/dx1, dL/dx2, ..., dL/dx_N) = g(x1, x2, ..., x_N, dL/dy1, dL/dy2, ..., dL/dy_M), where L is a scalar-value function of (x1, x2, ..., xN) (e.g., the loss function). dL/dx_i is the partial derivative of L with respect to x_i.

Used in: FunctionDefLibrary

message GraphDef

graph.proto:16

Represents the graph of operations

Used in: MetaGraphDef, RunMetadata, RunMetadata.FunctionGraphs

message GraphOptions

config.proto:256

Used in: ConfigProto

message HistogramPluginData

plugin_data.proto:24

Histogram summaries created by the `tensorboard.plugins.histogram.summary` module will include `SummaryMetadata` whose `plugin_data` field has as `content` a binary string that is the encoding of a `HistogramPluginData` proto.

message HistogramProto

summary.proto:22

Serialization format for histogram module in core/lib/histogram/histogram.h

Used in: Summary.Value

message ImagePluginData

plugin_data.proto:24

Image summaries created by the `tensorboard.plugins.image.summary` module will include `SummaryMetadata` whose `plugin_data` field has as `content` a binary string that is the encoding of an `ImagePluginData` proto.

message JobDef

cluster.proto:68

Defines a single job in a TensorFlow cluster.

Used in: ClusterDef

message Layout

layout.proto:89

* A layout encapsulates how charts are laid out within the custom scalars dashboard.

message ListValue

struct.proto:82

Represents a Python list.

Used in: StructuredValue

message LogMessage

event.proto:45

Protocol buffer used for logging messages to the events file.

Used in: Event

enum LogMessage.Level

event.proto:46

Used in: LogMessage

message MarginChartContent

layout.proto:48

* Encapsulates information on a single margin chart. A margin chart uses fill area to visualize lower and upper bounds that surround a value.

Used in: Chart

message MarginChartContent.Series

layout.proto:52

* Encapsulates a tag of data for the chart.

Used in: MarginChartContent

message Memory

tfprof_log.proto:155

Used in: ExecMemory

message MemoryStats

step_stats.proto:44

For memory tracking.

Used in: NodeExecStats

message MetaGraphDef

meta_graph.proto:34

NOTE: This protocol buffer is evolving, and will go through revisions in the coming months. Protocol buffer containing the following which are necessary to restart training, run inference. It can be used to serialize/de-serialize memory objects necessary for running computation in a graph when crossing the process boundary. It can be used for long term storage of graphs, cross-language execution of graphs, etc. MetaInfoDef GraphDef SaverDef CollectionDef TensorInfo SignatureDef

message MetaGraphDef.MetaInfoDef

meta_graph.proto:37

Meta information regarding the graph to be exported. To be used by users of this protocol buffer to encode information regarding their meta graph.

Used in: MetaGraphDef

message MultilineChartContent

layout.proto:38

* Encapsulates information on a single line chart. This line chart may have lines associated with several tags.

Used in: Chart

message NameAttrList

attr_value.proto:61

A list of attr names and their values. The whole list is attached with a string name. E.g., MatMul[T=float].

Used in: AttrValue, AttrValue.ListValue

message NamedTupleValue

struct.proto:104

Represents Python's namedtuple.

Used in: StructuredValue

message NodeDef

node_def.proto:13

Used in: FunctionDef, GraphDef

message NodeDef.ExperimentalDebugInfo

node_def.proto:66

Used in: NodeDef

message NodeExecStats

step_stats.proto:55

Time/size stats recorded for a single execution of a graph node.

Used in: DeviceStepStats

message NodeOutput

step_stats.proto:38

Output sizes recorded for a single execution of a graph node.

Used in: NodeExecStats

message NoneValue

struct.proto:79

Represents None.

Used in: StructuredValue

(message has no fields)

message NpmiPluginData

plugin_data.proto:24

nPMI summaries created by the `tensorboard.plugins.npmi.summary` module will include `SummaryMetadata` whose `plugin_data` field has as `content` a binary string that is the encoding of an `NpmiPluginData` proto.

message OpDef

op_def.proto:15

Defines an operation. A NodeDef in a GraphDef specifies an Op by using the "op" field which should match the name of a OpDef. LINT.IfChange

Used in: FunctionDef, OpList

message OpDef.ArgDef

op_def.proto:21

For describing inputs and outputs.

Used in: OpDef

message OpDef.AttrDef

op_def.proto:64

Description of the graph-construction-time configuration of this Op. That is to say, this describes the attr fields that will be specified in the NodeDef.

Used in: OpDef

message OpDeprecation

op_def.proto:159

Information about version-dependent deprecation of an op

Used in: OpDef

message OpList

op_def.proto:168

A collection of OpDefs

Used in: MetaGraphDef.MetaInfoDef

message OpLogEntry

tfprof_log.proto:28

Used in: OpLogProto

message OpLogProto

tfprof_log.proto:42

message OptimizerOptions

config.proto:209

Options passed to the graph optimizer

Used in: GraphOptions

enum OptimizerOptions.GlobalJitLevel

config.proto:243

Control the use of the compiler/jit. Experimental.

Used in: OptimizerOptions

enum OptimizerOptions.Level

config.proto:227

Optimization level

Used in: OptimizerOptions

message PairValue

struct.proto:98

Represents a (key, value) pair.

Used in: NamedTupleValue

message PrCurvePluginData

plugin_data.proto:20

message ProfileNode

tfprof_log.proto:69

Used in: ProfileProto

message ProfileProto

tfprof_log.proto:54

A proto representation of the profiler's profile. It allows serialization, shipping around and deserialization of the profiles. Please don't depend on the internals of the profile proto.

message RPCOptions

config.proto:328

Used in: ConfigProto

message RequestedExitCode

event.proto:110

Used in: WorkerHeartbeatRequest

message ResourceHandleProto

resource_handle.proto:17

Protocol buffer representing a handle to a tensorflow resource. Handles are not valid across executions, but can be serialized back and forth from within a single run.

Used in: TensorProto

message ResourceHandleProto.DtypeAndShape

resource_handle.proto:36

Protocol buffer representing a pair of (data type, tensor shape).

Used in: ResourceHandleProto

message RewriterConfig

rewriter_config.proto:24

Graph rewriting is experimental and subject to change, not covered by any API stability guarantees.

Used in: GraphOptions

enum RewriterConfig.CpuLayout

rewriter_config.proto:43

Enum for layout conversion between NCHW and NHWC on CPU. Default is OFF.

Used in: RewriterConfig

message RewriterConfig.CustomGraphOptimizer

rewriter_config.proto:193

Message to describe custom graph optimizer and its parameters

Used in: RewriterConfig

enum RewriterConfig.MemOptType

rewriter_config.proto:124

Used in: RewriterConfig

enum RewriterConfig.NumIterationsType

rewriter_config.proto:51

Enum controlling the number of times to run optimizers. The default is to run them twice.

Used in: RewriterConfig

enum RewriterConfig.Toggle

rewriter_config.proto:32

Used in: RewriterConfig

message RunMetadata

config.proto:677

Metadata output (i.e., non-Tensor) for a single Run() call.

message RunMetadata.FunctionGraphs

config.proto:689

Used in: RunMetadata

message RunOptions

config.proto:612

Options for a single Run() call.

Used in: CallableOptions

message RunOptions.Experimental

config.proto:651

Everything inside Experimental is subject to change and is not subject to API stability guarantees in https://www.tensorflow.org/guide/version_compat.

Used in: RunOptions

message RunOptions.Experimental.RunHandlerPoolOptions

config.proto:663

Options for run handler thread pool.

Used in: Experimental

enum RunOptions.TraceLevel

config.proto:615

TODO(pbar) Turn this into a TraceOptions proto which allows tracing to be controlled in a more orthogonal manner?

Used in: RunOptions

message SaveSliceInfoDef

variable.proto:75

Used in: VariableDef

message SaveableObject

saved_object_graph.proto:169

Used in: SavedObject

message SavedAsset

saved_object_graph.proto:88

A SavedAsset points to an asset in the MetaGraph. When bound to a function this object evaluates to a tensor with the absolute filename. Users should not depend on a particular part of the filename to remain stable (e.g. basename could be changed).

Used in: SavedObject

message SavedBareConcreteFunction

saved_object_graph.proto:119

Used in: SavedObject

message SavedConcreteFunction

saved_object_graph.proto:104

Stores low-level information about a concrete function. Referenced in either a SavedFunction or a SavedBareConcreteFunction.

Used in: SavedObjectGraph

message SavedConstant

saved_object_graph.proto:129

Used in: SavedObject

message SavedFunction

saved_object_graph.proto:97

A function with multiple signatures, possibly with non-Tensor arguments.

Used in: SavedObject

message SavedObject

saved_object_graph.proto:36

Used in: SavedObjectGraph

message SavedObjectGraph

saved_object_graph.proto:24

Used in: MetaGraphDef

message SavedResource

saved_object_graph.proto:162

A SavedResource represents a TF object that holds state during its lifetime. An object of this type can have a reference to a: create_resource() and an initialize() function.

Used in: SavedObject

message SavedUserObject

saved_object_graph.proto:74

A SavedUserObject is an object (in the object-oriented language of the TensorFlow program) of some user- or framework-defined class other than those handled specifically by the other kinds of SavedObjects. This object cannot be evaluated as a tensor, and therefore cannot be bound to an input of a function.

Used in: SavedObject

message SavedVariable

saved_object_graph.proto:136

Represents a Variable that is initialized by loading the contents from the checkpoint.

Used in: SavedObject

message SaverDef

saver.proto:12

Protocol buffer representing the configuration of a Saver.

Used in: MetaGraphDef

enum SaverDef.CheckpointFormatVersion

saver.proto:39

A version number that identifies a different on-disk checkpoint format. Usually, each subclass of BaseSaverBuilder works with a particular version/format. However, it is possible that the same builder may be upgraded to support a newer checkpoint format in the future.

Used in: SaverDef

message ScalarPluginData

plugin_data.proto:24

Scalar summaries created by the `tensorboard.plugins.scalar.summary` module will include `SummaryMetadata` whose `plugin_data` field has as `content` a binary string that is the encoding of an `ScalarPluginData` proto.

message ScopedAllocatorOptions

rewriter_config.proto:19

Used in: RewriterConfig

message SessionLog

event.proto:63

Protocol buffer used for logging session state.

Used in: Event

enum SessionLog.SessionStatus

event.proto:64

Used in: SessionLog

message SessionMetadata

config.proto:363

Metadata about the session. This can be used by the runtime and the Ops for debugging, monitoring, etc. The (name, version) tuple is expected to be a unique identifier for sessions within the same process. NOTE: This is currently used and propagated only by the direct session.

Used in: ConfigProto.Experimental

message SignatureDef

meta_graph.proto:317

SignatureDef defines the signature of a computation supported by a TensorFlow graph. For example, a model with two loss computations, sharing a single input, might have the following signature_def map. Note that across the two SignatureDefs "loss_A" and "loss_B", the input key, output key, and method_name are identical, and will be used by system(s) that implement or rely upon this particular loss method. The output tensor names differ, demonstrating how different outputs can exist for the same method. signature_def { key: "loss_A" value { inputs { key: "input" value { name: "input:0" dtype: DT_STRING tensor_shape: ... } } outputs { key: "loss_output" value { name: "loss_output_A:0" dtype: DT_FLOAT tensor_shape: ... } } } ... method_name: "some/package/compute_loss" } signature_def { key: "loss_B" value { inputs { key: "input" value { name: "input:0" dtype: DT_STRING tensor_shape: ... } } outputs { key: "loss_output" value { name: "loss_output_B:0" dtype: DT_FLOAT tensor_shape: ... } } } ... method_name: "some/package/compute_loss" }

Used in: MetaGraphDef

message StepStats

step_stats.proto:86

Used in: RunMetadata

message StructuredValue

struct.proto:35

`StructuredValue` represents a dynamically typed value representing various data structures that are inspired by Python data structures typically used in TensorFlow functions as inputs and outputs. For example when saving a Layer there may be a `training` argument. If the user passes a boolean True/False, that switches between two concrete TensorFlow functions. In order to switch between them in the same way after loading the SavedModel, we need to represent "True" and "False". A more advanced example might be a function which takes a list of dictionaries mapping from strings to Tensors. In order to map from user-specified arguments `[{"a": tf.constant(1.)}, {"q": tf.constant(3.)}]` after load to the right saved TensorFlow function, we need to represent the nested structure and the strings, recording that we have a trace for anything matching `[{"a": tf.TensorSpec(None, tf.float32)}, {"q": tf.TensorSpec([], tf.float64)}]` as an example. Likewise functions may return nested structures of Tensors, for example returning a dictionary mapping from strings to Tensors. In order for the loaded function to return the same structure we need to serialize it. This is an ergonomic aid for working with loaded SavedModels, not a promise to serialize all possible function signatures. For example we do not expect to pickle generic Python objects, and ideally we'd stay language-agnostic.

Used in: DictValue, FunctionSpec, ListValue, PairValue, SavedConcreteFunction, TupleValue, TypeSpecProto

message Summary

summary.proto:90

A Summary is a set of named values to be displayed by the visualizer. Summaries are produced regularly during training, as controlled by the "summary_interval_secs" attribute of the training operation. Summaries are also produced at the end of an evaluation.

Used in: Event

message Summary.Audio

summary.proto:108

Used in: Value

message Summary.Image

summary.proto:91

Used in: Value

message Summary.Value

summary.proto:121

Used in: Summary

message SummaryDescription

summary.proto:14

Metadata associated with a series of Summary data

message SummaryMetadata

summary.proto:40

A SummaryMetadata encapsulates information on which plugins are able to make use of a certain summary value.

Used in: Summary.Value, service.GetOrCreateBlobSequenceRequest, service.ScalarPointMetadata, service.StreamExperimentDataResponse, service.TensorTag, service.WriteScalarRequest.Tag, service.WriteTensorRequest.Tag

message SummaryMetadata.PluginData

summary.proto:41

Used in: SummaryMetadata

message TaggedRunMetadata

event.proto:78

For logging the metadata output for a single session.run() call.

Used in: Event

message TensorConnection

config.proto:710

Defines a connection between two tensors in a `GraphDef`.

Used in: CallableOptions

message TensorDescription

tensor_description.proto:15

Used in: NodeOutput

message TensorInfo

meta_graph.proto:217

Information about a Tensor necessary for feeding or retrieval.

Used in: AssetFileDef, SignatureDef, TensorInfo.CompositeTensor

message TensorInfo.CompositeTensor

meta_graph.proto:234

Generic encoding for composite tensors.

Used in: TensorInfo

message TensorInfo.CooSparse

meta_graph.proto:220

For sparse tensors, The COO encoding stores a triple of values, indices, and shape.

Used in: TensorInfo

message TensorProto

tensor.proto:16

Protocol buffer representing a tensor.

Used in: AttrValue, AttrValue.ListValue, BoundedTensorSpecProto, Summary.Value, VariantTensorDataProto, service.StreamExperimentDataResponse.TensorPoints, service.TensorPoint

message TensorShapeProto

tensor_shape.proto:13

Dimensions of a tensor.

Used in: AttrValue, AttrValue.ListValue, BoundedTensorSpecProto, CostGraphDef.Node.OutputInfo, CppShapeInferenceResult, CppShapeInferenceResult.HandleShapeAndType, ResourceHandleProto.DtypeAndShape, SavedVariable, StructuredValue, TensorDescription, TensorInfo, TensorProto, TensorSpecProto

message TensorShapeProto.Dim

tensor_shape.proto:15

One dimension of the tensor.

Used in: TensorShapeProto

message TensorSpecProto

struct.proto:110

A protobuf to represent tf.TensorSpec.

Used in: StructuredValue

message TextPluginData

plugin_data.proto:24

Text summaries created by the `tensorboard.plugins.text.summary` module will include `SummaryMetadata` whose `plugin_data` field has as `content` a binary string that is the encoding of an `TextPluginData` proto.

message ThreadPoolOptionProto

config.proto:303

Used in: ConfigProto

message TrackableObjectGraph

trackable_object_graph.proto:12

message TrackableObjectGraph.TrackableObject

trackable_object_graph.proto:13

Used in: TrackableObjectGraph

message TrackableObjectGraph.TrackableObject.ObjectReference

trackable_object_graph.proto:14

Used in: SavedObject, TrackableObject

message TrackableObjectGraph.TrackableObject.SerializedTensor

trackable_object_graph.proto:22

Used in: TrackableObject

message TrackableObjectGraph.TrackableObject.SlotVariableReference

trackable_object_graph.proto:40

Used in: SavedObject, TrackableObject

message Tuple

tfprof_log.proto:151

Used in: ExecTime, ProfileNode

message TupleValue

struct.proto:87

Represents a Python tuple.

Used in: StructuredValue

message TypeSpecProto

struct.proto:126

Represents a tf.TypeSpec

Used in: StructuredValue, TensorInfo.CompositeTensor

enum TypeSpecProto.TypeSpecClass

struct.proto:127

Used in: TypeSpecProto

enum VariableAggregation

variable.proto:30

Indicates how a distributed variable will be aggregated.

Used in: SavedVariable, VariableDef

message VariableDef

variable.proto:46

Protocol buffer representing a Variable.

enum VariableSynchronization

variable.proto:12

Indicates when a distributed variable will be synced.

Used in: SavedVariable, VariableDef

message VariantTensorDataProto

tensor.proto:89

Protocol buffer representing the serialization format of DT_VARIANT tensors.

Used in: TensorProto

message VerifierConfig

verifier_config.proto:12

The config for graph verifiers.

Used in: RewriterConfig

enum VerifierConfig.Toggle

verifier_config.proto:13

Used in: VerifierConfig

message VersionDef

versions.proto:24

Version information for a piece of serialized data There are different types of versions for each type of data (GraphDef, etc.), but they all have the same common shape described here. Each consumer has "consumer" and "min_producer" versions (specified elsewhere). A consumer is allowed to consume this data if producer >= min_producer consumer >= min_consumer consumer not in bad_consumers

Used in: GraphDef, SavedUserObject

message WatchdogConfig

event.proto:106

Used in: WorkerHeartbeatRequest

enum WorkerHealth

event.proto:90

Current health status of a worker.

Used in: WorkerHeartbeatResponse

message WorkerHeartbeatRequest

event.proto:114

message WorkerHeartbeatResponse

event.proto:120

enum WorkerShutdownMode

event.proto:99

Indicates the behavior of the worker when an internal error or shutdown signal is received.

Used in: WorkerHeartbeatRequest