Deploy to GitHub Pages: 55ec0e2a

develop/doc/operators.json

@@ -3437,16 +3437,16 @@
  "attrs" : [  ] 
 },{
  "type" : "edit_distance",
- "comment" : "\n\nEditDistance operator computes the edit distances between a batch of hypothesis\nstrings and their references.\n\nEdit distance, also called Levenshtein distance, measures how dissimilar two strings \nare by counting the minimum number of operations to transform one string into anthor. \nHere the operations include insertion, deletion, and substitution. For example, \ngiven hypothesis string A = \"kitten\" and reference B = \"sitting\", the edit distance \nis 3 for A will be transformed into B at least after two substitutions and one \ninsertion:\n  \n   \"kitten\" -> \"sitten\" -> \"sittin\" -> \"sitting\"\n\nInput(Hyps) is a LoDTensor consisting of all the hypothesis strings with the total \nnumber denoted by `batch_size`, and the separation is specified by the LoD information. \nAnd the `batch_size` reference strings are arranged in order in the same way in the \nLoDTensor Input(Refs).\n\nOutput(Out) contains the `batch_size` results and each stands for the edit stance \nfor a pair of strings respectively. If Attr(normalized) is true, the edit distance \nwill be divided by the length of reference string.\n",
+ "comment" : "\n\nEditDistance operator computes the edit distances between a batch of hypothesis\nstrings and their references.\n\nEdit distance, also called Levenshtein distance, measures how dissimilar two strings\nare by counting the minimum number of operations to transform one string into anthor.\nHere the operations include insertion, deletion, and substitution. For example,\ngiven hypothesis string A = \"kitten\" and reference B = \"sitting\", the edit distance\nis 3 for A will be transformed into B at least after two substitutions and one\ninsertion:\n\n   \"kitten\" -> \"sitten\" -> \"sittin\" -> \"sitting\"\n\nInput(Hyps) is a LoDTensor consisting of all the hypothesis strings with the total\nnumber denoted by `batch_size`, and the separation is specified by the LoD information.\nAnd the `batch_size` reference strings are arranged in order in the same way in the\nLoDTensor Input(Refs).\n\nOutput(Out) contains the `batch_size` results and each stands for the edit stance\nfor a pair of strings respectively. If Attr(normalized) is true, the edit distance\nwill be divided by the length of reference string.\n",
  "inputs" : [ 
  { 
    "name" : "Hyps",
-   "comment" : "(2-D LoDTensor<int>, 2nd dim. equal to 1) The indices for hypothesis strings.",
+   "comment" : "(2-D LoDTensor<int64_t>, 2nd dim. equal to 1) The indices for hypothesis strings.",
    "duplicable" : 0,
    "intermediate" : 0
  }, { 
    "name" : "Refs",
-   "comment" : "(2-D LoDTensor<int>, 2nd dim. equal to 1) The indices for reference strings.",
+   "comment" : "(2-D LoDTensor<int64_t>, 2nd dim. equal to 1) The indices for reference strings.",
    "duplicable" : 0,
    "intermediate" : 0
  } ],