Use same max_depth when comparing gbdt and hgbt - #882
Open
ArturoAmorQ wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As flagged in the forum,
HistGradientBoostingRegressorandGradientBoostingRegressorare explicitly aligned on the max number of iterations, but the default values of other important parameters, such asmax_depth, are very different (HGBT builds full trees and GBDT builds shallow trees).As is, the unfair comparison may make
HistGradientBoostingRegressorlook slower thanGradientBoostingRegressor, depending on the CPU (see this issue).To keep the message of this notebook simple, this PR modifies
max_depthonly, as it impacts the fit time the most.