tidymodels/dials

Issues

• Deprecate `grid_latin_hypercube()` and `grid_max_entropy()`

  #332 opened 6 months ago by hfrick
  0

• Revise space-filling designs

  #307 opened 6 months ago by topepo
  0

• Restructure parameter section reference page

  #330 opened 7 months ago by hfrick
  1

• Release dials 1.2.1

  #326 opened 10 months ago by hfrick
  0

• Move from `trans` to `transform` with scales 1.3.0

  #316 opened 10 months ago by hfrick
  0

• Fix doc-related NOTE on R-devel

  #320 opened 10 months ago by hfrick
  0

• finalize with recipe

  #314 opened a year ago by jxu
  0

• parameters is under-documented

  #313 opened a year ago by jxu
  0

• slowdown in `check_for_unknowns()`

  #305 opened a year ago by simonpcouch
  1

• Use rlang type-checkers

  #312 opened a year ago by hfrick
  0

• Use cli errors

  #311 opened a year ago by hfrick
  0

• Test is flaky

  #308 opened a year ago by MichaelChirico
  4

• tune_bayes issue

  #270 opened 2 years ago by amin0511ss
  4

• Upkeep for dials 2023

  #274 opened 2 years ago by hfrick
  2

• Remove `pull_dials_object()` from pkgdown site

  #279 opened 2 years ago by hfrick
  1

• Deprecate grid methods for `workflow` objects

  #299 opened 2 years ago by hfrick
  2

• Release dials 1.2.0

  #303 opened 2 years ago by hfrick
  1

• Use updates error handling

  #271 opened 2 years ago by EmilHvitfeldt
  0

• Allow `label = NULL` for `new_quant_param()`

  #266 opened 2 years ago by hfrick
  1

• Error in `.f()`: ! Values should be on [0, 1].

  #258 opened 2 years ago by Tadge-Analytics
  8

• Release dials 1.1.0

  #263 opened 2 years ago by hfrick
  1

• Better error message when using range argument wrong

  #247 opened 2 years ago by EmilHvitfeldt
  2

• pluralize possible values in `print.qual_param`

  #249 opened 2 years ago by simonpcouch
  1

• prior_terminal_node_expo hyperparameter has incorrect default range for dbarts

  #251 opened 2 years ago by n8layman
  2

• type stable `trans` values

  #255 opened 2 years ago by topepo
  0

• `default` values should be within `range` or `values`

  #229 opened 2 years ago by hfrick
  5

• Parameter importance for tuning grid construction

  #248 opened 2 years ago by franzbischoff
  6

• Release dials 1.0.0

  #240 opened 2 years ago by hfrick
  1

• Expand documentation for custom transforms

  #238 opened 2 years ago by mikemahoney218
  10

• Warning: partial match of 'inv' to 'inverse'

  #237 opened 3 years ago by mikemahoney218
  2

• Use `pillar::type_sum()` rather than `dplyr::type_sum()`

  #234 opened 3 years ago by DavisVaughan
  2

• mismatch in `mtry` documentation

  #232 opened 3 years ago by simonpcouch
  2

• improve prompting on engine-specific arguments without default parameters

  #230 opened 3 years ago by simonpcouch
  1

• revise `parameters.default` error message to point out class of `x`

  #225 opened 3 years ago by simonpcouch
  2

• Remove usage of `parameters()` to extract a parameter set

  #210 opened 3 years ago by hfrick
  1

• Release dials 0.1.1

  #222 opened 3 years ago by hfrick
  1

• Failure with dev scales

  #217 opened 3 years ago by hadley
  6

• sample_size = sample_prop() quirk when creating tuning grid

  #212 opened 3 years ago by py9mrg
  4

• Upkeep for dials

  #213 opened 3 years ago by hfrick
  1

• Upkeep for dials

  #209 opened 3 years ago by hfrick
  1

• Release dials 0.1.0

  #205 opened 3 years ago by hfrick
  2

• replace `pull_dials_object()` with `extract_dials_parameters()`

  #173 opened 3 years ago by hfrick
  2

• update documentation referencing model definitions

  #198 opened 3 years ago by hfrick
  1

• grid_latin_hypercube() varies eventhough size is set.

  #196 opened 3 years ago by nvelden
  10

• sample_size()

  #175 opened 3 years ago by Steviey
  2

• Move `master` branch to `main`

  #184 opened 3 years ago by jennybc
  2

• Can't tune recipes::step_window size parameter

  #180 opened 3 years ago by camroberts
  5

• Release dials 0.0.10

  #185 opened 3 years ago by hfrick
  1

• tune() `alpha` and `lambda` hyperparameters in XGBoost

  #176 opened 3 years ago by afewmoments
  10

• Possible bug with `batch_size()` parameter?

  #177 opened 3 years ago by tonyk7440
  3