Open GillesVandewiele opened 6 years ago
Ok I figured out what is going wrong... Don't know if this is supposed to be, but since you are taking the maximum along the first axis, it is just the best score and the maximum number of features in a subset which is displayed over there.
I guess it makes more sense to display the number of features for the current best solution? I'll try to make some changes and send a PR in the nearby future.
Yes, they are independent stats about the score and the features number, so it's the maximum number of selected features, not the number of features of the best individual.
Hello,
First of all, great work on creating this repository! Very lightweight and nicely coded. I've used it a lot for projects already, but lately I have been running into a strange problem...
I'm running the algorithm to tune for AUC, and the sum(selector.support_) is not equal to the number of features from the best individual in the logs that are printed to std output.
print(sum(selector.support_))
-->231
while I expected 244 here.Maybe something wrong with the HOF from DEAP?