You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
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.
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 thecrank
API).The text was updated successfully, but these errors were encountered: