All six of the failing tests are checking for expected Environment.cross_experiment_key
Battle-Plan
Need dataset hashes to be consistent across different Pandas versions
Add new clause to :func:hyperparameter_hunter.keys.hashing.to_hashable to handle DataFrames
Because to_hashable is used by make_hash_sha256, this change will apply not only to key hashes, but also to the WIP hashes generated by :mod:feature_engineering to track changes made by different EngineerSteps
Both produce consistent values for datasets for Pandas 0.24.2 and 0.25.0. However, the first feels safer, whereas the second is easier to understand and follows some representation of the object, rather than an actual hash, which is the intended purpose of to_hashable
Problem
Environment.cross_experiment_key
valuescross_experiment_key
, only the (hashed) values of the datasets actually changedCategorical.optional
Feature Engineering stepstests.test_environment
are failing:test_environment_init_cv_params
(both scenarios)test_environment_init_metrics
(both scenarios)test_environment_init_cross_experiment_params
(both scenarios)Environment.cross_experiment_key
Battle-Plan
hyperparameter_hunter.keys.hashing.to_hashable
to handle DataFramesto_hashable
is used bymake_hash_sha256
, this change will apply not only to key hashes, but also to the WIP hashes generated by :mod:feature_engineering
to track changes made by differentEngineerStep
sOptions for New DataFrame Clause
or something like
Both produce consistent values for datasets for Pandas 0.24.2 and 0.25.0. However, the first feels safer, whereas the second is easier to understand and follows some representation of the object, rather than an actual hash, which is the intended purpose of
to_hashable