4 ms·
I think you really get into this sort of mess when you want to squeeze the last ounce of predictive performance out of an algorithm (or ensemble of algorithms).
by stdbrouw 11y ago
I think you really get into this sort of mess when you want to squeeze the last ounce of predictive performance out of an algorithm (or ensemble of algorithms). When you just want performance that is better than a plain old regression, I've found that just picking sane defaults for some hyperparameters (e.g. RBF kernel for SVM) and doing a small grid search for others (e.g. slack parameter for SVM, cost-complexity for trees) works very well.
In Python this is easy enough with scikit-learn, and in R the caret package makes semi-automatic tuning really easy.
So the question becomes: how far do we really need to go to create business value, and does it actually make sense to go all Kaggle on the problem?
- dasboth 11y agoI'm only a data science student at the moment so I don't have much "real world" experience with machine learning, but this is what I would have thought. If you're trying to get quick value from a dataset, you can probably run a "vanilla" random forest or something and get pretty good results. Then, if you want to use it in production somehow, you can go back and "go all Kaggle" (I like the expression!) on it.