Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Always Normalize Features #17

Open
epeters3 opened this issue Jan 16, 2020 · 1 comment
Open

Always Normalize Features #17

epeters3 opened this issue Jan 16, 2020 · 1 comment
Labels
feature 🚀 New feature or request

Comments

@epeters3
Copy link
Owner

Many optimization strategies do best when the features are all normalized. Rather than currently requiring normalization to be found as a preprocessor when sampling, always insert a normalization preprocessing step, with an option to not normalize (e.g. have normalize=True be a default in the crank API).

@epeters3 epeters3 added the feature 🚀 New feature or request label Jan 16, 2020
@epeters3
Copy link
Owner Author

I think it makes sense to still include the normalization primitives as searchable options since it may be valuable to have normalization again after some prediction or other preprocessing that again alters the range of the data in the ML pipeline.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature 🚀 New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant