interface pública GraphDebugInfoOrBuilder
| Subclasses indiretas conhecidas |
Métodos Públicos
| booleano abstrato | contémTraces (chave de string) This maps a node name to a stack trace in the source code. |
| cadeia abstrata | getFiles (índice interno) This stores all the source code file names and can be indexed by the `file_index`. |
| abstrato com.google.protobuf.ByteString | getFilesBytes (índice interno) This stores all the source code file names and can be indexed by the `file_index`. |
| abstrato int | getFilesCount () This stores all the source code file names and can be indexed by the `file_index`. |
| lista abstrata<String> | getListaArquivos () This stores all the source code file names and can be indexed by the `file_index`. |
| mapa abstrato<String, GraphDebugInfo.StackTrace > | obterTraces () Use getTracesMap() em vez disso. |
| abstrato int | getTracesCount () This maps a node name to a stack trace in the source code. |
| mapa abstrato<String, GraphDebugInfo.StackTrace > | getTracesMap () This maps a node name to a stack trace in the source code. |
| resumo GraphDebugInfo.StackTrace | getTracesOrDefault (chave de string, GraphDebugInfo.StackTrace defaultValue) This maps a node name to a stack trace in the source code. |
| resumo GraphDebugInfo.StackTrace | getTracesOrThrow (chave de string) This maps a node name to a stack trace in the source code. |
Métodos Públicos
público abstrato booleano contémTraces (chave 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; string abstrata 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; resumo 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; público abstrato int getFilesCount ()
This stores all the source code file names and can be indexed by the `file_index`.
repeated string files = 1; lista abstrata pública<String> getFilesList ()
This stores all the source code file names and can be indexed by the `file_index`.
repeated string files = 1; público abstrato Map<String, GraphDebugInfo.StackTrace > getTraces ()
Use getTracesMap() em vez disso.
público abstrato 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; público abstrato 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; resumo público GraphDebugInfo.StackTrace getTracesOrDefault (chave String, 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; resumo público GraphDebugInfo.StackTrace getTracesOrThrow (chave 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;