Chapter 7 DecisionTree example used normalized data #5
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The DecisionTree example in 'Chapter 7.ipynb' was not running with scikit-learn 1.2.1 and with Scikit-learn 1.1.1 was throwing a warning. The message included: "The feature names should match those that were passed during fit." and was referencing the normalized data.
After some digging, it turns out that newApplicant was changed for KNN example and not reverted to the original data for the DecisionTree example. This code creates a newApplicant with non-normalized values and now runs without throwing errors. I tried to stay close to the style of the code in the KNN example.