alteryx / alteryx/evalml

Update label encoder in pipeline implementation to look for LabelEncoder class instead of looking for "Label Encoder"

Abierto
#2,906 1 comentario 1 reacción 1 asignado Reclamado por @asniyaz Ver en GitHub
enhancement needs design tech debt
Lenguaje dominante
Python
Estrellas
850
Forks
96
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

https://github.com/alteryx/evalml/pull/2821/ introduces the label encoder as a component in the pipeline, rather than an attribute. However, we still set a pipeline's `_encoder` attribute to a label encoder in the pipeline, if it's available.

As documented in [this comment](https://github.com/alteryx/evalml/pull/2821/files#r723692569), there is an assumption that the Label Encoder component has a name "Label Encoder". However, we should be more flexible and accept the label encoder even if its name was "my cool label encoder".

One suggestion is to find the component by checking for the component class instead. This work would be made much easier by https://github.com/alteryx/evalml/issues/2878.

One edge case that may be important to think about the case where there may be multiple label encoders. What do we do then?

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.