added option to use NaN values in categorical columns #305
Conversation
This file contains 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
added copy to any predict or predict_proba call to only pass definitiv copies
removed copy from predict function calls, added test for testing categorical labels
…-manipulation-prevention-by-models
…-types-and-value-manipulation-prevention-by-models Fix for nan in categorical types and value manipulation prevention by models
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.
fixed issue when categorical features have nan as values, a crash occurs
added the option to allow nan category values in frontend
issue: #273
This is a reupload after seeing the old PR still being open with the new version of ExpDash