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
There's a bug where if you set nfolds = 0, and turn on early stopping in any tree based model (GBM, DRF, XGBoost), the reported actual value for the ntrees parameters are incorrect. This is supposed to be updated with the final/found/actual value, but for some reason it’s just replacing it with the “input” value.
When you have CV turned on (and use CV for early stopping), it will correctly report the "actual" (found) value for ntrees (which can be confirmed by looking at model summary with actual # of trees). However, if you turn off CV, then it incorrectly reports the input value as the “actual” value. Bug can be reproduced from the attached notebook.
This is only currently a bug in Python right now because there's a [https://h2oai.atlassian.net/browse/PUBDEV-8051|https://h2oai.atlassian.net/browse/PUBDEV-8051|smart-link] where we are not storing the actual value at all, so that's currently unaffected (but we need to fix that ASAP as well).
The text was updated successfully, but these errors were encountered:
There's a bug where if you set nfolds = 0, and turn on early stopping in any tree based model (GBM, DRF, XGBoost), the reported actual value for the ntrees parameters are incorrect. This is supposed to be updated with the final/found/actual value, but for some reason it’s just replacing it with the “input” value.
When you have CV turned on (and use CV for early stopping), it will correctly report the "actual" (found) value for ntrees (which can be confirmed by looking at model summary with actual # of trees). However, if you turn off CV, then it incorrectly reports the input value as the “actual” value. Bug can be reproduced from the attached notebook.
This is only currently a bug in Python right now because there's a [https://h2oai.atlassian.net/browse/PUBDEV-8051|https://h2oai.atlassian.net/browse/PUBDEV-8051|smart-link] where we are not storing the actual value at all, so that's currently unaffected (but we need to fix that ASAP as well).
The text was updated successfully, but these errors were encountered: