NodeDef.Builder

 Each input is "node:src_output" with "node" being a string name and
 "src_output" indicating which output tensor to use from "node". If
 "src_output" is 0 the ":0" suffix can be omitted.  Regular inputs
 may optionally be followed by control inputs that have the format
 "^node".
 

 Each input is "node:src_output" with "node" being a string name and
 "src_output" indicating which output tensor to use from "node". If
 "src_output" is 0 the ":0" suffix can be omitted.  Regular inputs
 may optionally be followed by control inputs that have the format
 "^node".
 

 Each input is "node:src_output" with "node" being a string name and
 "src_output" indicating which output tensor to use from "node". If
 "src_output" is 0 the ":0" suffix can be omitted.  Regular inputs
 may optionally be followed by control inputs that have the format
 "^node".
 

thiết bị chuỗi

 A (possibly partial) specification for the device on which this
 node should be placed.
 The expected syntax for this string is as follows:
 DEVICE_SPEC ::= PARTIAL_SPEC
 PARTIAL_SPEC ::= ("/" CONSTRAINT) *
 CONSTRAINT ::= ("job:" JOB_NAME)
              | ("replica:" [1-9][0-9]*)
              | ("task:" [1-9][0-9]*)
              | ("device:" [A-Za-z]* ":" ([1-9][0-9]* | "*") )
 Valid values for this string include:
 * "/job:worker/replica:0/task:1/device:GPU:3"  (full specification)
 * "/job:worker/device:GPU:3"                   (partial specification)
 * ""                                    (no specification)
 If the constraints do not resolve to a single device (or if this
 field is empty or not present), the runtime will attempt to
 choose a device automatically.
 

 This stores debug information associated with the node.
 

 Each input is "node:src_output" with "node" being a string name and
 "src_output" indicating which output tensor to use from "node". If
 "src_output" is 0 the ":0" suffix can be omitted.  Regular inputs
 may optionally be followed by control inputs that have the format
 "^node".
 

string name = 1;

 The name given to this operator. Used for naming inputs,
 logging, visualization, etc.  Unique within a single GraphDef.
 Must match the regexp "[A-Za-z0-9.][A-Za-z0-9_>./]*".
 

chuỗi

 The operation name.  There may be custom parameters in attrs.
 Op names starting with an underscore are reserved for internal use.
 

 Operation-specific graph-construction-time configuration.
 Note that this should include all attrs defined in the
 corresponding OpDef, including those with a value matching
 the default -- this allows the default to change and makes
 NodeDefs easier to interpret on their own.  However, if
 an attr with a default is not specified in this list, the
 default will be used.
 The "names" (keys) must match the regexp "[a-z][a-z0-9_]+" (and
 one of the names from the corresponding OpDef's attr field).
 The values must have a type matching the corresponding OpDef
 attr's type field.
 TODO(josh11b): Add some examples here showing best practices.
 

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

 Operation-specific graph-construction-time configuration.
 Note that this should include all attrs defined in the
 corresponding OpDef, including those with a value matching
 the default -- this allows the default to change and makes
 NodeDefs easier to interpret on their own.  However, if
 an attr with a default is not specified in this list, the
 default will be used.
 The "names" (keys) must match the regexp "[a-z][a-z0-9_]+" (and
 one of the names from the corresponding OpDef's attr field).
 The values must have a type matching the corresponding OpDef
 attr's type field.
 TODO(josh11b): Add some examples here showing best practices.
 

 Operation-specific graph-construction-time configuration.
 Note that this should include all attrs defined in the
 corresponding OpDef, including those with a value matching
 the default -- this allows the default to change and makes
 NodeDefs easier to interpret on their own.  However, if
 an attr with a default is not specified in this list, the
 default will be used.
 The "names" (keys) must match the regexp "[a-z][a-z0-9_]+" (and
 one of the names from the corresponding OpDef's attr field).
 The values must have a type matching the corresponding OpDef
 attr's type field.
 TODO(josh11b): Add some examples here showing best practices.
 

 Operation-specific graph-construction-time configuration.
 Note that this should include all attrs defined in the
 corresponding OpDef, including those with a value matching
 the default -- this allows the default to change and makes
 NodeDefs easier to interpret on their own.  However, if
 an attr with a default is not specified in this list, the
 default will be used.
 The "names" (keys) must match the regexp "[a-z][a-z0-9_]+" (and
 one of the names from the corresponding OpDef's attr field).
 The values must have a type matching the corresponding OpDef
 attr's type field.
 TODO(josh11b): Add some examples here showing best practices.
 

 Operation-specific graph-construction-time configuration.
 Note that this should include all attrs defined in the
 corresponding OpDef, including those with a value matching
 the default -- this allows the default to change and makes
 NodeDefs easier to interpret on their own.  However, if
 an attr with a default is not specified in this list, the
 default will be used.
 The "names" (keys) must match the regexp "[a-z][a-z0-9_]+" (and
 one of the names from the corresponding OpDef's attr field).
 The values must have a type matching the corresponding OpDef
 attr's type field.
 TODO(josh11b): Add some examples here showing best practices.
 

thiết bị chuỗi

 A (possibly partial) specification for the device on which this
 node should be placed.
 The expected syntax for this string is as follows:
 DEVICE_SPEC ::= PARTIAL_SPEC
 PARTIAL_SPEC ::= ("/" CONSTRAINT) *
 CONSTRAINT ::= ("job:" JOB_NAME)
              | ("replica:" [1-9][0-9]*)
              | ("task:" [1-9][0-9]*)
              | ("device:" [A-Za-z]* ":" ([1-9][0-9]* | "*") )
 Valid values for this string include:
 * "/job:worker/replica:0/task:1/device:GPU:3"  (full specification)
 * "/job:worker/device:GPU:3"                   (partial specification)
 * ""                                    (no specification)
 If the constraints do not resolve to a single device (or if this
 field is empty or not present), the runtime will attempt to
 choose a device automatically.
 

thiết bị chuỗi

 A (possibly partial) specification for the device on which this
 node should be placed.
 The expected syntax for this string is as follows:
 DEVICE_SPEC ::= PARTIAL_SPEC
 PARTIAL_SPEC ::= ("/" CONSTRAINT) *
 CONSTRAINT ::= ("job:" JOB_NAME)
              | ("replica:" [1-9][0-9]*)
              | ("task:" [1-9][0-9]*)
              | ("device:" [A-Za-z]* ":" ([1-9][0-9]* | "*") )
 Valid values for this string include:
 * "/job:worker/replica:0/task:1/device:GPU:3"  (full specification)
 * "/job:worker/device:GPU:3"                   (partial specification)
 * ""                                    (no specification)
 If the constraints do not resolve to a single device (or if this
 field is empty or not present), the runtime will attempt to
 choose a device automatically.
 

 This stores debug information associated with the node.
 

 This stores debug information associated with the node.
 

 This stores debug information associated with the node.
 

 Each input is "node:src_output" with "node" being a string name and
 "src_output" indicating which output tensor to use from "node". If
 "src_output" is 0 the ":0" suffix can be omitted.  Regular inputs
 may optionally be followed by control inputs that have the format
 "^node".
 

 Each input is "node:src_output" with "node" being a string name and
 "src_output" indicating which output tensor to use from "node". If
 "src_output" is 0 the ":0" suffix can be omitted.  Regular inputs
 may optionally be followed by control inputs that have the format
 "^node".
 

 Each input is "node:src_output" with "node" being a string name and
 "src_output" indicating which output tensor to use from "node". If
 "src_output" is 0 the ":0" suffix can be omitted.  Regular inputs
 may optionally be followed by control inputs that have the format
 "^node".
 

 Each input is "node:src_output" with "node" being a string name and
 "src_output" indicating which output tensor to use from "node". If
 "src_output" is 0 the ":0" suffix can be omitted.  Regular inputs
 may optionally be followed by control inputs that have the format
 "^node".
 

Thay vào đó hãy sử dụng các bộ truy cập đột biến thay thế.

string name = 1;

 The name given to this operator. Used for naming inputs,
 logging, visualization, etc.  Unique within a single GraphDef.
 Must match the regexp "[A-Za-z0-9.][A-Za-z0-9_>./]*".
 

string name = 1;

 The name given to this operator. Used for naming inputs,
 logging, visualization, etc.  Unique within a single GraphDef.
 Must match the regexp "[A-Za-z0-9.][A-Za-z0-9_>./]*".
 

 The operation name.  There may be custom parameters in attrs.
 Op names starting with an underscore are reserved for internal use.
 

chuỗi

 The operation name.  There may be custom parameters in attrs.
 Op names starting with an underscore are reserved for internal use.
 

 This stores debug information associated with the node.
 

 This stores debug information associated with the node.
 

 Operation-specific graph-construction-time configuration.
 Note that this should include all attrs defined in the
 corresponding OpDef, including those with a value matching
 the default -- this allows the default to change and makes
 NodeDefs easier to interpret on their own.  However, if
 an attr with a default is not specified in this list, the
 default will be used.
 The "names" (keys) must match the regexp "[a-z][a-z0-9_]+" (and
 one of the names from the corresponding OpDef's attr field).
 The values must have a type matching the corresponding OpDef
 attr's type field.
 TODO(josh11b): Add some examples here showing best practices.
 

 Operation-specific graph-construction-time configuration.
 Note that this should include all attrs defined in the
 corresponding OpDef, including those with a value matching
 the default -- this allows the default to change and makes
 NodeDefs easier to interpret on their own.  However, if
 an attr with a default is not specified in this list, the
 default will be used.
 The "names" (keys) must match the regexp "[a-z][a-z0-9_]+" (and
 one of the names from the corresponding OpDef's attr field).
 The values must have a type matching the corresponding OpDef
 attr's type field.
 TODO(josh11b): Add some examples here showing best practices.
 

 Operation-specific graph-construction-time configuration.
 Note that this should include all attrs defined in the
 corresponding OpDef, including those with a value matching
 the default -- this allows the default to change and makes
 NodeDefs easier to interpret on their own.  However, if
 an attr with a default is not specified in this list, the
 default will be used.
 The "names" (keys) must match the regexp "[a-z][a-z0-9_]+" (and
 one of the names from the corresponding OpDef's attr field).
 The values must have a type matching the corresponding OpDef
 attr's type field.
 TODO(josh11b): Add some examples here showing best practices.
 

thiết bị chuỗi

 A (possibly partial) specification for the device on which this
 node should be placed.
 The expected syntax for this string is as follows:
 DEVICE_SPEC ::= PARTIAL_SPEC
 PARTIAL_SPEC ::= ("/" CONSTRAINT) *
 CONSTRAINT ::= ("job:" JOB_NAME)
              | ("replica:" [1-9][0-9]*)
              | ("task:" [1-9][0-9]*)
              | ("device:" [A-Za-z]* ":" ([1-9][0-9]* | "*") )
 Valid values for this string include:
 * "/job:worker/replica:0/task:1/device:GPU:3"  (full specification)
 * "/job:worker/device:GPU:3"                   (partial specification)
 * ""                                    (no specification)
 If the constraints do not resolve to a single device (or if this
 field is empty or not present), the runtime will attempt to
 choose a device automatically.
 

thiết bị chuỗi

 A (possibly partial) specification for the device on which this
 node should be placed.
 The expected syntax for this string is as follows:
 DEVICE_SPEC ::= PARTIAL_SPEC
 PARTIAL_SPEC ::= ("/" CONSTRAINT) *
 CONSTRAINT ::= ("job:" JOB_NAME)
              | ("replica:" [1-9][0-9]*)
              | ("task:" [1-9][0-9]*)
              | ("device:" [A-Za-z]* ":" ([1-9][0-9]* | "*") )
 Valid values for this string include:
 * "/job:worker/replica:0/task:1/device:GPU:3"  (full specification)
 * "/job:worker/device:GPU:3"                   (partial specification)
 * ""                                    (no specification)
 If the constraints do not resolve to a single device (or if this
 field is empty or not present), the runtime will attempt to
 choose a device automatically.
 

 This stores debug information associated with the node.
 

 This stores debug information associated with the node.
 

 Each input is "node:src_output" with "node" being a string name and
 "src_output" indicating which output tensor to use from "node". If
 "src_output" is 0 the ":0" suffix can be omitted.  Regular inputs
 may optionally be followed by control inputs that have the format
 "^node".
 

string name = 1;

 The name given to this operator. Used for naming inputs,
 logging, visualization, etc.  Unique within a single GraphDef.
 Must match the regexp "[A-Za-z0-9.][A-Za-z0-9_>./]*".
 

string name = 1;

 The name given to this operator. Used for naming inputs,
 logging, visualization, etc.  Unique within a single GraphDef.
 Must match the regexp "[A-Za-z0-9.][A-Za-z0-9_>./]*".
 

 The operation name.  There may be custom parameters in attrs.
 Op names starting with an underscore are reserved for internal use.
 

 The operation name.  There may be custom parameters in attrs.
 Op names starting with an underscore are reserved for internal use.