alteryx / alteryx/evalml

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

Aperta
#2,906 1 commento 1 reazione 1 assegnatario Rivendicata da @asniyaz Vedi su GitHub
enhancement needs design tech debt
Lingua principale
Python
Stelle
850
Fork
96
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

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?

Guida per i contributori

Apri la guida per i contributori

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.