GraphDebugInfoOrBuilder

interfaz pública GraphDebugInfoOrBuilder

Subclases indirectas conocidas

Métodos públicos

booleano abstracto	contieneTraces (clave de cadena) This maps a node name to a stack trace in the source code.
cadena abstracta	getFiles (índice int) This stores all the source code file names and can be indexed by the `file_index`.
resumen com.google.protobuf.ByteString	getFilesBytes (índice int) This stores all the source code file names and can be indexed by the `file_index`.
resumen entero	getFilesCount () This stores all the source code file names and can be indexed by the `file_index`.
Lista abstracta<Cadena>	obtener lista de archivos () This stores all the source code file names and can be indexed by the `file_index`.
Mapa abstracto<Cadena, GraphDebugInfo.StackTrace >	obtenerTrazas () Utilice `getTracesMap()` en su lugar.
resumen entero	getTracesCount () This maps a node name to a stack trace in the source code.
Mapa abstracto<Cadena, GraphDebugInfo.StackTrace >	obtenerTracesMap () This maps a node name to a stack trace in the source code.
resumen GraphDebugInfo.StackTrace	getTracesOrDefault (clave de cadena, GraphDebugInfo.StackTrace defaultValue) This maps a node name to a stack trace in the source code.
resumen GraphDebugInfo.StackTrace	getTracesOrThrow (clave de cadena) This maps a node name to a stack trace in the source code.

Métodos públicos

booleano abstracto público contieneTraces (clave de cadena)

 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;

Cadena abstracta pública getFiles (índice int)

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

repeated string files = 1;

resumen público com.google.protobuf.ByteString getFilesBytes (índice int)

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

repeated string files = 1;

resumen público int getFilesCount ()

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

repeated string files = 1;

Lista abstracta pública<Cadena> getFilesList ()

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

repeated string files = 1;

Mapa abstracto público<Cadena, GraphDebugInfo.StackTrace > getTraces ()

Utilice getTracesMap() en su lugar.

resumen público 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;

Mapa abstracto público<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;

resumen público GraphDebugInfo.StackTrace getTracesOrDefault (clave de cadena, 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;

resumen público GraphDebugInfo.StackTrace getTracesOrThrow (clave de cadena)

 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;