hotfix: go for FeaturesType instead of InputData in a pipeline tuning #1311
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a 🙋 feature or enhancement.
Summary
tune
function so that theinput_data
param can be of typeFeaturesType
. This allows passing one of the following data formats:str, PathLike, numpy array, pandas DataFrame, FEDOT-native InputData, FEDOT-native MultiModalData, dictionary, or tuple
add unit tests with different data formats(covered withtest/unit/api/test_main_api
andtest/integration/pipelines/tuning/test_pipeline_tuning
)Context
related to discussion in #1298