GraphDebugInfoOrBuilder

공용 인터페이스 GraphDebugInfoOrBuilder

알려진 간접 하위 클래스

공개 방법

추상 부울	containTraces (문자열 키) 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`.
추상 정수	getFilesCount () This stores all the source code file names and can be indexed by the `file_index`.
추상 목록<문자열>	getFilesList () This stores all the source code file names and can be indexed by the `file_index`.
추상 맵<String, GraphDebugInfo.StackTrace >	getTrace () 대신 `getTracesMap()` 사용하세요.
추상 정수	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.

공개 방법

공개 추상 부울 containTraces (문자열 키)

 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;

공개 추상 List<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;