class AutoBase and AutoAbstract

[martins0n]

🚀 Feature Request

• Auto and Tune share the same logic and methods
• We should move it to unified class

Proposal

• add class AutoBase with methods fit, summary, top_k
• add interface AutoAbstract with fit, summary, top_k, objective , _init_optuna
• inherit Auto from AutoBase

Test cases

• refactor test_auto to test common methods of AutoBase where it's necessary

Additional context

No response

[GooseIt]

I'd like to take this issue after completing 1025.

[GooseIt]

As I currently understand it, classes Tune and Auto will have vastly different fit methods: the first is going to optimize hyperparameters for one selected Pipeline, while the second will pick the best-fitted pipeline from a user-determined pool without any hyperparameter optimization for any given pipeline. The question is:
Should fit method in AutoBase class be an abstractmethod, that later will be overridden separately in Tune and Auto classes?
Or should I rather strive to write fit method in such a way that it will work with both Tune and Auto classes without any overrides?
If I am wrong in my understanding, please correct me.

[martins0n]

Should fit method in AutoBase class be an abstractmethod, that later will be overridden separately in Tune and Auto classes?

Yes, you're right

It's better to implement it mostly separately. In case they have something in common we will refactor it next.

In the future tasks fit in Auto will call Tune.fit for the best configs to be fine turned - so the logic will be more complicated

[GooseIt]

In case you worry that I left the project silently, I'm still working on the issue and will submit code tomorrow.

[martins0n]

It's ok. We are not in a hurry