GraphDebugInfoOrBuilder

общедоступный интерфейс GraphDebugInfoOrBuilder
Известные косвенные подклассы

Публичные методы

абстрактное логическое значение
содержитTraces (строковый ключ) 
 This maps a node name to a stack trace in the source code.
абстрактная строка
getFiles (целевой индекс) 
 This stores all the source code file names and can be indexed by the
 `file_index`.
абстрактный com.google.protobuf.ByteString
getFilesBytes (индекс целого числа) 
 This stores all the source code file names and can be indexed by the
 `file_index`.
абстрактный int
getFilesCount () 
 This stores all the source code file names and can be indexed by the
 `file_index`.
абстрактный список<String>
получить список файлов () 
 This stores all the source code file names and can be indexed by the
 `file_index`.
абстрактная карта<String, GraphDebugInfo.StackTrace >
получитьТрассы ()
Вместо этого используйте getTracesMap() .
абстрактный int
getTracesCount () 
 This maps a node name to a stack trace in the source code.
абстрактная карта<String, GraphDebugInfo.StackTrace >
getTracesMap () 
 This maps a node name to a stack trace in the source code.
абстрактный GraphDebugInfo.StackTrace
getTracesOrDefault (строковый ключ, GraphDebugInfo.StackTrace defaultValue) 
 This maps a node name to a stack trace in the source code.
абстрактный GraphDebugInfo.StackTrace
getTracesOrThrow (строковый ключ) 
 This maps a node name to a stack trace in the source code.

Публичные методы

общедоступное абстрактное логическое значение containsTraces (строковый ключ) 

 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;

общедоступная абстрактная строка getFiles (индекс int) 

 This stores all the source code file names and can be indexed by the
 `file_index`.
repeated string files = 1;

общедоступный абстрактный com.google.protobuf.ByteString getFilesBytes (индекс int) 

 This stores all the source code file names and can be indexed by the
 `file_index`.
repeated string files = 1;

публичный абстрактный int getFilesCount () 

 This stores all the source code file names and can be indexed by the
 `file_index`.
repeated string files = 1;

общедоступный абстрактный список <String> getFilesList () 

 This stores all the source code file names and can be indexed by the
 `file_index`.
repeated string files = 1;

общедоступная абстрактная Map<String, GraphDebugInfo.StackTrace > getTraces ()

Вместо этого используйте getTracesMap() .

публичный абстрактный 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;

общедоступная абстрактная 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;

общедоступный абстрактный GraphDebugInfo.StackTrace getTracesOrDefault (строковый ключ, 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;

общедоступный абстрактный GraphDebugInfo.StackTrace getTracesOrThrow (строковый ключ) 

 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;