align verbosity options with documented behavior #682
Merged
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.
Closes #677. That issue points out that the
verbose
option is, in most cases, the option actually controlling Bayesian tuning output. This PR follows up on #547 and aims to disambiguateverbose
andverbose_iter
to better align with the documented functionality.Many of the changes here transition
if (control$verbose)
toif (isTRUE(control$verbose_iter))
, sinceverbose_iter
isn't incontrol_grid()
output. This also adds aniter = FALSE
argument totune_log()
, a helper that is used in many different places for many different things—iter
indicates that this is an update on the iterative search, which need not necessarily be an issue that triggers the catalog orlog_problems()
.With this PR:
finetune is unaffected!👍