GraphDebugInfoOrBuilder

interface publique GraphDebugInfoOrBuilder

Sous-classes indirectes connues GraphDebugInfo , GraphDebugInfo.Builder GraphDebugInfo tensorflow.GraphDebugInfo de type Protobuf.GraphDebugInfo GraphDebugInfo.Builder tensorflow.GraphDebugInfo de type Protobuf.GraphDebugInfo

Méthodes publiques

booléen abstrait	contientTraces (clé de chaîne) This maps a node name to a stack trace in the source code.
chaîne abstraite	getFiles (index entier) This stores all the source code file names and can be indexed by the `file_index`.
résumé com.google.protobuf.ByteString	getFilesBytes (index int) This stores all the source code file names and can be indexed by the `file_index`.
entier abstrait	getFilesCount () This stores all the source code file names and can be indexed by the `file_index`.
Liste abstraite<String>	getFilesList () This stores all the source code file names and can be indexed by the `file_index`.
Carte abstraite<String, GraphDebugInfo.StackTrace >	obtenirTraces () Utilisez plutôt getTracesMap() .
entier abstrait	getTracesCount () This maps a node name to a stack trace in the source code.
Carte abstraite<String, GraphDebugInfo.StackTrace >	getTracesMap () This maps a node name to a stack trace in the source code.
résumé GraphDebugInfo.StackTrace	getTracesOrDefault (clé de chaîne, GraphDebugInfo.StackTrace defaultValue) This maps a node name to a stack trace in the source code.
résumé GraphDebugInfo.StackTrace	getTracesOrThrow (clé de chaîne) This maps a node name to a stack trace in the source code.

Méthodes publiques

public abstract boolean containTraces (clé de chaîne)

 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;

chaîne abstraite publique getFiles (index int)

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

repeated string files = 1;

résumé public com.google.protobuf.ByteString getFilesBytes (index int)

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

repeated string files = 1;

public abstrait int getFilesCount ()

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

repeated string files = 1;

liste abstraite publique<String> getFilesList ()

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

repeated string files = 1;

public abstract Map<String, GraphDebugInfo.StackTrace > getTraces ()

Utilisez plutôt getTracesMap() .

public abstrait 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;

public abstract 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;

résumé public GraphDebugInfo.StackTrace getTracesOrDefault (clé de chaîne, 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;

résumé public GraphDebugInfo.StackTrace getTracesOrThrow (clé de chaîne)

 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;