GraphDebugInfoOrBuilder

interfejs publiczny GraphDebugInfoOrBuilder

Znane podklasy pośrednie

Metody publiczne

abstrakcyjna wartość logiczna	zawieraTraces (klucz ciąg) This maps a node name to a stack trace in the source code.
abstrakcyjny ciąg	getFiles (indeks int) This stores all the source code file names and can be indexed by the `file_index`.
streszczenie com.google.protobuf.ByteString	getFilesBytes (indeks int) This stores all the source code file names and can be indexed by the `file_index`.
streszczenie wew	getFilesCount () This stores all the source code file names and can be indexed by the `file_index`.
lista abstrakcyjna<String>	getFilesList () This stores all the source code file names and can be indexed by the `file_index`.
streszczenie Mapa<String, GraphDebugInfo.StackTrace >	pobierzTraces () Zamiast tego użyj `getTracesMap()` .
streszczenie wew	getTracesCount () This maps a node name to a stack trace in the source code.
streszczenie Mapa<String, GraphDebugInfo.StackTrace >	getTracesMap () This maps a node name to a stack trace in the source code.
streszczenie GraphDebugInfo.StackTrace	getTracesOrDefault (klucz ciągu, GraphDebugInfo.StackTrace wartość domyślna) This maps a node name to a stack trace in the source code.
streszczenie GraphDebugInfo.StackTrace	getTracesOrThrow (klawisz ciągu) This maps a node name to a stack trace in the source code.

Metody publiczne

publiczna wartość logiczna abstrakcyjna zawieraTraces (klucz ciąg)

 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 streszczenie String getFiles (indeks int)

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

repeated string files = 1;

publiczna abstrakcja com.google.protobuf.ByteString getFilesBytes (indeks int)

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

repeated string files = 1;

publiczne streszczenie int getFilesCount ()

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

repeated string files = 1;

publiczna lista abstrakcyjna<String> getFilesList ()

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

repeated string files = 1;

publiczne streszczenie Map<String, GraphDebugInfo.StackTrace > getTraces ()

Zamiast tego użyj getTracesMap() .

publiczne streszczenie 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;

publiczne streszczenie 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;

publiczne streszczenie GraphDebugInfo.StackTrace getTracesOrDefault (klucz łańcuchowy, wartość domyślna GraphDebugInfo.StackTrace )

 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;

publiczne streszczenie GraphDebugInfo.StackTrace getTracesOrThrow (klucz ciąg)

 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;