GitLab

Created by: gkirgizov

In ApiComposer.compose_fedot_model there's a piece of code that's responsible for preparation and fit of initial assumption. There's also logic that determines available operations based on results of the fit. Aim of this issue is to separate this configuration stage from the ApiComposer and make it more light-weight. Maybe logic of handling preset and determining available_operations could be hidden. Maybe all this can be made part of InitialAssumptionsBuilder. I'm not sure what's better.

Idea (with reference to the code) was initiated here: https://github.com/nccr-itmo/FEDOT/pull/716#discussion_r893171027

Another point that could help in refactoring this is to modify ApiTime such that init_pipeline_fit_time could be computed similarly to ApiTime.launch_tuning with something like ApiTime.launch_init_pipeline_fit. With this we could hide all timing-related logic in ApiTime.