Improve TextFeaturizer Documentation #2568
Conversation
Codecov Report
@@ Coverage Diff @@
## main #2568 +/- ##
=====================================
Coverage 99.9% 99.9%
=====================================
Files 287 287
Lines 26338 26338
=====================================
Hits 26304 26304
Misses 34 34
Continue to review full report at Codecov.
|
docs/source/demos/text_input.ipynb
Outdated
| "cell_type": "markdown", | ||
| "metadata": {}, | ||
| "source": [ | ||
| "Here, the Text Featurization component takes in a single \"Message\" column, but then the next component in the pipeline, the Imputer, recieves five columns of input, the result of featurizing the text-type \"Message\" column. Most importantly, these featurized columns are what ends up passed in to the estimator.\n", |
There was a problem hiding this comment.
recieves --> receives
Just a suggestion but maybe split this up into something like:
Here, the Text Featurization component takes in a single "Message" column, but then the next component in the pipeline, the Imputer, receives five columns of input. These five columns are the result of featurizing the text-type "Message" column.
docs/source/demos/text_input.ipynb
Outdated
| "**Diversity Score** is the ratio of unique words to total words\n", | ||
| "\n", | ||
| "**Mean Characters per Word** is the average number of letters in each word\n", | ||
| "\n", | ||
| "**Polarity Score** is a prediction of how \"polarized\" the text is, on a scale from -1 (extremely negative) to 1 (extremely positive)\n", |
There was a problem hiding this comment.
Omega nitpick: Let's add periods to the end of these!
Closes #2474
TextFeaturizerdocstring