Make LightGBM not verbose #4308
Merged
Conversation
This file contains 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
Codecov ReportPatch and project coverage have no change.
Additional details and impacted files@@ Coverage Diff @@
## main #4308 +/- ##
=====================================
Coverage 99.7% 99.7%
=====================================
Files 357 357
Lines 39739 39739
=====================================
Hits 39619 39619
Misses 120 120
☔ View full report in Codecov by Sentry. |
MichaelFu512
commented
Sep 14, 2023
| @@ -108,6 +108,7 @@ def __init__( | |||
| "n_jobs": n_jobs, | |||
| "bagging_freq": bagging_freq, | |||
| "bagging_fraction": bagging_fraction, | |||
| "verbose": -1, | |||
There was a problem hiding this comment.
Note: this does suppress everything that LightGBM would display. (including info and warnings).
jeremyliweishih
approved these changes
Sep 18, 2023
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.
Pull Request Description
Closes #4307
Whenever you run
automl.search(), LightGBM really likes to say the same warning over and over again.For example, in the start page of the documentation for EvalML even if you set
verbose=False:the output has this:
After creating the pull request: in order to pass the release_notes_updated check you will need to update the "Future Release" section of
docs/source/release_notes.rstto include this pull request by adding :pr:123.