Add more feature selection operators about tpot HOT 7 CLOSED

Would these be options that fall under the _dt_feature_selection method?

from tpot.

Nope - these will be separate functions.

On Friday, December 4, 2015, Nathan [email protected] wrote:

Would these be options that fall under the _dt_feature_selection method?

—
Reply to this email directly or view it on GitHub
#45 (comment).

Randal S. Olson, Ph.D.
Postdoctoral Researcher, Institute for Biomedical Informatics
University of Pennsylvania

E-mail: [email protected] | Twitter: @randal_olson
https://twitter.com/randal_olson
http://www.randalolson.com

from tpot.

Right, duh, because dt stands for decision tree. These operators would then act as alternatives to _dt_feature_selection. I'd be interested in taking a stab at it tonight/this weekend.

from tpot.

Awesome. I'll keep an eye out for the PR!

On Friday, December 4, 2015, Nathan [email protected] wrote:

Right, duh, because dt stands for decision tree. These operators would
then act as alternatives to _dt_feature_selection. I'd be interested in
taking a stab at it tonight/this weekend.

—
Reply to this email directly or view it on GitHub
#45 (comment).

Randal S. Olson, Ph.D.
Postdoctoral Researcher, Institute for Biomedical Informatics
University of Pennsylvania

E-mail: [email protected] | Twitter: @randal_olson
https://twitter.com/randal_olson
http://www.randalolson.com

from tpot.

@bartleyn, just wanted to ping you about this one to see if you're working on it. If not, I'll likely try to tackle this issue this week.

from tpot.

Was actually about to submit my PR -- I've gotten all four to work as additional operators, but could probably use some optimization (no caching, etc). Also could probably abstract a couple additional things.

from tpot.

Woohoo! 👍

In your PR, please note what operators are slow (and how they can be optimized) and how else the code can be improved so we can file them as PRs or fix them on the spot.

Cheers!

from tpot.