Skip to content

[ML] Output max num trees in hyperparameters metadata #1867

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

Merged
merged 8 commits into from
Apr 26, 2021

Conversation

valeriy42
Copy link
Contributor

We output max number trees as a hyperparameter in the model metadata and add a unit test to ensure that we achieve reproducible results when retraining a model with all hyperparameters specified.

Fixes #1853 .

Copy link
Contributor

@tveasey tveasey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good stuff! Writing this test showed up some interesting omissions. I think there is a tweak needed to get this to work with restore, but otherwise LGTM.

Copy link
Contributor

@tveasey tveasey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a small tweak requested anticipating incremental training. Looks pretty much good to go though.

@valeriy42 valeriy42 merged commit b197a08 into elastic:master Apr 26, 2021
@valeriy42 valeriy42 deleted the max-num-trees-hyperparam branch April 26, 2021 08:33
valeriy42 added a commit to valeriy42/ml-cpp that referenced this pull request Apr 26, 2021
We output max number trees as a hyperparameter in the model metadata and add a unit test to ensure that we achieve reproducible results when retraining a model with all hyperparameters specified.

Fixes elastic#1853 .
tveasey added a commit that referenced this pull request Apr 26, 2021
…x setup (#1870)

Following on from #1867, we can and should be imposing the minimum depth constraint to the hyperparameter search
bounding box. This was incorrectly applied before and also fixes the issue with reproducibility based on user overrides.
This is a bit cleaner than applying the constraint magically in the code to adjust hyperparameters.
valeriy42 pushed a commit to valeriy42/ml-cpp that referenced this pull request Apr 26, 2021
…x setup (elastic#1870)

Following on from elastic#1867, we can and should be imposing the minimum depth constraint to the hyperparameter search
bounding box. This was incorrectly applied before and also fixes the issue with reproducibility based on user overrides.
This is a bit cleaner than applying the constraint magically in the code to adjust hyperparameters.
valeriy42 added a commit to valeriy42/ml-cpp that referenced this pull request Apr 26, 2021
We output max number trees as a hyperparameter in the model metadata and add a unit test to ensure that we achieve reproducible results when retraining a model with all hyperparameters specified.

Fixes elastic#1853 .
valeriy42 added a commit to valeriy42/ml-cpp that referenced this pull request Apr 26, 2021
We output max number trees as a hyperparameter in the model metadata and add a unit test to ensure that we achieve reproducible results when retraining a model with all hyperparameters specified.

Fixes elastic#1853 .
valeriy42 pushed a commit to valeriy42/ml-cpp that referenced this pull request Apr 26, 2021
…x setup (elastic#1870)

Following on from elastic#1867, we can and should be imposing the minimum depth constraint to the hyperparameter search
bounding box. This was incorrectly applied before and also fixes the issue with reproducibility based on user overrides.
This is a bit cleaner than applying the constraint magically in the code to adjust hyperparameters.
valeriy42 pushed a commit to valeriy42/ml-cpp that referenced this pull request Apr 26, 2021
…x setup (elastic#1870)

Following on from elastic#1867, we can and should be imposing the minimum depth constraint to the hyperparameter search
bounding box. This was incorrectly applied before and also fixes the issue with reproducibility based on user overrides.
This is a bit cleaner than applying the constraint magically in the code to adjust hyperparameters.
valeriy42 added a commit that referenced this pull request Apr 27, 2021
* [ML] Output max num trees in hyperparameters metadata (#1867)

We output max number trees as a hyperparameter in the model metadata and add a unit test to ensure that we achieve reproducible results when retraining a model with all hyperparameters specified.

Fixes #1853 .

* [ML] Apply tree depth constraint to hyperparameter search bounding box setup (#1870)

Following on from #1867, we can and should be imposing the minimum depth constraint to the hyperparameter search
bounding box. This was incorrectly applied before and also fixes the issue with reproducibility based on user overrides.
This is a bit cleaner than applying the constraint magically in the code to adjust hyperparameters.

Co-authored-by: Tom Veasey <[email protected]>
valeriy42 added a commit that referenced this pull request Apr 27, 2021
* [ML] Output max num trees in hyperparameters metadata (#1867)

We output max number trees as a hyperparameter in the model metadata and add a unit test to ensure that we achieve reproducible results when retraining a model with all hyperparameters specified.

Fixes #1853 .

* [ML] Apply tree depth constraint to hyperparameter search bounding box setup (#1870)

Following on from #1867, we can and should be imposing the minimum depth constraint to the hyperparameter search
bounding box. This was incorrectly applied before and also fixes the issue with reproducibility based on user overrides.
This is a bit cleaner than applying the constraint magically in the code to adjust hyperparameters.

Co-authored-by: Tom Veasey <[email protected]>
valeriy42 added a commit that referenced this pull request Apr 27, 2021
* [ML] Output max num trees in hyperparameters metadata (#1867)

We output max number trees as a hyperparameter in the model metadata and add a unit test to ensure that we achieve reproducible results when retraining a model with all hyperparameters specified.

Fixes #1853 .

* [ML] Apply tree depth constraint to hyperparameter search bounding box setup (#1870)

Following on from #1867, we can and should be imposing the minimum depth constraint to the hyperparameter search
bounding box. This was incorrectly applied before and also fixes the issue with reproducibility based on user overrides.
This is a bit cleaner than applying the constraint magically in the code to adjust hyperparameters.

Co-authored-by: Tom Veasey <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[ML] Add maximum number trees to hyperparameters inference model metadata
2 participants