-
Notifications
You must be signed in to change notification settings - Fork 125
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
Understanding the engineered features in Autogluaon. #163
Comments
I'm not sure if autogluon creates those names, but if you look for quick-fix, you need to one-hot encode categorical variables by yourself:
with this:
where for categorical >0.5 means True, <=0.5 means False |
Thanks @mglowacki100! I agee I think one-hot encoding is the best way to go for now. That feature engineering is performed by |
Thought of that but was thinking that this would increase training time hugely. But anyways, I'll run it on limited features. |
Hi @csinva, I see you're autogluon contributor, so two additional things regarding
|
This a tricky situation, as I don't think it is possible for the categorical feature rules to display meaningful information in a low-split-count model without one-hot-encoding them, since we use label encoding where a tree model split is nearly impossible to interpret. However, you probably pay a huge performance and accuracy penalty by one-hot-encoding. @csinva in autogluon/autogluon#2981 I am moving the interpretable logic into its own class called |
Thanks, I think one-hot encoding categorical variables is a decent solution, as it should atleast preserve interpretability. |
I was using interpretrable models in autogluaon. While the model training was easier but the challenges is in understand the rules as the rules are created using engineered features and we do not have visibility on the feature engineering. For example, this was rule created when I was running on Lendclub data.
There is such value as '11' in 'emp_title'. So, how do we reverse transform the value '11' back to original data?
The text was updated successfully, but these errors were encountered: