Add unit test in python for dnn explanation#1714
Merged
shendiaomo merged 1 commit intosql-machine-learning:developfrom Jan 15, 2020
Merged
Add unit test in python for dnn explanation#1714shendiaomo merged 1 commit intosql-machine-learning:developfrom
shendiaomo merged 1 commit intosql-machine-learning:developfrom
Conversation
typhoonzero
approved these changes
Jan 15, 2020
| save="dnnmodel", | ||
| is_pai=False, | ||
| plot_type='bar', | ||
| result_table="iris.explain_result") |
Collaborator
There was a problem hiding this comment.
Will this overwrite the above test's result?
Collaborator
Author
There was a problem hiding this comment.
No. They are saved to different files and DNN doesn't support explaining to table now.
Collaborator
There was a problem hiding this comment.
Maybe set result_table="" to avoid confusing?
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
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.
Fix #1694 (comment)