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

Support HyperParameter composition #80

Open
csala opened this issue Jun 13, 2018 · 0 comments
Open

Support HyperParameter composition #80

csala opened this issue Jun 13, 2018 · 0 comments
Assignees
Labels
new feature New features that affect the public API

Comments

@csala
Copy link
Contributor

csala commented Jun 13, 2018

Some classifiers accept multiple types for the same HyperParameter.
An example of this is the max_features hyperparameter of the RandomForestRegressor:

max_features : int, float, string or None, optional (default="auto")
The number of features to consider when looking for the best split:

  • If int, then consider max_features features at each split.
  • If float, then max_features is a percentage and
    int(max_features * n_features) features are considered at each split.
  • If "auto", then max_features=n_features.
  • If "sqrt", then max_features=sqrt(n_features).
  • If "log2", then max_features=log2(n_features).
  • If None, then max_features=n_features.

Combining multiple HyperParameters, or multiple Ranges of the same type, in a single HyperParameter (e.g. STRING + INT + FLOAT) should be possible in order to cover cases like this one.

@csala csala added the new feature New features that affect the public API label Jun 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new feature New features that affect the public API
Projects
None yet
Development

No branches or pull requests

2 participants