GraphDebugInfoOrBuilder

interfaccia pubblica GraphDebugInfoOrBuilder

Sottoclassi indirette conosciute GraphDebugInfo , GraphDebugInfo.Builder GraphDebugInfo Tipo di protocollo tensorflow.GraphDebugInfo GraphDebugInfo.Builder Tipo di protocollo tensorflow.GraphDebugInfo

Metodi pubblici

booleano astratto	contieneTracce (chiave String) This maps a node name to a stack trace in the source code.
stringa astratta	getFiles (indice int) This stores all the source code file names and can be indexed by the `file_index`.
astratto com.google.protobuf.ByteString	getFilesBytes (indice int) This stores all the source code file names and can be indexed by the `file_index`.
astratto int	getFilesCount () This stores all the source code file names and can be indexed by the `file_index`.
Elenco astratto<String>	getFilesList () This stores all the source code file names and can be indexed by the `file_index`.
Mappa astratta <String, GraphDebugInfo.StackTrace >	getTracce () Utilizzare invece getTracesMap() .
astratto int	getTracesCount () This maps a node name to a stack trace in the source code.
Mappa astratta <String, GraphDebugInfo.StackTrace >	getTracesMap () This maps a node name to a stack trace in the source code.
astratto GraphDebugInfo.StackTrace	getTracesOrDefault (chiave stringa, GraphDebugInfo.StackTrace defaultValue) This maps a node name to a stack trace in the source code.
astratto GraphDebugInfo.StackTrace	getTracesOrThrow (chiave String) This maps a node name to a stack trace in the source code.

Metodi pubblici

booleano astratto pubblico contieneTraces (chiave String)

 This maps a node name to a stack trace in the source code.
 The map key is a mangling of the containing function and op name with
 syntax:
   op.name '@' func_name
 For ops in the top-level graph, the func_name is the empty string.
 Note that op names are restricted to a small number of characters which
 exclude '@', making it impossible to collide keys of this form. Function
 names accept a much wider set of characters.
 It would be preferable to avoid mangling and use a tuple key of (op.name,
 func_name), but this is not supported with protocol buffers.
 

map<string, .tensorflow.GraphDebugInfo.StackTrace> traces = 2;

public abstract String getFiles (indice int)

 This stores all the source code file names and can be indexed by the
 `file_index`.
 

repeated string files = 1;

abstract pubblico com.google.protobuf.ByteString getFilesBytes (indice int)

 This stores all the source code file names and can be indexed by the
 `file_index`.
 

repeated string files = 1;

public abstract int getFilesCount ()

 This stores all the source code file names and can be indexed by the
 `file_index`.
 

repeated string files = 1;

lista astratta pubblica<String> getFilesList ()

 This stores all the source code file names and can be indexed by the
 `file_index`.
 

repeated string files = 1;

public abstract Map<String, GraphDebugInfo.StackTrace > getTraces ()

Utilizzare invece getTracesMap() .

public abstract int getTracesCount ()

 This maps a node name to a stack trace in the source code.
 The map key is a mangling of the containing function and op name with
 syntax:
   op.name '@' func_name
 For ops in the top-level graph, the func_name is the empty string.
 Note that op names are restricted to a small number of characters which
 exclude '@', making it impossible to collide keys of this form. Function
 names accept a much wider set of characters.
 It would be preferable to avoid mangling and use a tuple key of (op.name,
 func_name), but this is not supported with protocol buffers.
 

map<string, .tensorflow.GraphDebugInfo.StackTrace> traces = 2;

public abstract Map<String, GraphDebugInfo.StackTrace > getTracesMap ()

 This maps a node name to a stack trace in the source code.
 The map key is a mangling of the containing function and op name with
 syntax:
   op.name '@' func_name
 For ops in the top-level graph, the func_name is the empty string.
 Note that op names are restricted to a small number of characters which
 exclude '@', making it impossible to collide keys of this form. Function
 names accept a much wider set of characters.
 It would be preferable to avoid mangling and use a tuple key of (op.name,
 func_name), but this is not supported with protocol buffers.
 

map<string, .tensorflow.GraphDebugInfo.StackTrace> traces = 2;

public abstract GraphDebugInfo.StackTrace getTracesOrDefault (chiave stringa, GraphDebugInfo.StackTrace defaultValue)

 This maps a node name to a stack trace in the source code.
 The map key is a mangling of the containing function and op name with
 syntax:
   op.name '@' func_name
 For ops in the top-level graph, the func_name is the empty string.
 Note that op names are restricted to a small number of characters which
 exclude '@', making it impossible to collide keys of this form. Function
 names accept a much wider set of characters.
 It would be preferable to avoid mangling and use a tuple key of (op.name,
 func_name), but this is not supported with protocol buffers.
 

map<string, .tensorflow.GraphDebugInfo.StackTrace> traces = 2;

public abstract GraphDebugInfo.StackTrace getTracesOrThrow (chiave String)

 This maps a node name to a stack trace in the source code.
 The map key is a mangling of the containing function and op name with
 syntax:
   op.name '@' func_name
 For ops in the top-level graph, the func_name is the empty string.
 Note that op names are restricted to a small number of characters which
 exclude '@', making it impossible to collide keys of this form. Function
 names accept a much wider set of characters.
 It would be preferable to avoid mangling and use a tuple key of (op.name,
 func_name), but this is not supported with protocol buffers.
 

map<string, .tensorflow.GraphDebugInfo.StackTrace> traces = 2;