Fix indentation in tensorflow SignatureDef proto comment to avoid confusion. The method_name should be on the same level of inputs/outputs.
PiperOrigin-RevId: 353781944 Change-Id: I26d593c34b1877c600659588992c632011967353
This commit is contained in:
parent
eadb3c0bec
commit
953dea002e
@ -261,7 +261,7 @@ message TensorInfo {
|
||||
// graph.
|
||||
//
|
||||
// For example, a model with two loss computations, sharing a single input,
|
||||
// might have the following signature_def map.
|
||||
// might have the following signature_def map, in a MetaGraphDef message.
|
||||
//
|
||||
// Note that across the two SignatureDefs "loss_A" and "loss_B", the input key,
|
||||
// output key, and method_name are identical, and will be used by system(s) that
|
||||
@ -287,9 +287,9 @@ message TensorInfo {
|
||||
// tensor_shape: ...
|
||||
// }
|
||||
// }
|
||||
// method_name: "some/package/compute_loss"
|
||||
// }
|
||||
// ...
|
||||
// method_name: "some/package/compute_loss"
|
||||
// }
|
||||
// signature_def {
|
||||
// key: "loss_B"
|
||||
@ -310,9 +310,9 @@ message TensorInfo {
|
||||
// tensor_shape: ...
|
||||
// }
|
||||
// }
|
||||
// method_name: "some/package/compute_loss"
|
||||
// }
|
||||
// ...
|
||||
// method_name: "some/package/compute_loss"
|
||||
// }
|
||||
message SignatureDef {
|
||||
// Named input parameters.
|
||||
|
Loading…
Reference in New Issue
Block a user