Explain hashing vectorizer #12
Merged
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
Current coverage is 91.78% (diff: 100%)@@ master #12 diff @@
==========================================
Files 12 12
Lines 565 572 +7
Methods 0 0
Messages 0 0
Branches 90 91 +1
==========================================
+ Hits 515 525 +10
+ Misses 28 27 -1
+ Partials 22 20 -2
|
Also add coef_scale to explain_prediction kwargs
This was referenced Oct 19, 2016
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.
When the hashing vectorizer is passed as-is (not wrapped into InvertableHashingVectorizer), then an InvertableHashingVectorizer is built when explaining predictions for this document, and then discarded. If the InvertableHashingVectorizer is passed, then it is assumed that it was already fit (it's also possible to call a partial fit for it, but it seems to complicate the API).
Fixes #9