GraphDebugInfoOrBuilder

giao diện công cộng GraphDebugInfoOrBuilder

Các lớp con gián tiếp đã biết GraphDebugInfo , GraphDebugInfo.Builder Thông tin gỡ lỗi đồ thị Loại protobuf tensorflow.GraphDebugInfo GraphDebugInfo.Builder Loại protobuf tensorflow.GraphDebugInfo

Phương pháp công khai

trừu tượng boolean	chứaTraces (Khóa chuỗi) This maps a node name to a stack trace in the source code.
chuỗi trừu tượng	getFiles (chỉ mục int) This stores all the source code file names and can be indexed by the `file_index`.
trừu tượng com.google.protobuf.ByteString	getFilesBytes (chỉ mục int) This stores all the source code file names and can be indexed by the `file_index`.
int trừu tượng	getFilesCount () This stores all the source code file names and can be indexed by the `file_index`.
Danh sách trừu tượng<String>	getFilesList () This stores all the source code file names and can be indexed by the `file_index`.
Bản đồ trừu tượng<Chuỗi, GraphDebugInfo.StackTrace >	getTraces () Thay vào đó hãy sử dụng getTracesMap() .
int trừu tượng	getTraceCount () This maps a node name to a stack trace in the source code.
Bản đồ trừu tượng<Chuỗi, GraphDebugInfo.StackTrace >	getTraceMap () This maps a node name to a stack trace in the source code.
trừu tượng GraphDebugInfo.StackTrace	getTracesOrDefault (Khóa chuỗi, GraphDebugInfo.StackTrace defaultValue) This maps a node name to a stack trace in the source code.
trừu tượng GraphDebugInfo.StackTrace	getTracesOrThrow (Khóa chuỗi) This maps a node name to a stack trace in the source code.

Phương pháp công khai

boolean trừu tượng công khai chứaTraces (Khóa chuỗi)

 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;

chuỗi tóm tắt công khai getFiles (chỉ mục int)

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

repeated string files = 1;

tóm tắt công khai com.google.protobuf.ByteString getFilesBytes (chỉ mục int)

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

repeated string files = 1;

tóm tắt công khai int getFilesCount ()

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

repeated string files = 1;

Danh sách tóm tắt công khai<String> getFilesList ()

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

repeated string files = 1;

Bản đồ trừu tượng công khai<String, GraphDebugInfo.StackTrace > getTraces ()

Thay vào đó hãy sử dụng getTracesMap() .

tóm tắt công khai int getTraceCount ()

 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;

Bản đồ trừu tượng công khai<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;

tóm tắt công khai GraphDebugInfo.StackTrace getTracesOrDefault (Khóa chuỗi, 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;

tóm tắt công khai GraphDebugInfo.StackTrace getTracesOrThrow (Khóa chuỗi)

 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;