Closed PeterDSteinberg closed 7 years ago
TODO:
score_weights
parameter is used correctly related to deap
(it is used to flip minimization to maximization) and make sure the examples use it correctly (IIRC, there is some confusion currently in the elm
docs from Phase I).Here are the py.test -m "not slow" -vvvv
(skipping slow tests and running with verbose flag) output.
The tests show 18 failed, 1866 passed, 1941 skipped, 194 deselected, 15 warnings in 383.18 seconds
pytest_vvv_not_slow_tuesday_october_11_results.txt
Over the next day I'll continue commenting on existing issues and making new ones (about 4 or 6) that relate to the 18 test failures. Those test failures do not delay the merge of this PR as some are "expected failures" (not marked as such in py.test but expected to fail because we have not completed all of data structure flexibility goals).
@gbrener Could you checkout this branch and run the py.test
command in Py 3.6 / 2.7 locally and pipe your output to a similar file so we can check the number of failures is the same or explain why different. I constructed my env by install elm
from the anaconda elm 3.5 dev branch to get the environment, then installed from this branch + xarray_filters PR 19
Refactor of evolutionary algorithms as
EaSearchCV
(subclass ofdask_searchcv.DaskBaseSearchCV
):dask_searchcv
rather than the Phase Ielm
approachcv_results_
attribute ofEaSearchCV
)Example usage: