-
Notifications
You must be signed in to change notification settings - Fork 42
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
Feature Request: tune_bayes()
verbose options
#677
Comments
Ah, I see. Thanks for the issue! The difference between those arguments has been obfuscated since 1.0.0. For the meantime before we get a fix out, you can still get that library(parsnip)
library(rsample)
library(tune)
set.seed(42)
res <- tune_bayes(
nearest_neighbor("regression", neighbors = tune()),
mpg ~ .,
vfold_cv(mtcars, v = 3),
control = control_bayes(verbose = TRUE),
iter = 2, initial = 3
)
#>
#> ❯ Generating a set of 3 initial parameter results
#> ✓ Initialization complete
#>
#>
#> ── Iteration 1 ─────────────────────────────────────────────────────────────────
#>
#> i Current best: rmse=3.557 (@iter 0)
#> i Gaussian process model
#> ✓ Gaussian process model
#> i Generating 12 candidates
#> i Predicted candidates
#> i neighbors=12
#> i Estimating performance
#> i Fold1: preprocessor 1/1
#> ✓ Fold1: preprocessor 1/1
#> i Fold1: preprocessor 1/1, model 1/1
#> ✓ Fold1: preprocessor 1/1, model 1/1
#> i Fold1: preprocessor 1/1, model 1/1 (extracts)
#> i Fold1: preprocessor 1/1, model 1/1 (predictions)
#> i Fold2: preprocessor 1/1
#> ✓ Fold2: preprocessor 1/1
#> i Fold2: preprocessor 1/1, model 1/1
#> ✓ Fold2: preprocessor 1/1, model 1/1
#> i Fold2: preprocessor 1/1, model 1/1 (extracts)
#> i Fold2: preprocessor 1/1, model 1/1 (predictions)
#> i Fold3: preprocessor 1/1
#> ✓ Fold3: preprocessor 1/1
#> i Fold3: preprocessor 1/1, model 1/1
#> ✓ Fold3: preprocessor 1/1, model 1/1
#> i Fold3: preprocessor 1/1, model 1/1 (extracts)
#> i Fold3: preprocessor 1/1, model 1/1 (predictions)
#> ✓ Estimating performance
#> ⓧ Newest results: rmse=3.572 (+/-0.861)
#>
#> ── Iteration 2 ─────────────────────────────────────────────────────────────────
#>
#> i Current best: rmse=3.557 (@iter 0)
#> i Gaussian process model
#> ✓ Gaussian process model
#> i Generating 11 candidates
#> i Predicted candidates
#> i neighbors=9
#> i Estimating performance
#> i Fold1: preprocessor 1/1
#> ✓ Fold1: preprocessor 1/1
#> i Fold1: preprocessor 1/1, model 1/1
#> ✓ Fold1: preprocessor 1/1, model 1/1
#> i Fold1: preprocessor 1/1, model 1/1 (extracts)
#> i Fold1: preprocessor 1/1, model 1/1 (predictions)
#> i Fold2: preprocessor 1/1
#> ✓ Fold2: preprocessor 1/1
#> i Fold2: preprocessor 1/1, model 1/1
#> ✓ Fold2: preprocessor 1/1, model 1/1
#> i Fold2: preprocessor 1/1, model 1/1 (extracts)
#> i Fold2: preprocessor 1/1, model 1/1 (predictions)
#> i Fold3: preprocessor 1/1
#> ✓ Fold3: preprocessor 1/1
#> i Fold3: preprocessor 1/1, model 1/1
#> ✓ Fold3: preprocessor 1/1, model 1/1
#> i Fold3: preprocessor 1/1, model 1/1 (extracts)
#> i Fold3: preprocessor 1/1, model 1/1 (predictions)
#> ✓ Estimating performance
#> ⓧ Newest results: rmse=3.565 (+/-0.794) Created on 2023-04-24 with reprex v2.0.2 The |
This issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with a reprex: https://reprex.tidyverse.org) and link to this issue. |
tune_bayes()
verbose optionsIn {tune} 1.0.0
verbose = TRUE
resulted in:Created on 2023-04-24 with reprex v2.0.2
Session info
After reading the changelog I expected that
verbose_iter
replaced this option (like infinetune::control_sim_anneal()
).But now with {tune} 1.1.1 I get:
Created on 2023-04-24 with reprex v2.0.2
Session info
Can the old behaviour be restored somehow?
The text was updated successfully, but these errors were encountered: