Repository navigation
Feat: Report specificity and confidence intervals in analytics - #3586
Closed
🐦[T3T]Berserker 🐦 🐍 (TrinityBerserker) wants to merge 1 commit into
Closed
🐦[T3T]Berserker 🐦 🐍 (TrinityBerserker) wants to merge 1 commit into
🐦[T3T]Berserker 🐦 🐍 (TrinityBerserker) wants to merge 1 commit into
Conversation
Author
|
@microsoft-github-policy-service agree |
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.
This PR resolves #3579 by reporting scorer specificity alongside attack success rates and adding confidence intervals to outcome statistics.
Changes:
All existing unit tests pass (114 tests in test_analytics.py and 24 in test_derivation.py).
Fixes #3579