Remove "suspicious data" functionality from model exploration #178
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.
This is for #176.
I've removed all of the code for keeping track of and saving the suspicious data, and I've removed
output_suspicious_TD
from the docs. I took this opportunity to rewrite_get_confusion_matrix()
to use a singleselect()
instead of 4filter()
+count()
s. I did a little bit of initial profiling, and I think this should be a pretty significant speedup.I renamed some variables which had capital letters like
TP
andFN
, replacing those with their lowercase counterparts, or spelling out "true_positives" and "false_negatives", etc.