# dials 0.0.9 2020-09-16

• Quantitative parameters now print the number of possible values if they have been set with value_set() (@kmdupr33, #138).

• The print() method for parameters() has changed to be more clear.

• A new function, pull_dials_object() was also added.

• Duplicate parameter combinations are now automatically removed from grid results.

• The range for epochs() was change to start at 10 iterations instead of 1.

• The lower range for spline_degree() now starts at 1 instead of 3.

• The upper range for cost() now goes to 2^5 instead of 2^-1.

# dials 0.0.8 2020-07-08

• A number of new parameter objects associated with engine-specific functions were added for engines “ranger”, “randomForest”, “earth” and “C5.0”.

# dials 0.0.7 2020-06-10

• The grid_*() functions no longer generate subclassed tibbles.

• predictor_prop() was added.

• The levels argument for tune_grid() can now handle a named vector, to account for differences in ordering.

## Breaking changes

• The range of dist_power() was changed so that the lower limit is 1.

• The deprecation period for margin() is over; please use svm_margin() instead.

# dials 0.0.6 2020-04-03

• Quick bug fix release related to range checks in 0.0.5. The check is more forgiving when the required type is integer and a double is provided.

# dials 0.0.5 2020-04-01

• When kept in the original units, a parameter’s range must now be the same data type as the parameter.

• Renamed margin() to svm_margin() (@gabrielodom and @gralgomez, #85)

• A bug in space filling designs with qualitative parameters was fixed (#94)

• A better error message was created when grids are used with parameters sets that contain parameters that require finalization (#99)

• Space-filling desings now share the same attributes as other grid objects (#100)

• The range for sample_frac() was fixed (#96)

# dials 0.0.4 2019-12-02

## New parameter functions:

• Parameters smoothness() was added.

## Other changes

• param_set() is being renamed parameters(). The old name implied that you only use it to set parameters (say from a recipe or model rather than de novo). param_set() will be available until version 0.0.5.

• The range for num_hash() was increase to be 2^8 to 2^12.

• The range for max_tokens() was changed to be 0 to 1000.

## Breaking changes

• offset() has been renamed kernel_offset() to avoid name conflicts.

# dials 0.0.3 2019-10-01

## Breaking changes

• All parameter objects are now parameter functions. For example, the pre-configured object mtry is now a function, mtry(), with arguments for the range and the trans. This provides greater flexibility in parameter creation, and should feel more natural.

• deg_free() erroneously produced real values; integers are now returned.

• Default ranges were changed for learn_rate() and neighbors() were changed.

• update.param_set() now takes multiple named arguments.

## Other changes

• Two functions for space-filling designs were added: grid_max_entropy() and grid_latin_hypercube().

• A data set was added for modeling ridership on the Chicago L trains.

## New parameter functions:

• Parameters spline_degree(), over_ratio(), under_ratio(), freq_cut(), unique_cut(), num_breaks(), min_unique(), num_hash(), signed_hash(), sample_prop(), window_size(), min_dist(), and degree_int() were added.

# dials 0.0.2 2018-12-09

• Parameter objects now contain code to finalize their values and a number of helper functions for certain data-specific parameters. A force option can be used to avoid updating the values.

• Parameter objects are printed differently inside of tibbles.

• regularization was changed to penalty in a few models to be consistent with this change.

• batch_size and threshold were added.

• Added a set of parameters for the textrecipes package issue 16.

# dials 0.0.1 2018-08-13

• First CRAN version