alteryx / alteryx/evalml

Move pipeline parameter logic into AutoMLAlgorithm

Open
#3,400 0 comments 1 reaction 0 assignees View on GitHub
enhancement
Dominant language
Python
Stars
850
Forks
96
PR merge metrics
No merged PRs in 30d

Description

Related to [this discussion](https://github.com/alteryx/evalml/pull/3373#discussion_r832473688).

With [this PR](https://github.com/alteryx/evalml/pull/3373) we have consolidated most of the pipeline parameter-creating logic into the `AutoMLAlgorithm` class. However, there are still cases, like with the sampler parameters, that might be useful to move out of `AutoMLSearch`. My main concern is if we choose to move this, we would need to pass all of the relevant data to `AutoMLAlgo`, like `sampler_name`, `problem_type`, and the `X, y` data.

This issue tracks determining if there is another way to move the pipeline parameter definitions to `AutoMLAlgorithm` in a clean way, and implementing it if so. If not, it would be nice to write about what the limitations/tradeoffs are.

fyi @freddyaboulton @jeremyliweishih

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.