check compatibility of initial and param_info

[simonpcouch]

Closes #59. This code just reproduces the portion of dials::encode_unit() methods that picks up on this discrepancy and gives it a more context-specific message.

library(tidymodels)

set.seed(1)

rf_spec <- rand_forest(mode = "regression", mtry = tune())

grid_with_bigger_range <- grid_latin_hypercube(mtry(range = c(1, 16)))

car_folds <- vfold_cv(car_prices, v = 2)

car_wflow <- workflow() %>% 
  add_formula(Price ~ .) %>% 
  add_model(rf_spec)

tune_res_with_bigger_range <- tune_grid(
  car_wflow, 
  resamples = car_folds,
  grid = grid_with_bigger_range
)
parameter_set_with_smaller_range <- parameters(mtry(range = c(1, 5)))

finetune::tune_sim_anneal(
  car_wflow,
  param_info = parameter_set_with_smaller_range,
  resamples = car_folds,
  initial = tune_res_with_bigger_range,
  iter = 2
)
#> Optimizing rmse
#> Initial best: 2570.90000
#> Error in `tune_sim_anneal()`:
#> ! The parameter set used when tuning generating the initial results
#>   isn't compatible with the parameter set supplied as `param_info`.
#> ℹ Possible values of parameters in `param_info` should encompass all values
#>   evaluated in the initial grid.
#>
#> ✖ Optimization stopped prematurely; returning current results.
#> # Tuning results
#> # 2-fold cross-validation 
#> # A tibble: 2 × 5
#>   splits            id    .metrics         .notes           .iter
#>   <list>            <chr> <list>           <list>           <int>
#> 1 <split [402/402]> Fold1 <tibble [6 × 5]> <tibble [0 × 3]>     0
#> 2 <split [402/402]> Fold2 <tibble [6 × 5]> <tibble [0 × 3]>     0

^{Created on 2024-01-16 with reprex v2.0.2}

I've situated this solution so that it only applies to tune_sim_anneal() as tune_bayes() is able to handle that difference just fine.

[simonpcouch]

Transitioned to mapply() so that we don't get purrr's Error in index i, caused by [call we can't control] rethrown error formatting.

[topepo]

Nice! I didn't know about transform.