Open calz1 opened 7 years ago
Thanks for the great bug report! Very comprehensive info, which is quite useful.
Unfortunately in this case, multiclass classification just isn't supported by feature_learning
yet. It might be as simple as modifying make_deep_learning_classifier()
to take in a param for num_output_classes=2
(defaulting to binary classification). It wouldn't be too hard to find the number of classes earlier in the process, and feed them in. I have a feeling that properly supporting multilabel classification for deep learning might be slightly more involved than that, but it might be that simple for feature_learning.
i'm first focusing on .predict_uncertainty()
and some better analytics (see https://github.com/ClimbsRocks/auto_ml/issues/218 for an idea I have to get linear-model-style interpretation from much more accurate tree-based models). but if you want to take a whack at this, i'd love to see how it goes, and will happily provide support.
@calz1 I also just updated the README to note this. It was a silent failure point before, so thanks for reminding me of this so I could make the docs clearer.
I was trying out using auto_ml to do image recognition via this dataset which is basically 64 pixels of hand-drawn images. This code works fine and generates a trained model I can score.
but if you change the last line to:
ml_predictor.train(df_train,model_names='XGBClassifier',feature_learning=True, fl_data=df_fl)
then I get the following. Not sure if it is relevant, but the feature learning epochs didn't seem to do so well and dropped in epoch 2 to accuracy of only .1.