package angel

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

message AllocationDescription

allocation_description.proto:9

Used in: NodeExecStats, TensorDescription

message AllocationRecord

step_stats.proto:12

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

Used in: AllocatorMemoryUsed

message AllocatorMemoryUsed

step_stats.proto:19

Used in: NodeExecStats

message AssetFileDef

meta_graph.proto:313

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:16

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: FunctionDef, NameAttrList, NodeDef, OpDef.AttrDef

message AttrValue.ListValue

attr_value.proto:18

LINT.IfChange

Used in: AttrValue

message BatchingParameters

session_bundle_config.proto:73

Batching parameters. Each individual parameter is optional. If omitted, the default value from the relevant batching config struct (SharedBatchScheduler ::Options or BatchSchedulerRetrier::Options) is used.

SharedBatchScheduler options (see shared_batch_scheduler.h):

Used in: SessionBundleConfig

message CollectionDef

meta_graph.proto:150

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:193

AnyList is used for collecting Any protos.

Used in: CollectionDef

message CollectionDef.BytesList

meta_graph.proto:178

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:188

FloatList is used for collecting float values.

Used in: CollectionDef

message CollectionDef.Int64List

meta_graph.proto:183

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

Used in: CollectionDef

message CollectionDef.NodeList

meta_graph.proto:161

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 CostGraphDef

cost_graph.proto:10

Used in: RunMetadata

message CostGraphDef.Node

cost_graph.proto:11

Used in: CostGraphDef

message CostGraphDef.Node.InputInfo

cost_graph.proto:25

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:32

Outputs of this node.

Used in: Node

enum DataType

types.proto:9

LINT.IfChange

Used in: AttrValue, AttrValue.ListValue, CostGraphDef.Node.OutputInfo, OpDef.ArgDef, TensorDescription, TensorInfo, TensorProto, serving.GetModelStatusResponse, serving.Instance

message DebugOptions

debug.proto:54

Options for initializing DebuggerState in TensorFlow Debugger (tfdbg).

Used in: RunOptions

message DebugTensorWatch

debug.proto:10

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

Used in: DebugOptions

message DebuggedSourceFile

debug.proto:70

Used in: DebuggedSourceFiles

message DebuggedSourceFiles

debug.proto:87

message DeviceStepStats

step_stats.proto:76

Used in: StepStats

message FileSystemStoragePathSourceConfig

file_system_storage_path_source.proto:9

Config proto for FileSystemStoragePathSource.

message FileSystemStoragePathSourceConfig.ServableToMonitor

file_system_storage_path_source.proto:43

A servable name and base path to look for versions of the servable.

Used in: FileSystemStoragePathSourceConfig

message FileSystemStoragePathSourceConfig.ServableVersionPolicy

file_system_storage_path_source.proto:11

A policy that dictates which version(s) of a servable should be served.

Used in: ServableToMonitor, ModelConfig

message FileSystemStoragePathSourceConfig.ServableVersionPolicy.All

file_system_storage_path_source.proto:22

Serve all versions found on disk.

Used in: ServableVersionPolicy

(message has no fields)

message FileSystemStoragePathSourceConfig.ServableVersionPolicy.Latest

file_system_storage_path_source.proto:16

Serve the latest versions (i.e. the ones with the highest version numbers), among those found on disk. This is the default policy, with the default number of versions as 1.

Used in: ServableVersionPolicy

message FileSystemStoragePathSourceConfig.ServableVersionPolicy.Specific

file_system_storage_path_source.proto:30

Serve a specific version (or set of versions). This policy is useful for rolling back to a specific version, or for canarying a specific version while still serving a separate stable version.

Used in: ServableVersionPolicy

message FunctionDef

function.proto:24

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 FunctionDefLibrary

function.proto:13

A library is a set of named functions.

Used in: GraphDef

message GradientDef

function.proto:98

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:13

Represents the graph of operations

Used in: MetaGraphDef, RunMetadata

message LogCollectorConfig

log_collector_config.proto:8

Used in: LoggingConfig

message LogMetadata

logging.proto:12

Metadata logged along with the request logs.

message LoggingConfig

logging_config.proto:17

Configuration for logging query/responses.

Used in: ModelConfig

message MemoryStats

step_stats.proto:41

For memory tracking.

Used in: NodeExecStats

message MetaGraphDef

meta_graph.proto:30

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

Used in: SavedModel

message MetaGraphDef.MetaInfoDef

meta_graph.proto:33

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 ModelConfig

model_server_config.proto:21

Common configuration for loading a model being served.

Used in: ModelConfigList

message ModelConfigList

model_server_config.proto:72

Static list of models to be loaded for serving.

Used in: ModelServerConfig

message ModelServerConfig

model_server_config.proto:77

ModelServer config.

Used in: serving.ReloadConfigRequest

enum ModelType

model_server_config.proto:14

The type of model. TODO(b/31336131): DEPRECATED.

Used in: ModelConfig

message MonitoringConfig

monitoring_config.proto:19

Configuration for monitoring.

message NameAttrList

attr_value.proto:59

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 NamedTensorProto

named_tensor.proto:11

A pair of tensor name and tensor values.

Used in: SessionBundleConfig, serving.SessionRunRequest, serving.SessionRunResponse

message NodeDef

node_def.proto:10

Used in: FunctionDef, GraphDef

message NodeExecStats

step_stats.proto:52

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

Used in: DeviceStepStats

message NodeOutput

step_stats.proto:35

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

Used in: NodeExecStats

message OpDef

op_def.proto:14

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:20

For describing inputs and outputs.

Used in: OpDef

message OpDef.AttrDef

op_def.proto:59

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:154

Information about version-dependent deprecation of an op

Used in: OpDef

message OpList

op_def.proto:163

A collection of OpDefs

Used in: MetaGraphDef.MetaInfoDef

message PlatformConfig

platform_config.proto:11

Configuration for a servable platform e.g. tensorflow or other ML systems.

Used in: PlatformConfigMap

message PlatformConfigMap

platform_config.proto:17

message PrometheusConfig

monitoring_config.proto:9

Configuration for Prometheus monitoring.

Used in: MonitoringConfig

message Resource

resources.proto:17

One kind of resource on one device (or type of device).

Used in: ResourceAllocation.Entry

message ResourceAllocation

resources.proto:41

An allocation of one or more kinds of resources, along with the quantity of each. Used to denote the resources that a servable (or collection of servables) will use or is currently using. Also used to denote resources available to the serving system for loading more servables.

message ResourceAllocation.Entry

resources.proto:44

A collection of resources, each with a quantity. Treated as a resource-> quantity map, i.e. no resource can repeat and the order is immaterial.

Used in: ResourceAllocation

message ResourceHandleProto

resource_handle.proto:12

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 RunMetadata

config.proto:68

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

Used in: serving.SessionRunResponse

message RunOptions

config.proto:15

Options for a single Run() call.

Used in: serving.SessionRunRequest

message RunOptions.Experimental

config.proto:54

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

enum RunOptions.TraceLevel

config.proto:18

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

Used in: RunOptions

message SamplingConfig

logging_config.proto:10

Used in: LogMetadata, LoggingConfig

message SavedModel

saved_model.proto:12

SavedModel is the high level serialization format for TensorFlow Models. See [todo: doc links, similar to session_bundle] for more information.

message SavedModelBundleSourceAdapterConfig

saved_model_bundle_source_adapter.proto:11

Config proto for SavedModelBundleSourceAdapter.

message SaverDef

saver.proto:11

Protocol buffer representing the configuration of a Saver.

Used in: MetaGraphDef

enum SaverDef.CheckpointFormatVersion

saver.proto:38

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 SessionBundleConfig

session_bundle_config.proto:13

Configuration parameters for a SessionBundle, with optional batching.

Used in: SavedModelBundleSourceAdapterConfig, SessionBundleSourceAdapterConfig

message SessionBundleSourceAdapterConfig

session_bundle_source_adapter.proto:11

Config proto for SessionBundleSourceAdapter.

message SignatureDef

meta_graph.proto:295

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:81

Used in: RunMetadata

message TensorDescription

tensor_description.proto:12

Used in: NodeOutput

message TensorInfo

meta_graph.proto:207

Information about a Tensor necessary for feeding or retrieval.

Used in: AssetFileDef, SignatureDef

message TensorInfo.CooSparse

meta_graph.proto:210

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

Used in: TensorInfo

message TensorProto

tensor.proto:13

Protocol buffer representing a tensor.

Used in: AttrValue, AttrValue.ListValue, NamedTensorProto, VariantTensorDataProto

message TensorShapeProto

tensor_shape.proto:11

Dimensions of a tensor.

Used in: AttrValue, AttrValue.ListValue, CostGraphDef.Node.OutputInfo, TensorDescription, TensorInfo, TensorProto, serving.Instance

message TensorShapeProto.Dim

tensor_shape.proto:13

One dimension of the tensor.

Used in: TensorShapeProto

message VariantTensorDataProto

tensor.proto:86

Protocol buffer representing the serialization format of DT_VARIANT tensors.

Used in: TensorProto

message VersionDef

versions.proto:22

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