Added drop of columns containing only NANs #142
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
patrickleonardy
requested review from
sborms and
ZlaTanskY
and removed request for
sborms
ZlaTanskY
requested changes
Dec 5, 2022
Co-authored-by: Jano Roelandt <48879098+ZlaTanskY@users.noreply.github.com>
ZlaTanskY
approved these changes
Dec 7, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Story Title
NaN column not preprocessed properly #138
Changes made
How does the solution address the problem
This PR will let the preprocessor drop automatically columns containing only missing values and write a warning if the dataset contains missing values and if a columns containing only missing values is dropped
Linked issues
Resolves #138