-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update evalml docs to mention woodwork #1361
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1361 +/- ##
=======================================
Coverage 99.95% 99.95%
=======================================
Files 213 213
Lines 13857 13857
=======================================
Hits 13850 13850
Misses 7 7 Continue to review full report at Codecov.
|
81f1509
to
d808f17
Compare
Docs visible here for the start page |
d808f17
to
6ccea4d
Compare
docs/source/start.ipynb
Outdated
"execution_count": null, | ||
"metadata": {}, | ||
"outputs": [], | ||
"source": [] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oops, will delete this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm!
docs/source/start.ipynb
Outdated
"source": [ | ||
"To provide data to EvalML, it is recommended that you create a `DataTable` object using [the woodwork project](https://woodwork.alteryx.com/en/stable/).\n", | ||
"\n", | ||
"EvalML also accepts and works well with pandas `DataFrames`. But using the `DataTable` makes it easy to control how EvalML will treat each feature, as a numeric feature, a categorical feature, a text feature or other type of feature. Woodwork `DataTable`s include features like inferring when a categorical feature should be treated as a text feature. For this reason, if you don't provide woodwork objects, EvalML will raise a warning." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"EvalML also accepts and works well with pandas `DataFrames`. But using the `DataTable` makes it easy to control how EvalML will treat each feature, as a numeric feature, a categorical feature, a text feature or other type of feature. Woodwork `DataTable`s include features like inferring when a categorical feature should be treated as a text feature. For this reason, if you don't provide woodwork objects, EvalML will raise a warning." | |
"EvalML also accepts and works well with pandas `DataFrames`. But using the `DataTable` makes it easy to control how EvalML will treat each feature, as a numeric feature, a categorical feature, a text feature or other type of feature. Woodwork's DataTable includes features like inferring when a categorical feature should be treated as a natural language feature. For this reason, if you don't provide woodwork objects, EvalML will raise a warning." |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@gsheni ah right. I think we're gonna stick with "text" in evalml for the time being. Some of our classes use "text". We can have a separate conversation about that if you'd like.
I'll add in your other suggestion.
Thanks!
faecf06
to
6d87a54
Compare
@dsherry Formating |
Fix #1287
Adds a mention and example to the start page and to the automl user guide page about woodwork.
This is just to start us off. Eventually I'd like us to add a page or section to the automl guide about "formatting data for automl", which shows how to set the column types using woodwork, override some of the default inference and run automl with those settings.