alteryx / alteryx/evalml

Explore Target Encoder vs OHE usage scenarios

Open
#1,440 0 comments 0 reactions 1 assignee Claimed by @asniyaz View on GitHub
enhancement needs design spike
Dominant language
Python
Stars
850
Forks
96
PR merge metrics
No merged PRs in 30d

Description

As raised in discussion with @dsherry @freddyaboulton and @rpeck, we want to explore the possibility of creating a `top_n` parameter for Target Encoder and grouping objects outside of this number together into one group, [here](https://github.com/alteryx/evalml/pull/1401#discussion_r523236206). Additionally, we wanted to explore if there were a number of categoricals or a distribution of categoricals where it would be more beneficial to use Target Encoder versus One Hot Encoder. This would be useful in order to add Target Encoder to `AutoMLSearch`.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.