-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Document eval_metric in XGBoost #6887
Comments
hannah.tillman commented: also add {{score_eval_metric_only}} to params: Score only the evaluation metric when enabled. This can make model training faster if scoring is frequent (e.g. each iteration). Defaults to {{False}}. |
hannah.tillman commented: Quick notes: Put in the FAQ:
By default, H2O calculates all appropriate metrics for given problems. Given a binary classification model, H2O will report at least logloss, AUC, and AUCPR. When early stopping is used, you will need to choose one of the built-in early stopping metrics. For consistency between different model types and/or algorithm implementations, these are always calculated by H2O itself and are independent of XGBoost’s You don’t always need to specify your custom
|
JIRA Issue Details Jira Issue: PUBDEV-8889 |
Linked PRs from JIRA |
In [https://github.com//pull/6399|https://github.com//pull/6399|smart-link] we added a notebook describing how to properly use {{eval_metric}} to speed-up XGBoost scoring in early stopping scenario with frequent scoring.
[~accountid:5afa05ceac509206c8203255] pointed out that we need to also document it clearly in H2O documentation: [https://github.com//pull/6399#pullrequestreview-1160569522|https://github.com//pull/6399#pullrequestreview-1160569522|smart-link] - the use case of early stopping being an important factor
The text was updated successfully, but these errors were encountered: