-
Notifications
You must be signed in to change notification settings - Fork 1.3k
implement a new attribute allow_string_features
#1420
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
Conversation
…the new text preprocessing. On default it is enabled.
…the new text preprocessing. On default it is enabled.
…the new text preprocessing. On default it is enabled.
Codecov Report
@@ Coverage Diff @@
## development #1420 +/- ##
===============================================
+ Coverage 84.50% 84.57% +0.07%
===============================================
Files 146 146
Lines 11285 11295 +10
Branches 1929 1931 +2
===============================================
+ Hits 9536 9553 +17
+ Misses 1233 1229 -4
+ Partials 516 513 -3 |
It all seems okay to me :) Do you want to do the advertisement of the feature in |
i will do this in the next PR. If every thing is okay merge it. |
implement a new attribute
allow_string_features
which en-/disables the new text preprocessing. On default it is enabled.Bascilly the AutoSklearnEstimator gets a new variable
allow_string_features
which is True on default. This new varialbe gets passed to the FeatureValidator (feature_validator.py). Here i use if/else statements which check if text features are allowed before assigning the string class. If text_preprocssing is disabledstring
andobject
are treated ascategorical
as it was handled priviously.