alteryx / alteryx/evalml

Standardize how we access unique target values for classification problems

Aperta
#3,112 2 commenti 0 reazioni 1 assegnatario Rivendicata da @asniyaz Vedi su GitHub
refactor tech debt
Lingua principale
Python
Stelle
850
Fork
96
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

Right now, we access unique target values for classification problems in several ways:
1. `list(ww.init_series(np.unique(y)))` (`classification_pipeline.py`)
2. `unique_labels` (`confusion_matrix`)
3. LabelBinarizer / np.unique in `roc_curve` (slightly different than label encoding)

It could be helpful to standardize how we encode and decode targets pre and post fit time. This issue tracks finding places where we encode/decode and seeing how we could standardize this process.

Note that in some cases, we might encode/decode outside of the context of a pipeline (such as confusion_matrix), but it could still be helpful to consolidate our implementation to fewer methods if possible!

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.